create-agdf 0.20.2 → 0.30.0

package/generated/.opencode/contracts/modes.md

@@ -161,9 +161,10 @@ Graph Impact, Knowledge Persistence Decision, Closeout):
 - `packages/cli/bin/**`
 - any other executable code file, in any language, anywhere in the repository
 
-A `MASTER_BACKLOG.md` entry is required only when the change is otherwise a "Relevant Run" below. A
-change that is not clearly and fully outside every listed path fails closed to the existing, unchanged
-ceremony — ambiguity is never read as permission for the lighter path.
+No central backlog participates in Run control; inventory derives from current records.
+normal Run operations do not maintain it. Existing Run relevance, approvals and evidence duties
+remain unchanged. Worktree placement is defined solely in task-target-resolution.md.
+
 
 #### Narrow Code-Fix Criterion
 

package/generated/.opencode/contracts/prd-definition.md

@@ -82,7 +82,7 @@ never hand-build an extra approval card or claim missing runtime integration is
 
 The PRD owns exactly one `## Preview Review` section containing only one fenced `json` object.
 Use `schema_version: "1"`, a short lowercase `version` ending in `-vN`, the canonical approved
-`source_ur_digest`, and `entry: ".agdf/control/artefacts/<run_id>/previews/<version>/index.html"`.
+`source_ur_digest`, and `entry: ".agdf/control/runs/<run_id>/evidence/previews/<version>/index.html"`.
 Provide `files` sorted by path, each with `path`, raw-byte SHA-256 `digest`, exact `bytes` and
 `media_type`; also provide `review_task`, nonempty `scenarios`, valid PRD `criterion_ids`, and
 `open_questions` (an array, possibly empty). No other keys or separate manifest are accepted.
@@ -114,12 +114,12 @@ intake true, intake_mode resume, run_id, expected_revision_id and prd_action rev
 Never edit an approved PRD or transfer its approval. An approved-intent change uses the existing
 earliest affected UR/PRD revision route, not this unapproved authoring assignment.
 
-Use the shared Reviewed Recording Input in gate-artifact-preparation and existing
-run-step --step artefact --gate PRD --evidence <recording-input.json> with the supplied current
-run/revision. Record PRD derived_from the exact approved UR; analyses do not replace that source.
+Use the shared reviewed-material contract in gate-artifact-preparation and existing
+run-step --step artefact --gate PRD --evidence <reviewed-PRD.md> --reviewer <name> --reviewed true --update-draft <true|false> with the supplied current
+run/revision and original operation UUID. Record PRD derived_from the exact approved UR; analyses do not replace that source.
 Initial registration uses update_draft false; explicit registered replacement uses true with
-fresh reviewed mapping and recording paths. Retain previous proof/history and other protected
-bytes. Never hand-author receipts, substitute run-update for required source binding or reseal
+fresh reviewed material and inline attestation. Retain previous proof/history and other protected
+bytes. Never hand-author receipts, substitute a hand edit for required source binding or reseal
 unknown edits. Follow existing transaction recovery and supported visible retry with fresh state.
 
 Use the returned revision and redispatch gate-check. When supplied, prepare exact run-present,

package/generated/.opencode/contracts/quality.md

@@ -38,6 +38,12 @@ approval and history records stay with their existing writers and retention rule
 this policy authorizes no deletion or rewriting. Required reviews retain their own
 assessment and accountable owner even when they share evidence.
 
+For Run control, follow the bound typed MCP continuation and operation-contract.
+Authoring inputs, material staging and recording use the existing owners described in
+gate-artifact-preparation.md, section Typed MCP control transport. Local path/validator
+examples are fallback only when the required MCP group is unavailable; they never require
+a shell switch when the current host exposes the corresponding typed operation.
+
 ## Verification Effectiveness And Completion
 
 Derive expected results from approved requirements and domain rules, not copied
@@ -65,7 +71,9 @@ host behavior are distinct evidence classes. Claim savings or compliance only as
 
 ## Quality Readiness Projection
 
