agent-os v0.7.0

Implementation-ready issues

• shape-work now completes by creating or reusing concrete implementation issues on the configured planning surface.
• Each issue carries stable identity, readiness, outcome, boundaries, acceptance, ground truth, dependencies, evidence, delivery target, and open risks.
• Research, grilling, and prototypes remain decision evidence; implementation issues are the durable delivery-ready output.

Developer-owned execution

• Multiple issues no longer imply batch-work.
• Any ready issue can be selected for deliver-work.
• batch-work consumes an existing dependency-mapped issue graph only after an explicit developer request for integrated batch execution.
• dispatch-next selects one ready issue unless a batch was explicitly requested.

Lifecycle safeguards

• A chart-work handoff moves a branch to shaping, not delivery-ready.
• Selected shaping branches keep the map open until issues and a frontier exist.
• deliver-work stops before mutation when a target contains several independently closable outcomes or delivery boundaries.
• Project policy setup now captures implementation-issue readiness conventions.

Evidence

• Repository validator passed.
• All validator red cases passed, including new issue-materialization, routing, and decomposition failures.
• Batch manifest tests passed.
• VitePress production build and GitHub Pages deployment passed.
• A sealed read-only Codex 0.146.0 forward test produced two ready issues, one dependency-blocked verification issue, reconciled the handoff and map, and exposed the correct frontier without choosing batch. Actual tracker mutation and retry idempotency remain unmeasured.