codex-workflow-v2 2.0.0-beta.1 → 2.0.0-beta.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -2
- package/dist/src/alpha6/milestone.d.ts +10 -0
- package/dist/src/alpha6/milestone.js +98 -1
- package/dist/src/alpha6/milestone.js.map +1 -1
- package/dist/src/cli.js +220 -3
- package/dist/src/cli.js.map +1 -1
- package/dist/src/reviewer.d.ts +4 -0
- package/dist/src/reviewer.js +24 -7
- package/dist/src/reviewer.js.map +1 -1
- package/dist/src/version.d.ts +1 -1
- package/dist/src/version.js +1 -1
- package/dist/src/workflow.d.ts +18 -0
- package/dist/src/workflow.js +186 -8
- package/dist/src/workflow.js.map +1 -1
- package/docs/autonomy-guardrails.md +8 -1
- package/docs/beta2-initial-assembly-navigation-brief.md +616 -0
- package/docs/development-flow.md +17 -2
- package/docs/release.md +8 -1
- package/docs/split-required-recovery.md +5 -4
- package/docs/stable-release-defect-register.md +330 -1
- package/docs/updating-existing-project.md +2 -0
- package/package.json +1 -1
- package/plugins/codex-workflow-gateway/references/protocol.md +56 -1
- package/plugins/codex-workflow-gateway/skills/codex-workflow-gateway/SKILL.md +44 -0
- package/references/state-machine.md +4 -1
|
@@ -63,7 +63,10 @@ human turn boundary.
|
|
|
63
63
|
|
|
64
64
|
During initial planning, all linked Tasks may be materialized before one complete
|
|
65
65
|
`milestone plan-set`; execution remains blocked until every reverse membership is classified.
|
|
66
|
-
|
|
66
|
+
`next` returns `milestone initial-assembly` before Task 1 and after every safe linked-Task
|
|
67
|
+
materialization, with explicit `discovery start` and `discovery materialize` commands. After at
|
|
68
|
+
least one linked Task exists, it also exposes the closing `milestone plan-set` command. Failed navigation is fail-closed and cannot be treated as an
|
|
69
|
+
expected assembly signal. After that boundary, semantic updates use human-only `milestone scope-change-prepare` and
|
|
67
70
|
`milestone scope-change-apply`. A human-confirmed, expiring Milestone Autonomy Contract may
|
|
68
71
|
use `milestone autonomy-evolve` only for membership changes while outcome, success signal,
|
|
69
72
|
acceptance, checks, discovery, and base branch remain fixed. It may also approve Project Memory
|