ContextLattice v3.10.0 - Agent Runner Layer

Release date: 2026-07-06

v3.10.0 turns ContextLattice from a memory/control layer that agents can call into a practical local runner substrate for real agent work. Pi and Droid are now optional adapter-first runner choices, task-agent workers can execute them through safe repo-local adapters, and operators get bounded runner-quality evidence before choosing the next runner.

This is a minor release, not a major break: the public memory API, adapter contract, dashboard contract, and install shape remain compatible. ContextLattice still does not auto-dispatch, auto-merge, auto-push, or supervise Pi/Droid inside gateway-go.

Highlights

• Adds optional Pi and Droid runner adapters for task-agent work without adding Pi/Droid Docker services or gateway-specific routes.
• Keeps third-party runner installation explicit: ContextLattice surfaces readiness and install hints, but does not install Pi or Droid automatically.
• Routes Pi/Droid task-worker execution through safe adapter scripts with explicit argv execution, prompt-file construction, timeout handling, bounded stdout/stderr tails, and secret redaction.
• Adds runner_capability.v1, runner_result.v1, agent_task_lease.v1, and runner_quality_sample.v1 contract coverage.
• Records compact runner-quality samples after adapter completion and links them to context-pack quality, exact prompt-token savings, and modeled inference-avoidance evidence.
• Adds Go-native /telemetry/runner-quality and first-class contextlattice_runner_quality CLI support.
• Adds task-class slicing for runner-quality summaries so operators compare similar work instead of flattening all adapter outcomes together.
• Surfaces advisor-only runner recommendations in the dashboard and doctor/status flows.
• Repositions public docs around the CLI as the primary interaction path; dashboard, HTTP, and MCP are companion visibility/integration surfaces.
• Clarifies local-lite-advanced as an optional public adapter lab, not a paid/private boundary.
• Removes unreleased version-lane language from public-facing docs and uses paid-generic entitlement naming.

Operator Flow

contextlattice_adopt status --pretty
contextlattice_agent_discover --agents pi,droid --repo . --pretty
contextlattice_doctor --repo . --agents pi,droid --skip-provider-smoke --pretty

contextlattice_agent_adapter bootstrap --agent pi --project contextlattice --pretty
contextlattice_agent_adapter context-pack --agent droid --project contextlattice --pretty

TASK_AGENT=pi python3 scripts/task_agent_worker.py --task-agent pi --worker-name local-pi-01
TASK_AGENT=droid python3 scripts/task_agent_worker.py --task-agent droid --worker-name local-droid-01

contextlattice_runner_quality --pretty
contextlattice_runner_quality --task-class scout --pretty

Compatibility

No migration is required from v3.9.1.

Pi and Droid remain optional. Existing Codex, Claude Code, OpenCode, Hermes, MCP, HTTP, dashboard, and CLI workflows continue to use the same public contract.

GO_PAID_ENTITLEMENT_* replaces the public env-template naming for paid entitlement gates. Existing public release docs no longer describe unreleased version lanes as public product concepts.

Safety Boundaries

• No /v1/pi/* or /v1/droid/* gateway routes.
• No Pi/Droid Docker Compose services.
• No third-party runner auto-install.
• No automatic runner dispatch from runner-quality telemetry.
• No automatic merge, push, or destructive git behavior.
• No raw prompts, completions, stdout, stderr, or secrets in runner-quality telemetry.

Verification

• Pi/Droid runner support tests passed.
• Agent output contract audit passed.
• Gateway Go tests passed.
• Dashboard dependency install, test suite, and production build passed.
• Public leak guard scanned the changed release surface with no findings.
• Hosted PR checks passed for the merged public feature PRs.