codex-workflow-v2 2.0.0-beta.12.9 → 2.0.0-beta.13.1

package/README.md

@@ -32,12 +32,38 @@ automation do not import anything from the parent V1 project.
   the rejected Plan, and exact dirty bytes can be adopted by one newly authorized owning Step;
 - bounded first-failure Plan-integrity recovery for legacy/in-flight contradictions that could not
   be rejected by the current pre-authorization feasibility gate;
+- beta.12.17 Plan-integrity update transport accepts any coherent exact beta.12 source from .11 up
+  to the current runner, provided declared, locked, installed, Task-branch, and Milestone-base
+  versions agree; this removes the release-specific source-version literal without weakening the
+  dirty-worktree, lease, transaction, or dependency-only commit boundary;
+- beta.12.18 preserves historical check-support decisions against the Plan that produced them and
+  recognizes one exact post-rebind Plan that explicitly adopts every previously derived support
+  path; the same dependency-only transport can therefore resume the stranded Task without a Human
+  approval, retroactive evidence mutation, or implicit scope carry-over;
+- beta.13 replaces secret-bearing CLI credentials with host-safe local references, atomically
+  records failed-Step continuation while preserving dirty bytes, and routes continuation by stable
+  mechanical/reviewer causes instead of attempt count. It also validates transitive component
+  owners and derives explicit production-edge obligations from multi-Step `runtime-composition`
+  PRA classifications before authorization, publishes a Signal-observed route-class
+  catalog with explicit action-level witness status, defaults `status` to a bounded projection, prepares isolated reviewer runtime evidence,
+  and requires an explicit ordinary/security review mode;
+- beta.12.19 closes the previous execution-boundary gap: after dependency registration, Knowledge
+  rebind, PRA and authorization, `next` and `task run` share one fail-closed authority for adopting
+  the exact registered dirty set. HEAD, Plan/rebind chain, file list, content hash, historical event
+  and current Step scope must all match; any byte or scope drift routes to `doctor`;
+- beta.12.16 check-support authority: migration checksum/catalog modules imported directly by an
+  approved check must be owned by the producing Step; an already-running Step receives only the
+  exact machine-proved support path without a Human replan or a synthetic second failure;
 - read-only Milestone progress projection with stable membership ordinals and replacement links;
 - one project-monotonic `#NNN` chat registry with compact titles, exact readback, and deterministic fallback;
 - narrow, read-only alpha.6 strict-review rescue preflight for the lifecycle deadlock fixed in alpha.7;
 - optional time-bound delegated approval with project/Milestone/Task scope and an explicit audit trail;
 - one bounded Milestone Autonomy Contract for approvals, guarded content-only context refresh,
   and membership-only Task-graph evolution;
+- audited remediation topology for an unstarted Task whose current Plan Risk Audit records
+  `stop-escalate`: Core may append exactly one upstream Task, inherit the blocked Task's exact
+  merged dependency frontier, and derive replacement Milestone/Task authority without a new
+  human approval while preserving outcome, success signal, acceptance, and checks;
 - bounded recovery of one previously passed and accepted Step commit omitted by a corrective Plan,
   without rewriting Git history or adopting the old Step into the replacement Plan;
 - Milestones aggregate already merged Tasks on the base branch, without an integration branch;
@@ -51,7 +77,7 @@ cross-machine synchronization are not part of its contract.
 Node.js 22 or newer is required. Consumers pin the exact package version:
 
 ```bash
-npm install --save-dev --save-exact codex-workflow-v2@2.0.0-beta.12.9
+npm install --save-dev --save-exact codex-workflow-v2@2.0.0-beta.13.1
 npx codex-workflow gateway handshake --repo .
 npx codex-workflow doctor --repo .
 ```
@@ -215,16 +241,19 @@ historical remediation event. An identical retry is idempotent. After recovery,
 the historical attempt is interpreted as `corrective`, but no attempt-count hard stop is
 created: after any required Knowledge refresh, `next` may continue the same failed Step.
 