-When `qa-gate` authors or refines `QA_REPORT.md`, it uses only the bound absolute plugin-owned
+When `qa-gate` authors or refines `QA_REPORT.md`, it uses the version-matched `QA_REPORT`
+template from bound `authoring-inputs` at the current QA gate. Follow every cursor and preserve
+the manifest/digest binding. CLI fallback uses only the supplied absolute plugin-owned
 `template_path`. Repository scaffold copies are derived review references, not an authoring source.
 An unavailable or unsafe template blocks QA report authoring without mutation or success-shaped
 fallback; it does not turn missing evidence into a QA decision.
@@ -128,7 +136,7 @@ Tool-call batching:
 
 - `RUN_STATE.md` is written once per user gate approval, not once per field change. The
   agent keeps intermediate state in memory between gate approvals and writes the complete
-  updated state in one operation, then records it with `run-update` before the next `gate-check`.
+  reviewed material through its existing typed recording owner before the next `gate-check`.
 - The agent does not `read` existing artefacts for format reference. Skill instructions
   carry the format/structure inline. If a specific existing artefact must be inspected
   for content (not format), the read has no accompanying commentary.

package/generated/.opencode/contracts/request-activation.md

@@ -140,10 +140,9 @@ grant applicability or authority.
     { "operation_id": "status.opencode_repository", "route_family": "repository_status", "target_boundary": "explicit_required", "control_boundary": "absence_is_result", "owner_kind": "function", "owner": "evaluateOpenCodeStatus.repository" },
     { "operation_id": "runtime.checks", "route_family": "global_runtime_lifecycle", "target_boundary": "none", "control_boundary": "no_probe", "owner_kind": "command", "owner": "runtime-checks" },
     { "operation_id": "control.doctor", "route_family": "deterministic_control_inspection", "target_boundary": "required_after_activation", "control_boundary": "missing_is_result", "owner_kind": "command", "owner": "doctor" },
+    { "operation_id": "control.inventory", "route_family": "deterministic_control_inspection", "target_boundary": "required_after_activation", "control_boundary": "missing_is_result", "owner_kind": "command", "owner": "inventory" },
     { "operation_id": "control.delivery_map", "route_family": "deterministic_control_inspection", "target_boundary": "required_after_activation", "control_boundary": "missing_is_result", "owner_kind": "command", "owner": "delivery-map" },
     { "operation_id": "run.create", "route_family": "run_lifecycle", "target_boundary": "required_after_activation", "control_boundary": "command_preconditions", "owner_kind": "command", "owner": "run-create" },
