codex-workflow-v2 2.0.0-beta.12.2 → 2.0.0-beta.12.3
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 +3 -3
- package/dist/src/alpha7/corrective-recovery.d.ts +1 -1
- package/dist/src/alpha7/corrective-recovery.js +257 -17
- package/dist/src/alpha7/corrective-recovery.js.map +1 -1
- package/dist/src/cli.js +1 -0
- package/dist/src/cli.js.map +1 -1
- package/dist/src/version.d.ts +1 -1
- package/dist/src/version.js +1 -1
- package/dist/src/workflow.js +8 -8
- package/dist/src/workflow.js.map +1 -1
- package/docs/autonomy-guardrails.md +13 -12
- package/docs/decisions.md +8 -0
- package/docs/pdf/codex-workflow-v2-architecture-ru.pdf +0 -0
- package/docs/pdf/codex-workflow-v2-chat-only-guide-ru.pdf +0 -0
- package/docs/pdf/codex-workflow-v2-technical-reference-ru.pdf +0 -0
- package/docs/pdf/sources/codex-workflow-v2-architecture-ru.md +13 -11
- package/docs/pdf/sources/codex-workflow-v2-chat-only-guide-ru.md +14 -13
- package/docs/pdf/sources/codex-workflow-v2-technical-reference-ru.md +20 -16
- package/docs/release.md +6 -4
- package/docs/updating-existing-project.md +12 -9
- package/docs/validation-report.md +70 -75
- package/package.json +1 -1
- package/plugins/codex-workflow-gateway/.codex-plugin/plugin.json +1 -1
- package/plugins/codex-workflow-gateway/references/protocol.md +9 -6
- package/plugins/codex-workflow-gateway/skills/codex-workflow-gateway/SKILL.md +11 -7
|
@@ -109,7 +109,7 @@ command shape or consuming a replacement Discovery. Never rebind, refresh, repla
|
|
|
109
109
|
resume, cancel, or manually replace the historical Task. Continue only after a later P04-B/P05
|
|
110
110
|
package explicitly advertises a topology-preserving replacement capability.
|
|
111
111
|
|
|
112
|
-
When beta.12.
|
|
112
|
+
When beta.12.3 `next` advertises `task stop-override-prepare`, the route is limited to the exact
|
|
113
113
|
beta.11 attempt-four policy stop: two ordinary failures, one corrective failure, a matching
|
|
114
114
|
attempt-3 `continue-fix`, and a matching attempt-4 `stop-escalate` under the unchanged Plan. Invoke
|
|
115
115
|
prepare with the exact Task/Step/revision, explicit human actor, and user-supplied reason. It is
|
|
@@ -120,12 +120,16 @@ evidence changes. Successful apply preserves the original stop, appends
|
|
|
120
120
|
`stop-escalate-overrides.jsonl`, and requires fresh sequential `status` then `next` before attempt
|
|
121
121
|
four runs through the normal strict-review cycle.
|
|
122
122
|
|
|
123
|
-
After an applied override, one ordinary delegated `task context-refresh` may
|
|
124
|
-
canonical Knowledge Map binding.
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
`
|
|
128
|
-
|
|
123
|
+
After an applied override, one or more ordinary delegated `task context-refresh` transitions may
|
|
124
|
+
change only the Plan's canonical Knowledge Map binding. A package update may also advance HEAD, but
|
|
125
|
+
only through the exact `update dependency-provenance-recover` route advertised by fresh `next`.
|
|
126
|
+
Continue only when fresh `next` advertises `task run` with
|
|
127
|
+
`stopOverrideContextRebind.state=validated` for the exact override and stop decision. Core verifies
|
|
128
|
+
the complete source-to-current Plan/audit/rebind chain and, when HEAD changed, every intervening Git
|
|
129
|
+
commit as registered dependency-only provenance. If C1 remains claimed but the lease was lost at
|
|
130
|
+
the Human boundary, first use the simultaneously advertised `task writer-credential-replace`
|
|
131
|
+
action for the exact claimant. A doctor route, semantic Plan drift, an unregistered or non-dependency
|
|
132
|
+
commit, missing delegated authority, a broken chain, or damaged chronology is a hard stop.
|
|
129
133
|
|
|
130
134
|
When `next` returns `milestone initial-assembly`, execution is unavailable. Follow only the
|
|
131
135
|
advertised `linked-task-assembly.commands` (`discovery start` and `discovery materialize`) until all
|