-For a legacy authorization without P01-A evidence, or a contradiction that genuinely becomes
-observable only after execution starts, the first guarded `checks-failed` event may cause `next` to advertise
-`task plan-integrity-recover` instead of an identical retry. The route is deliberately narrow:
-the current Step must contain an exact root `npm run <script>` check, that script must be absent
-from the current root `package.json`, and `package.json` must be outside the Step's
-`allowedWrites`. Core binds the current Task revision, Plan, failed remediation event, Step
-definition, Git HEAD, manifest hash, and complete dirty-file set. The recovery records an early
-`replan-required` decision and then reuses the existing corrective-yield plus human-confirmed,
-journaled corrective-replan path. It does not edit the Plan, run a second failing attempt, widen
-`allowedWrites`, or modify the worktree.
+For a legacy authorization without current mechanical evidence, or a contradiction that genuinely
+becomes observable only after execution starts, the first guarded `checks-failed` event may cause
+`next` to advertise `task plan-integrity-recover` instead of an identical retry. Missing scripts and
+missing required selectors retain the existing evidence-bound `replan-required` route. beta.12.16
+adds one narrower outcome for a direct imported checksum/catalog authority: when an absent declared
+migration output is writable by the Step, the check runner directly imports a tracked immutable
+support module, that module contains approved SHA/catalog anchors for the same output family, every
+dirty file remains inside the original Step scope, and the support module is outside both the
+original `allowedWrites` and `forbiddenScope`, Core records an append-only `continue-fix` authority
+for that exact support path. The Task keeps the same Plan hash and implementation bytes; subsequent
+run, commit and sealed-review packets use the effective scope and disclose the derived authority.
+Any semantic Plan change, indirect/dynamic check, unrelated dirty path, forbidden path, missing
+hash anchor or ambiguous import remains fail-closed and uses the ordinary corrective path.
 
 When an active downstream proof exposes a required change in files owned by a completed transitive
 predecessor Step, fresh `next` advertises `task downstream-proof-recover` instead of the impossible
@@ -289,7 +318,12 @@ success signal, acceptance, checks, discovery, and base branch remain cryptograp
 Pass `--delegation-grant` only when the same `next` response exposes an exact eligible
 `delegatedApprovalOptions` entry for that transition. Ordinary C1 handoff, claim, run,
 step-complete, step-review, merge, and sync-base do not inherit a Milestone approval grant.
-Adoption apply and semantic scope changes stay human-only. Revocation is immediate for future
+Adoption apply and arbitrary semantic scope changes stay human-only. The bounded
+`milestone remediation-materialize` route is not a generic delegated scope change: it is admitted
+only by a current `stop-escalate` audit, keeps Milestone semantics byte-for-byte unchanged, appends
+one required remediation Task, and adds only the blocked Task dependency edge. Its
+`corrective-derived` authority covers execution authorization and final acceptance of current
+required Tasks; final Milestone acceptance remains unchanged. Revocation is immediate for future
 uses. The original human path remains available and unchanged.
 
 ## Milestone autonomy and alpha.6 rescue
@@ -348,13 +382,21 @@ alpha regressions that must not recur are tracked in the
 - [Chat-only development guide](docs/pdf/codex-workflow-v2-chat-only-guide-ru.pdf)
 - [Deep technical reference](docs/pdf/codex-workflow-v2-technical-reference-ru.pdf)
 
-These beta.12.7 documents cover delegated Discovery, Milestone Autonomy Contract issuance,
+These beta.13 documents cover delegated Discovery, Milestone Autonomy Contract issuance,
 dependency-aware Task routing, C1 credential handling, external-sealed reviews, bounded
-Plan-integrity recovery, Task-local dependency provenance recovery, the human-confirmed legacy
+Plan-integrity recovery (including repeated selector-contract failures), pre-authorization
+selector feasibility, Task-local dependency provenance recovery, the human-confirmed legacy
 attempt-four stop override (including append-only multi-rebind, dependency-only HEAD continuation,
 evidence-accounted post-audit recovery revisions), both downstream-proof update bridges, exact
-dirty-worktree carryover into a replacement Step, and the P04-A
-structural-replacement stop boundary. Their reviewable
+dirty-worktree carryover into a replacement Step, audited additive remediation topology with
+corrective-derived Task authority, its atomic dependency-only Knowledge refresh without a Human
+approval gap, the atomic beta.12.11-to-beta.12.12 dirty-worktree update bridge, separate source/target
+Knowledge bindings for corrective replan, exact consecutive dependency-update carryover, historical
+corrective-yield journal continuity, atomic recovery of multiple consecutive unregistered
+dependency-only updates after a failed package transition, and the P04-A
+structural-replacement stop boundary. They also cover beta.13 host-safe credentials, atomic
+failed-Step continuation, cause-bound rolling refinement, structural production-edge admission,
+bounded status and prepared ordinary/security review. Their reviewable
 sources live in [`docs/pdf/sources`](docs/pdf/sources), and `npm run docs:pdf:check` proves the
 tracked binaries were generated from the current source and package version. The PDFs remain
 human-facing artifacts; the Markdown documents above, bundled gateway, schemas, and runtime code