v0.6.11

Release Notes - v0.6.11

Summary

• Strengthened the task runner path with clearer Codex bootstrapping, runner command coverage, log-following fixes, and release-critical runner evidence.
• Improved branch_pr route guidance so agents see safer next commands, better batch ownership handling, and clearer prompt fields for route oracle output.
• Hardened patch-release and commit-message workflows by preserving legacy close subjects, improving close formatting, and tightening release gate ergonomics.
• Updated context-upgrade and recipe surfaces while keeping release evidence, evaluator records, and generated documentation aligned with the current main branch.

Added

• Added task runner observability foundations so runner state, events, trace artifacts, and command surfaces are easier to inspect during task execution.
• Added task run route coverage for the direct-mode next-action path so approved tasks can be handed to the configured runner adapter from route decisions.
• Added Codex runner bootstrap behavior that starts with /goal, making automated task runs easier to resume and audit.
• Added route oracle prompt-field coverage so agent-facing prompts expose the concrete fields agents need instead of requiring manual reconstruction.
• Added branch_pr batch route oracle coverage for included tasks so batch ownership remains visible in route decisions.
• Added release evidence for the hosted publish tail of the previous release, keeping publication proof attached to the repository history.
• Added release route expectation coverage for v0.6.11 after release-ci-base exposed outdated test assumptions in merge-subject and runner-route behavior.

Improved

• Improved the task route oracle so the next command, authoritative checkout, and route phase are easier to consume from agent-facing surfaces.
• Clarified route oracle field names in prompt output so rendered labels and bundle paths are less likely to be confused.
• Refreshed evaluator review artifacts for the route oracle changes so quality evidence matches the current implementation.
• Strengthened batch route oracle precedence so stale batch metadata does not override the route that belongs to the current workflow mode.
• Updated direct-mode route-decision expectations to follow the runner path when no runner state exists, rather than falling back to a manual verify-show step.
• Improved commit message formatting for close and integration flows while retaining compatibility with legacy close subjects.
• Preserved legacy close-subject handling so older task closure records remain valid under the newer commit policy.
• Improved branch_pr close commit formatting and recorded task-scoped evidence for the change.
• Hardened patch-release workflow gates so release operators get stricter checks before publication.
• Hardened patch-release workflow ergonomics with tests that exercise the intended release path instead of relying on manual operator memory.
• Updated release route tests to accept compliant integrate subjects with the task suffix and merge emoji.
• Migrated the process runner to Execa v9 so process execution uses the current dependency surface.
• Aligned the core engine floor with the process-runner dependency update.
• Updated remaining direct dependencies needed by the process-runner migration.
• Refreshed generated recipe inventory after the dependency and recipe pointer changes.
• Updated the recipes submodule pointer and recorded task evidence for the pointer change.
• Gated context policy during framework upgrade so context policy changes are validated as part of the upgrade path.
• Split context upgrade coverage so policy upgrade behavior is tested in smaller, more maintainable checks.
• Aligned init policy template tests with the context policy upgrade behavior.
• Refreshed final verify steps for the context policy upgrade task.
• Recorded evaluator pass evidence for the context policy upgrade task.
• Improved runner log following so runner observability output is more reliable during long-running task runs.
• Fixed task runner lint findings that appeared after connecting the runner command surface.
• Connected the task run command to the runner execution path and refreshed task evidence for that work.
• Recorded evaluator verdict evidence for the Codex runner bootstrap and task runner changes.
• Refreshed LLM docs bundles after untracked-status documentation changes.
• Clarified untracked git status preflight behavior so operators can distinguish ignored, untracked, and tracked release risks.
• Clarified public docs around untracked git status preflight behavior.

Fixed

• Fixed route-decision batch test expectations so stale branch_pr batch artifacts no longer mask the direct-mode runner next action.
• Fixed integrate-merge test expectations so compliant merge subjects with task suffixes are treated as the expected branch_pr behavior.
• Fixed commit-message policy coverage for non-default close and merge subjects.
• Fixed patch-release workflow gate coverage so release checks catch outdated route expectations before candidate publication.
• Fixed process-runner compatibility issues introduced by the Execa v9 migration.
• Fixed runner log-following behavior so runner event streams are less likely to stall or misreport during inspection.
• Fixed context policy upgrade coverage gaps that could let template drift pass without a targeted test.
• Fixed recipes pointer drift by updating the submodule reference and regenerating related inventory evidence.
• Fixed release evidence continuity by recording hosted publish proof from the previous patch release.

Upgrade Notes

• No breaking changes.
• The release keeps the public package set in lockstep at 0.6.11: agentplane, @agentplaneorg/core, and @agentplaneorg/recipes.
• Release operators should continue using the branch_pr candidate route, merge the candidate through the protected base branch, and publish with the hosted npm workflow using the release commit SHA.

Verification

• ap release plan --patch generated .agentplane/.release/plan/2026-05-28T10-49-10-327Z for v0.6.11.
• ap doctor passed in the task worktree with no errors.
• node .agentplane/policy/check-routing.mjs passed.
• bun run test:fast passed with 337 test files, 2020 tests passed, and 2 skipped.
• bun run release:check passed after installing worktree dependencies with bun install --ignore-scripts.
• bun run build passed.
• bun run release:prepublish initially exposed stale test expectations in release-ci-base; both failing expectations were fixed in this release task.
• node scripts/checks/run-vitest-suite.mjs release-ci-base passed all 67 chunks after the fixes.
• bun run coverage:workflow-suite passed.
• bun run coverage:significant-suite passed and check-significant-coverage.mjs reported the significant suite contract OK.
• bun run test:release:critical passed with 4 files and 16 tests.