create-agdf 0.20.2 → 0.31.0

package/generated/submissions/openai/agdf/meta/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/submissions/openai/agdf/meta/contracts/tp-definition.md

@@ -69,6 +69,14 @@ not independent proof of human provenance. Table headings may use levels two thr
 
 ## Recording and revision
 
+A returned bound authoring continuation for an incomplete own unapproved draft already
+selects its correction route. Consume its authoring-inputs/material_call/recording_calls
+forms directly and use the supplied update_draft value. Do not dispatch this author again
+or add another intake for that same snapshot. The *_action revise route below is only for
+NEW editing intent on an already READY draft, and uses skill_id gate-check, never an author
+skill ID or a host skill alias. After saving, follow the returned continuation once.
+
+
 A ready draft without new editing intent is presented unchanged. Explicit ready-draft revision uses
 gate-check intake true, intake_mode resume, exact run_id/expected_revision_id and tp_action revise
 (CLI --tp-action revise), exclusive of other source actions and continue_delivery. Approved changes
@@ -76,7 +84,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/submissions/openai/agdf/meta/contracts/ur-definition.md

@@ -1,15 +1,48 @@
 # 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.
-A direct invocation first dispatches ur-definition; without a bound run follow the existing
+An already returned bound `ur_definition` continuation satisfies entry: consume its authoring inputs and writer forms directly. Do not repeat author dispatch or intake for that same snapshot. A direct invocation without such a continuation first dispatches ur-definition; without a bound run follow the existing
 resolve_delivery_run assignment, then gate-check intake/resume with its expected_revision_id.
 Never use AGDF_RUN_ID, cwd, discovery or a previous approval as authority. Missing, stale,
 foreign, invalid or approved bindings require fresh control routing; do not write.
@@ -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,
@@ -71,7 +104,7 @@ follows its current-request language contract and does not change the artefact l
 
 Before recording a complete draft, when `approval_summary_required` is true, include exactly
 one `## <approval_summary_heading>` section using the supplied heading verbatim. Write a
-complete summary in the resolved presentation language covering problem, goal, affected users,
+complete summary in the resolved presentation language. Read `approval_summary_format.required_fields` from authoring-inputs: those exact list field declarations need concrete authored values; prose or a heading alone is not a named field. Cover problem, goal, affected users,
 scope, non-goals, acceptance signals, source ownership, risks/unknowns and next step.
 Do not truncate decision-relevant content or use ellipses. The existing approval renderer's
 limits and validation apply. This summary is editorial; the UR remains authoritative.
@@ -79,15 +112,20 @@ 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.
+When this bound continuation returns a registered, incomplete unapproved draft, correct its
+readiness gaps directly through the supplied `ur_draft.replace` form. The existing authoring
+route already covers completing that same need; do not open another intake or dispatch.
+A deliberate change to an already READY registered draft outside that continuation still
+requires explicit user revision intent: enter via 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. Never substitute a field named revision.
+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/submissions/openai/agdf/meta/copilot-payload-baseline.json

@@ -1,7 +1,7 @@
 {
   "schema_version": 1,
   "profile_id": "copilot-runtime-plugin",
-  "max_files": 397,
-  "max_bytes": 3522791,
-  "rationale": "Approved risk-based-test-strategy-20261027-01 central quality policy, SD/TP contract delivery, templates and review guidance. Final consistent QA detail guidance adds 9 bytes to the first measured candidate: +13330 from 3509461, 397 files/3522791 bytes. Preserve exclusions, permissions and instruction budgets; zero headroom."
+  "max_files": 457,
+  "max_bytes": 4791833,
+  "rationale": "AGDF 0.31.0 adds 257 bytes for the required release catalogue entry. Exact generated payload with no reserve."
 }

package/generated/submissions/openai/agdf/meta/distribution-profile-history.json

@@ -148,6 +148,20 @@
       "profile_id": "runtime-plugin",
       "entry_digest": "1b194df6abf5de884b4d69ab38cde567b5c28674f392ef853678800e05de7e65",
       "status": "supported"
+    },
+    "0.30.0": {
+      "contract_id": "five-profile-v1",
+      "provenance_schema_version": 1,
+      "profile_id": "runtime-plugin",
+      "entry_digest": "05a4645b92ab7f33c40ae676f7e92c95f618b86e3fc031684cfbac8bf6b21ce6",
+      "status": "supported"
+    },
+    "0.31.0": {
+      "contract_id": "five-profile-v1",
+      "provenance_schema_version": 1,
+      "profile_id": "runtime-plugin",
+      "entry_digest": "d3a3b0a1fc9e3312cb8a9437a4acf8ba99a563b2dab665b38feec8e2257e4f23",
+      "status": "supported"
     }
   }
 }

package/generated/submissions/openai/agdf/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "agdf",
-  "version": "0.20.2",
+  "version": "0.31.0",
   "description": "Control layer for governed AI-assisted delivery.",
   "author": {
     "name": "Arndt Gold",

package/generated/submissions/openai/agdf/skills/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/submissions/openai/agdf/skills/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/submissions/openai/agdf/skills/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/submissions/openai/agdf/skills/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/submissions/openai/agdf/skills/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/submissions/openai/agdf/skills/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:
 
 - `../../meta/contracts/task-target-resolution.md`
 - `../../meta/contracts/gate-transition.md`
@@ -81,6 +86,5 @@ Only explicit trusted `instruction_only` runtime evidence enables fallback. Load
 - `../../meta/contracts/modes.md`
 - `../../meta/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/submissions/openai/agdf/skills/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/submissions/openai/agdf/skills/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/submissions/openai/agdf/skills/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/submissions/openai/agdf/skills/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.

package/generated/submissions/openai/agdf/skills/task-plan-review/SKILL.md

@@ -48,9 +48,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` `task-plan-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` `task-plan-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 task-plan-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/submissions/openai/agdf/skills/tp-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` `tp-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` `tp-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 tp-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/submissions/openai/agdf/skills/ur-definition/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ur-definition
-description: "Use this skill for this scope: bound UR drafting, clarification or revision. Boundary: content only; preserves approved intent. The requested effect, not discovery, decides AGDF activation."
+description: "Use this skill for this scope: UR drafting in planning scope or a bound Run. Boundary: content only; no start or approval authority. The requested effect, not discovery, decides AGDF activation."
 ---
 
 # ur-definition
@@ -34,9 +34,15 @@ Then pick one catalog route; non-authorizing, downstream checks remain.
 
 ## Executable Dispatch
 
-Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `ur-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` `ur-definition`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+For deliberate pre-Run planning, pass the confirmed `planning` scope instead of `run_id`.
+Use `plan-<future mutation UUID>` and null expected digest for capture, or the inspected
+plan identity/current digest for refinement. No delivery intake/continue/revision fields.
+Follow only `phase: planned_ur_definition`, shared template/contract and planning-scoped typed
+writers. Missing compatible Core stops before mutation; no CLI/shell writer or Run-assignment fallback.
 If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill ur-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.
@@ -51,4 +57,6 @@ review timing in the UR; creation belongs to the later bound analytical step.
 Set the initial `Preview requirement` metadata according to the UR contract; a required
 interactive before-PRD preview uses `before_prd_interactive`, otherwise `none`.
 Write only the supplied unapproved UR, preserving uncertainty and explicit human approval.
-After canonical recording, redispatch gate-check; use its fresh presentation and wait.
+In Run mode, after canonical recording redispatch gate-check; use its fresh presentation and wait.
+In planning mode, report the saved draft, source and remaining questions without requesting a
+gate approval. Only a later explicit selected-source start request uses the Core handoff contract.