codex-workflow-v2 2.0.0-beta.1 → 2.0.0-beta.10

package/docs/autonomy-guardrails.md

@@ -48,6 +48,9 @@ If the current Plan Risk Audit marks a Step for strict review, `task step-comple
 creates the workflow-owned commit, but the Step stays non-terminal and `next` routes to
 `task step-review`. Canonical completion is recorded only after the strict review and the
 reviewer attestation both bind to that exact completion commit.
+When `next` advertises `task step-review`, pass the exact claimant or required actor as
+`--actor`; the isolated reviewer identity is created inside Core and must not be substituted
+into the mutation actor slot.
 
 Invalid or stale review sidecars fail closed. The workflow blocks downstream acceptance and
 normal continuation when review evidence is malformed, unverified, or commit-mismatched.
@@ -124,6 +127,38 @@ dedicated user-visible Task chat. A Task chat may use internal Worker and Review
 but only its delegate coordinator uses the grant. This prevents one long Milestone context
 from accumulating every implementation and review loop.
 
+The context boundary is literal: a Task chat is a new standalone Codex task created with an
+explicit Task-only prompt, never a fork or handoff of the Milestone chat. Its prompt contains the
+exact repository/Milestone/Task identifiers and fresh Task contract, but no parent transcript,
+sibling Task details, recovery narrative, reasoning trace, or bearer credential. Creation failure
+is a dispatch blocker, not permission to fork. The coordinator verifies one unique mapping from
+each Task ID to its thread and title before work begins.
+
+A host-generated `codex_delegation` envelope containing routing provenance such as
+`source_thread_id` is allowed; it must contain the TaskContextPacket as its complete input and must
+not carry completed parent turns. The coordinator reads the title back after creation and explicitly
+renames it when the supplied title was omitted or normalized.
+
+Chat titles are allocated atomically by the project registry; sidebar counts and `count + 1` are
+not valid numbering sources. Primary forms are:
+
+```text
+#NNN · M<NN> · Coord · <Milestone title> · <MS-ID>
+#NNN · M<NN>/T<NN> · Task · <Task title> · <TASK-ID>
+```
+
+The sequence and membership ordinal come first; the full ID prevents ambiguous identity. Exact
+readback is mandatory and only registry-supplied deterministic fallbacks may be used.
+
+Autonomy also requires active supervision. After just-in-time dispatch, the Milestone coordinator
+keeps a bounded `wait_threads` loop for the routed Task, inspects completion/attention, and verifies
+fresh Workflow `status -> next` before deciding what happened. It resumes a recoverable
+nonterminal Task in the same chat with `send_message_to_thread`; it does not shift ordinary
+implementation questions to the user. The coordinator may stop only for an exact human/semantic
+gate, exhausted infrastructure retry, unrecoverable integrity conflict, a user-requested
+checkpoint, or terminal Milestone closure. A finished chat is not proof of a terminal Task, and a
+child result does not automatically wake a coordinator turn that has already ended.
+
 ## Update boundary
 
 Before changing the exact npm version, run `update preflight`. A compatible update is safe
@@ -151,7 +186,11 @@ current `MSA-*` code. Without that option the ordinary later-message human gate
 ## Bounded Milestone autonomy and C1 handoff
 
 Initial assembly may materialize every linked Task before one complete `milestone plan-set`;
-the Milestone cannot execute until all reverse memberships are classified. Ordinary semantic
+the Milestone cannot execute until all reverse memberships are classified. During that exact
+window `next` returns non-executable `milestone initial-assembly` navigation with explicit
+linked-Task Discovery/materialization options; the closing Plan option appears after the first
+linked Task exists. A failed navigation call must not
+be bypassed with a direct Plan command. Ordinary semantic
 scope change remains explicit and human-only through `milestone scope-change-prepare` and
 `milestone scope-change-apply`.