-    { "operation_id": "run.migrate", "route_family": "run_lifecycle", "target_boundary": "required_after_activation", "control_boundary": "command_preconditions", "owner_kind": "command", "owner": "run-migrate" },
-    { "operation_id": "run.render_legacy", "route_family": "run_lifecycle", "target_boundary": "required_after_activation", "control_boundary": "command_preconditions", "owner_kind": "command", "owner": "run-render-legacy" },
     { "operation_id": "continuation.current", "route_family": "active_run_continuation", "target_boundary": "required_after_activation", "control_boundary": "target_run_gate_revalidation", "owner_kind": "function", "owner": "existingTargetRunGateRevalidators" }
   ],
   "derived_operations": [
@@ -178,13 +177,15 @@ route synthesizes an immediate `Approval: UR` merely because a control file is a
 ## Active Run Inventory
 
 "Zeige die aktiven AGDF-Runs in diesem Projekt" / "Show the active AGDF runs in this project"
-selects `control.doctor`, even with gate-check loaded. For "this project", bind its verified chat
+selects `control.inventory`, even with gate-check loaded. For "this project", bind its verified chat
 repository root as `primary_target`, `target_source: current_repository`; cwd alone is not authority.
 Ambiguous or unavailable projects use existing target clarification.
-Call `agdf_inspect` with `operation: doctor`, `all_active: true`, `presentation_language` and actual
-`working_directory`; fallback: surface-local `doctor --dir <verified-root> --all-active --json`.
-Omit run selection, intake and continuation. Show every returned run plus integrity findings.
-Distinguish empty, absent control, incomplete inventory and failure; partial counts are not totals.
+Call `agdf_inspect` with `operation: inventory`, `presentation_language` and actual
+`working_directory`; fallback: surface-local `inventory --dir <verified-root> --json`.
+Omit run selection, intake and continuation. Show every returned open run with title, gate and
+attention class, the history counts and integrity findings. Classes rest on stored run state, not a
+live gate evaluation; say so. Distinguish empty, absent control, incomplete inventory and failure;
+partial counts are not totals. `doctor` with `all_active: true` stays the all-run health check.
 Listing never repairs, initializes or requests approval.
 
 ## Request Applicability Guard
@@ -244,7 +245,7 @@ The requested effect, not discovery, decides AGDF activation.
 A delivery request without a confirmed run binding first dispatches gate-check with intake true
 and no run_id. Its resolve_delivery_run continuation supplies canonical UR scope evidence for the
 coding agent's assignment. One unequivocal same-scope continuation uses resume, its run_id and
-expected_revision_id; a clear independent scope uses new and an unused run_id even when unrelated
+expected_revision_id; a clear independent scope uses new and an unused `run-<original-operation-uuid>` ID even when unrelated
 runs exist. Single-run count, recency, shared files and ambient AGDF_RUN_ID prove no scope match.
 Overlapping plausible scopes require one question about the work, not a technical Run-ID choice.
 Incomplete inventory is a technical failure, never evidence for a new scope. Read-only requests omit intake and

package/generated/.opencode/contracts/sd-definition.md

@@ -72,11 +72,11 @@ gate-check intake true, intake_mode resume, run_id, expected_revision_id and sd_
 (CLI --sd-action revise), exclusive of UR/PRD actions and continue_delivery. Never edit an
 approved design or transfer approvals. Source-intent changes use their existing revision owner.
 
-Use gate-artifact-preparation's shared Reviewed Recording Input with the supplied run/revision:
-run-step --step artefact --gate SD --evidence <recording-input.json>. Record SD-derived_from-PRD
+Use gate-artifact-preparation's shared reviewed-material contract with the supplied run/revision:
+run-step --step artefact --gate SD --evidence <reviewed-SD.md> --reviewer <name> --reviewed true --update-draft <true|false>. Record SD-derived_from-PRD
 from its exact approved source. Initial registration uses update_draft false; permitted explicit
 replacement uses true with fresh mapping/input paths, preserving previous proof/history and
-other protected bytes. No hand-authored receipt, run-update bypass or unknown-edit reseal.
+other protected bytes. No hand-authored receipt, manual reseal bypass or unknown-edit reseal.
 Use supported transaction/recovery with fresh state on failure.
 
 Redispatch gate-check after recording. Prepare its exact run-present when supplied, show returned

package/generated/.opencode/contracts/task-target-resolution.md

@@ -154,3 +154,27 @@ result; it must not resolve targets, derive governance or become a state store.
 Show orientation when target/context separation is material, when the target changes, or when the
 result is unresolved. Avoid redundant presentation for an obvious unchanged target. Presentation
 never grants mutation or gate authority.
+
+## Worktree Placement And Assigned Checkout
+
+When choosing a new worktree for an initiative, use
+`<owning-primary-checkout>/.agdf/worktrees/<initiative>/`. Determine the primary owner from
+Git common-directory/worktree metadata through the existing repository-context/Git boundary;
+a linked checkout's cwd is not the owner. Resolve unclear ownership, unsafe initiative paths
+and destination collisions before creation. Reuse an already assigned worktree for the coherent
+initiative; do not recursively create another worktree inside it. This rule does not require
+worktrees for every trivial task.
+
+Verify that the owning checkout ignores the container before creating a worktree. Preserve an
+existing correct ignore mechanism. Otherwise prepare a contained `.agdf/worktrees/.gitignore`
+with an ignore-all rule for its contents, preserving foreign rules, and verify the destination
+with `git check-ignore`. This is preparation guidance, not permission for an automatic manager
+to create/switch/move/clean worktrees or edit arbitrary ignore files.
+
+Existing locations and explicit user-instructed alternatives remain supported; record the
+assignment/exception rather than moving existing work. One writer continues each Run in its
+assigned checkout; reviewers read only. Path/branch names confer no authority and checkout-path
+target identity does not enforce branch/HEAD binding or cross-checkout locks. Never share or
+symlink control stores. New worktrees do not copy untracked Run artefacts; inventory and preserve
+registered/untracked evidence before separately authorized handoff or cleanup. Global plugins,
+configuration, ports and external services are not isolated by Git worktrees.

package/generated/.opencode/contracts/tp-definition.md

@@ -76,7 +76,7 @@ use their existing source-revision owner. Eligible incomplete-draft correction n
 source/integrity blockers.
 
 Use gate-artifact-preparation's shared language/summary and Reviewed Recording Input procedure:
-run-step --step artefact --gate TP --evidence <input.json> with this run/revision, TP-derived_from-SD,
+run-step --step artefact --gate TP --evidence <reviewed-TP.md> --reviewer <name> --reviewed true --update-draft <true|false> with this run/revision, TP-derived_from-SD,
 update_draft false initially and true for permitted replacement. Retain reviewed derivation, prior
 proof/history and other protected bytes; never hand-author receipts or bypass the checked writer.
 After recording redispatch gate-check for this same run with `continue_delivery: true`

package/generated/.opencode/contracts/ur-definition.md

@@ -1,11 +1,44 @@
 # AGDF Runtime Contract — UR Definition
 
 This contract guides `ur-definition` only after a non-authorizing, bound
-`skill_continuation` with `phase: ur_definition`. It creates no gate or persistence authority.
+`skill_continuation` with `phase: ur_definition` or `phase: planned_ur_definition`.
+The same owner defines UR content in both modes. It creates no gate or persistence authority.
 
-## Binding and ownership
+## Planning mode before a Run
 
-Use only the returned governance_target, run_id, revision_id, artifact_path and template_path.
+For explicit capture/refinement/priority intent, dispatch this same skill with the confirmed
+target and `planning: {plan_id, expected_digest}`. Use null digest for capture and an inspected
+canonical digest for replacement. Planning is mutually exclusive with Run/revision, delivery
+intake, continue_delivery and source-revision selectors. Do not enter Run assignment to save a
+planned need. The optional planning plugin orchestrates this mode; Core owns its semantics.
+
+Follow `phase: planned_ur_definition` only. Read every returned authoring-inputs page for the
+version-matched UR template, current source and `planning_capability`. Use the same need,
+clarification, preview, language and summary rules below. An incomplete draft remains saveable
+with clarification open. Planning stops at UR and minimal metadata: never author planned PRD,
+SD or TP, present a gate, collect Approval: UR or infer delivery permission.
+
+Use `agdf_record/planned_material.stage` for one UR, then `planned_ur.create` or
+`planned_ur.replace` with that exact planning scope and original mutation UUID. Choose the new
+identity as `plan-<mutation UUID>` without asking the user for an identifier. Creation material
+contains the ordinary UR template without planning scalar fields: Core adds exactly one initial
+`Planning schema: planned-ur-v1`, `Planning id: <plan_id>` and `Planning priority: high|normal|low`.
+Default normal applies only on explicit create. Replacement preserves schema/identity and
+changes priority in that same UR source under its expected digest; no saved parallel title/status.
+No Run-bound material, generic file writer, shell fallback or copied template is permitted.
+
+Return the saved readable title, source reference/digest, priority and remaining clarification.
+Completeness/priority/selection never starts delivery. Only a later explicit request to start from
+the selected current source uses `agdf_run/run.create_from_planned`; read its contract and preserve
+the original UUID after uncertainty. The handoff creates one unapproved Run for normal UR review.
+A different UUID on an already transferred identity returns that Run. Historical planning source
+is read-only afterwards; later product edits use the active Run's existing revision owner.
+Inspect the original operation before retry. Missing/incompatible Core, unsafe/stale source,
+pending recovery or ambiguous origins stop the affected action with concrete diagnosis.
+
+## Run mode binding and ownership
+
+For `phase: ur_definition`, use only the returned governance_target, run_id, revision_id, artifact_path and template_path.
 template_path is the absolute, version-matched template owned by the installed plugin runtime.
 Repository copies under `.agdf/control/templates/` are derived scaffold references and never
 override this authoring source. Read the template without rewriting it; persist only artifact_path.
@@ -42,7 +75,7 @@ Preserve the requirement and name a concrete recovery or obtain an explicit scop
 cannot be delivered. Record the responsible later UX/PRD step in Next Step; UR authoring still
 writes only its assigned UR, not a preview or product implementation. A requested before-PRD preview
 is created through UX intent clarification under the existing post-UR routing owner. Its durable
-output belongs to `.agdf/control/artefacts/<run_id>/previews/` for the bound run; the UX skill owns
+output belongs to `.agdf/control/runs/<run_id>/evidence/previews/` for the bound run; the UX skill owns
 creation, versioning, evidence and references. An inline chat rendering alone does not fulfill that
 run deliverable. In a new UR, set exactly one initial metadata line before the first section:
 `Preview requirement: before_prd_interactive` for a required interactive before-PRD preview,
@@ -79,15 +112,16 @@ For new-format URs, a missing or invalid required summary returns to this same a
 route before presentation. Correct it through the existing revision writer; no user approval
 is required merely to complete an unapproved incomplete draft.
 
-## Revision and recording
+## Run mode revision and recording
 
 A new draft is recorded through existing run-step --step ur --title <short title>, using
 --dir <governance_target> --run <run_id> --revision <revision_id>.
 For an already registered unapproved draft, require explicit user revision intent. Resume
 through gate-check with intake true, intake_mode resume, run_id, expected_revision_id and
 ur_action revise (CLI --ur-action revise). Ordinary intake of a ready draft still presents it.
-After editing a registered draft use existing run-update, not run-step: the previous seal
-must be replaced by the canonical revision writer. Never edit an approved UR or its approval.
+Stage the replacement and use ur_draft.replace with the current binding. The writer
+publishes the document and typed evidence atomically. Never edit bound bytes, reseal
+an unknown change or alter an approved UR or its approval.
 Use the returned new revision, redispatch gate-check for this target/run, prepare the fresh
 run-present when supplied, show its returned text verbatim and wait for a NEW deliberate
 `Approval: UR`. Previous presentations/replies cannot approve a changed draft.

package/generated/.opencode/skills/agdf-brownfield-analysis/SKILL.md

@@ -49,9 +49,10 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `brownfield-analysis`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `brownfield-analysis`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill brownfield-analysis`, language and working directory.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
 Quote shell values as data.
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
@@ -59,8 +60,10 @@ On skill_continuation use only its target/control. Without that tool and a valid
 or help retries. Dispatch never authorizes.
 
 Brownfield-specific output must make evidence, missing existing-system view, parallel-structure risk, reuse strategy, and the minimal next step visible.
-When `.agdf/control/` is present, persist or link `post_ur_review` output under `.agdf/control/artefacts/<key>/BROWNFIELD_REVIEW.md`,
-then record the Mode/Slice Decision with the validator's `run-step --step route --route <mode> --reason --evidence`.
+When `.agdf/control/` is present, persist or link `post_ur_review` output under `.agdf/control/runs/<run_id>/documents/BROWNFIELD_REVIEW.md`,
+then use the bound MCP continuation: stage the reviewed material and record the Mode/Slice
+Decision through `agdf_record/step.record` (step `route`). Only when that group is unavailable,
+use the supplied validator's `run-step --step route --route <mode> --reason --evidence`.
 
 ## Modes
 
@@ -198,7 +201,7 @@ Use a concise structure:
 - decision: pass | revise | block | not_applicable
 - mode_slice_decision: quick_task | verified_change | structured_slice | structured_delivery | block
 - required_next_gate: none | PRD | SD | TP | Brownfield Analysis
-- artefact: .agdf/control/artefacts/<key>/BROWNFIELD_REVIEW.md | none
+- artefact: .agdf/control/runs/<run_id>/documents/BROWNFIELD_REVIEW.md | none
 - scope:
 - evidence:
 - transparency: why later artefacts are skipped, shortened or required

package/generated/.opencode/skills/agdf-clean-implementation-review/SKILL.md

@@ -46,9 +46,10 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `clean-implementation-review`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `clean-implementation-review`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill clean-implementation-review`, language and working directory.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
 Quote shell values as data.
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.

package/generated/.opencode/skills/agdf-code-review/SKILL.md

@@ -45,9 +45,10 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `code-review`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `code-review`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill code-review`, language and working directory.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
 Quote shell values as data.
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
@@ -112,7 +113,8 @@ Use this compact structure:
 
 ```text
 ## Code Review
-Record the decision with the validator's `run-step --step review --decision <pass|revise|block> --evidence`.
+Stage the actual report and record through bound `agdf_record/step.record` (step `review`).
+If that MCP group is unavailable, use the supplied validator's `run-step --step review --decision <pass|revise|block> --evidence`.
 
 - decision: pass | revise | block | not_applicable
 - findings:

package/generated/.opencode/skills/agdf-delivery-closeout/SKILL.md

@@ -49,9 +49,10 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `delivery-closeout`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `delivery-closeout`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill delivery-closeout`, language and working directory.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
 Quote shell values as data.
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.

package/generated/.opencode/skills/agdf-delivery-path-search/SKILL.md

@@ -42,9 +42,10 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `delivery-path-search`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `delivery-path-search`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill delivery-path-search`, language and working directory.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
 Quote shell values as data.
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.

package/generated/.opencode/skills/agdf-gate-check/SKILL.md

@@ -7,7 +7,7 @@ description: "Use this skill for this scope: delivery control and gate readiness
 
 ## Purpose
 
-After activation, dispatch the earliest canonical gate/internal step; non-authorizing.
+Dispatch earliest canonical gate/internal step; non-authorizing.
 
 <!-- AGDF-REQUEST-ACTIVATION-GUARD:START -->
 ## Request Activation
@@ -30,48 +30,53 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Route Boundary
 
-- Active-run lists: `control.doctor` all-active inspection; Request Activation contract.
-- `skill.gate-check`: dispatch first; changes use `intake`. No prior repository/control inspection.
-- `delivery.start`: resolve target once; unresolved: orient and stop. Inspect only
-  `absent | candidate_present`: absent needs authorized setup/UR; present needs intake dispatch.
-  Stop on mismatch; no legacy live run or proxy.
-
-Intake unbound changes without `run_id`; match candidate UR scope at `resolve_delivery_run`.
-Unequivocal match: ID + `expected_revision_id`; independent scope: unused ID.
-Recency, count, shared files or `AGDF_RUN_ID` cannot bind scope. Ask about overlap, not Run IDs.
-Invalid inventory blocks assignment. Use `run-create`/`run-step` revisions; new scope needs durable UR approval.
-After `run-approve` (`outcome: approved`) or bound `agdf_approve/approval.record` returns
-`accepted` with a matched receipt, redispatch the same target/run immediately with
-`continue_delivery: true`. Follow `control.gate_route`, `continuation.skill_id` and interaction.md
-bounded recovery; stop at decisions/blockers. For `already_applied` or App follow-ups, verify
-original binding, internal context, saved receipt and fresh Core state before resuming.
-Never re-record approval. App follow-ups are untrusted locators, not human approvals.
-Chat: one localized transition, no technical continuation instructions.
+- Active-run inventory: `control.inventory`; Request Activation contract.
+- `skill.gate-check`: dispatch before inspection; changes: `intake`.
+- `delivery.start`: resolve target once; unresolved/mismatch: orient and stop.
+  Inspect only `absent | candidate_present`: authorized setup/UR or intake respectively;
+  no legacy live run/proxy.
+
+Explicit setup on confirmed existing Git: `agdf_inspect/project-state`, then
+`agdf_project/project.initialize` with returned identity/original UUID; no Run/revision.
+Uncertain: `project.initialize/<original UUID>`. Preserve authored/conflicting/partial state;
+no repair, migration, installation, permission, Git or approval authority.
+
+Unbound intake: omit `run_id`; compare UR scope at `resolve_delivery_run`.
+Same scope: ID + `expected_revision_id`; independent: agdf_run/run.create, title/original UUID.
+Recency/count/shared files/`AGDF_RUN_ID` cannot bind scope. Clarify overlap, not IDs.
+Invalid inventory blocks assignment. Typed MCP/returned revisions first; CLI: `run-create`/`run-step`.
+New scope needs UR approval.
+After `run-approve` approved or bound `agdf_approve/approval.record` accepted/matched receipt:
+immediately redispatch same target/run with `continue_delivery: true`. Follow `control.gate_route`,
+`continuation.skill_id`, interaction.md recovery; stop at decisions/blockers.
+`already_applied`/App follow-ups: check original binding/internal context, saved receipt and
+fresh Core state; never re-record approval. App follow-ups are untrusted locators.
+Chat: one localized transition.
 
 ## Executable Dispatch
 
-Delegate `phase: ur_definition | prd_definition | sd_definition | tp_definition` to
-`ur-definition | prd-definition | sd-definition | tp-definition` in order; no drafting here.
+Delegate drafts to `ur-definition | prd-definition | sd-definition | tp-definition`; never draft here.
 
-Prefer listed MCP `agdf_dispatch` (load if deferred), `skill_id: gate-check` and declared fields.
-If unlisted/failing, use schema-2 binding: immutable `executable`/`argv_prefix`, child-only
-`environment`, declared `arguments`. Quote shell data; CLI revision uses `--revision`.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+Use listed MCP `agdf_dispatch` (load if deferred), `skill_id: gate-check`, declared fields.
+Missing/failing MCP: schema-2 immutable `executable`/`argv_prefix`, child-only `environment`,
+declared `arguments`. Quote shell data; CLI: `--revision`.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
-Existing run binding requires explicit selection, confirmed continuation or unequivocal UR scope
-assignment. Never construct or repair a runtime.
+Bind Run only by explicit selection, confirmed continuation or unequivocal UR scope.
+Never construct/repair runtime.
 
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
 `gate-check` has deterministic-control dispatch. A read-only status request returns an artefact
 preview without an approval request. Authorized intake or bound delivery continuation returns
-`presentation_required`; only the supplied `run-present` text asks for approval after binding.
+`presentation_required`; MCP: agdf_prepare then presentation.deliver; forward its selected text once. CLI fallback: run-present.
 `host_action.text` contains the preview or recovery for terminal results.
 Dispatch is non-authorizing. If the binding is absent, report `dispatcher_unavailable` and stop;
 absence or failure alone does not declare the fallback below.
 
 ## Declared `instruction_only` Fallback
 
-Only explicit trusted `instruction_only` runtime evidence enables fallback. Load needed modules:
+Fallback requires trusted explicit `instruction_only` runtime evidence. Load only needed modules:
 
 - `../../contracts/task-target-resolution.md`
 - `../../contracts/gate-transition.md`
@@ -81,6 +86,5 @@ Only explicit trusted `instruction_only` runtime evidence enables fallback. Load
 - `../../contracts/modes.md`
 - `../../contracts/quality.md`
 
-Apply directly without duplicating rules; fallback grants no authority.
-`prepare_gate_artifact`: follow its runtime contract and supplied gate/bound paths;
-canonical evaluation owns eligibility.
+Apply without duplication/authority. `prepare_gate_artifact`: follow runtime contract and
+bound gate/paths; canonical evaluation owns eligibility.

package/generated/.opencode/skills/agdf-prd-definition/SKILL.md

@@ -35,9 +35,10 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `prd-definition`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `prd-definition`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill prd-definition`, language and working directory.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
 Quote shell values as data.
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.

package/generated/.opencode/skills/agdf-qa-gate/SKILL.md

@@ -51,9 +51,10 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `qa-gate`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `qa-gate`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill qa-gate`, language and working directory.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
 Quote shell values as data.
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.

package/generated/.opencode/skills/agdf-release-or/SKILL.md

@@ -56,9 +56,10 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `release-or`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `release-or`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill release-or`, language and working directory.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
 Quote shell values as data.
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
@@ -66,9 +67,11 @@ On skill_continuation use only its target/control. Without that tool and a valid
 or help retries. Dispatch never authorizes.
 
 OR-specific output must make gate status, delivered and intentionally not delivered content, missing approvals, missing evidence, risks, retained fallbacks, and the next permissible step visible.
-When `.agdf/control/` is present, persist or link the OR under `.agdf/control/artefacts/<key>/OR.md` and reference it from the selected canonical `RUN_STATE.md` or `MASTER_BACKLOG.md` when it is steering-relevant.
+When `.agdf/control/` is present, persist or link the OR under `.agdf/control/runs/<run_id>/documents/OR.md` and reference it from the selected canonical `RUN_STATE.md` when it is steering-relevant; no central backlog update is required.
 Use the Runtime Contract definition of `Relevant Run` to decide whether OR is mandatory or whether a Quick Task mini-closeout is enough.
-Close a `quick_task` with the validator's `run-step --step closeout --result --evidence --risk --next`.
+Close a `quick_task` through bound `agdf_closeout/closeout.record`, preserving its exact
+confirmation and original UUID. If that MCP group is unavailable, use the supplied
+validator's `run-step --step closeout --result --evidence --risk --next`.
 
 ## Rules
 1. OR is always allowed and mandatory for relevant runs as defined in the Runtime Contract.
@@ -86,7 +89,7 @@ Close a `quick_task` with the validator's `run-step --step closeout --result --e
 13. Keep machine status normalization in the CLI; do not write internal snake_case status values into the human-facing backlog.
 14. Reconcile Context Graph impact before clean closeout: report `context_graph_reconciliation: resolved | not_applicable | open_gap`.
 15. If Context Graph work remains unresolved, report it as an explicit open gap and do not describe the run as cleanly handoff-ready.
-16. After writing or updating `MASTER_BACKLOG.md`, run `agdf_inspect` with `operation: doctor` when the host lists it, otherwise `doctor --json` (or the locally available equivalent) and resolve any `AGDF_BACKLOG_STATUS_UNKNOWN` or `AGDF_BACKLOG_ARTEFACT_LABEL_UNKNOWN` finding before closeout. See the AGDF control scaffold's `MASTER_BACKLOG.md` template Rules section for the canonical status/artefact label vocabulary.
+16. Preserve optional legacy backlog information without new synchronization or locks. Check the selected Run and registered closeout evidence through the existing doctor/gate owners; legacy-only diagnostics cannot veto unrelated valid Run work. Explicit supported recovery alone may finish an old journal's already-recorded backlog output.
 17. When Delivery Map exposes `parent_reconciliation`, report that evaluated object without
     rediscovering or reclassifying the relationship. Keep Child completion and Parent coordination
     visibly separate. An `open` result retains exactly one next action and does not invalidate Child

package/generated/.opencode/skills/agdf-sd-definition/SKILL.md

@@ -36,9 +36,10 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `sd-definition`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `sd-definition`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill sd-definition`, language and working directory.
-For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete.
+For `--language`: Required; apply the same current-request selection and locale validation.
 `target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
 Quote shell values as data.
 For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.