create-agdf 0.20.2 → 0.30.0

package/generated/submissions/openai/agdf/meta/contracts/interaction.md

@@ -1,5 +1,23 @@
 # AGDF Runtime Contract — Interaction
 
+## MCP preferences and complete inputs
+
+The versioned meta/agdf-defaults.json and adjacent schema own shipped preferences; the existing
+.agdf/control/config.json is the sole project override. Explicit valid call/request > confirmed
+project > plugin applies to chat_language, artifact_language, presentation_route and gate_check_variant.
+Missing optional preferences inherit; present invalid recognized settings are actionable errors.
+Defaults never activate missing/incomplete control or write/repair configuration. Locale packs and
+contract constants retain their existing owners.
+
+MCP may omit presentation_language when the resolved preference matches the current request;
+otherwise send its explicit BCP 47 override. CLI --language and complete Core input remain explicit.
+Seven command groups may omit schema_version/assurance, and presentation.deliver may omit route.
+Only inspect gate-check inherits variant. Current native adapters still require explicit working_directory;
+omission without private trustworthy task context fails before effect. No target/process/plugin-directory guess.
+All authority/state/reply bindings remain explicit. Existing inspect/help shows effective values/source;
+no extra routine configuration call is needed. Original-operation snapshots and immutable presentations
+retain their bound values after preference changes; existing replay/recovery stays the only owner.
+
 ## Run Status Card
 
 When a run needs an operational status view, use the Run Status Card as a compact projection of existing control state.
@@ -7,7 +25,7 @@ It must not introduce a second gate model or override `gate-check`, `delivery-ma
 
 - `mode`: `quick_task | verified_change | structured_delivery | unknown`
 - `run_id`: the exactly selected canonical run
-- `presentation_language`: the resolved complete locale-pack tag; a valid unsupported requested tag resolves to the registry's deterministic `en` pack, while a missing or invalid dispatch value fails before this card exists and an incomplete or invalid registry fails closed
+- `presentation_language`: the resolved complete locale-pack tag; a valid unsupported requested tag resolves to the registry's deterministic `en` pack, while an invalid explicit value fails; omitted MCP language resolves from confirmed-project/plugin preferences before this card exists and an incomplete or invalid registry fails closed
 - `status`: `open | blocked | pass | warn | revise | block | in_progress`
 - `current_gate`: current user gate or internal step
 - `mode_slice_decision`: `undecided | quick_task | verified_change | structured_slice | structured_delivery | block`
@@ -83,7 +101,7 @@ requires fresh evaluator eligibility and carries the evaluated record scope and
 missing Git observations retain their concrete refusal. Inspect current evidence before resuming and
 perform only unfinished obligations. Applicable completed Quick Task CR or executed Verified Change
 routes `compact_closeout` to release-or: Quick Task uses existing OR-lite recording, Verified Change
-uses its linked Mini-Closeout and existing run-update boundary, never unsupported closeout.record.
+uses its linked Mini-Closeout through the current typed recording/closeout owner and exact confirmation.
 Completed Runs stay terminal. No persistent execution marker or exactly-once guarantee is added.
 
 When a bound authorized continuation corrects one missing relationship from exact previously
@@ -159,13 +177,13 @@ template:
 
 This narration is temporally and structurally separate from the Gate Transition Card:
 
-- The Gate Transition Card is **pre-approval** (in the orientation envelope); it is
-  subjunctive and contains the exact `Approval:` value.
+- The prepared decision is **pre-approval**; its one Markdown document contains the
+  effect and exact `Approval:` value. Historical Gate Transition Cards remain audit projections.
 - The narration is **post-acceptance** (after the gate advanced); it is indicative and
   does not contain the `Approval:` value.
 - Both never appear in the same assistant message.
 - The narration does not repeat the decision's effect (the card's job) and uses its own
-  template, not the card's three-question form.
+  template, without repeating the prepared decision summary.
 - For internal steps (Brownfield Review, Brownfield Analysis), the narration states what
   the agent does next and that no user action is required, without exposing
   `next_user_gate: none` or asking for a second approval.
@@ -186,116 +204,15 @@ compact human card collapses internal sub-states to stable human labels:
 all raw values unchanged.
 
 
-## Gate Transition Card
-
-Every ready `gate_approval` uses one fixed visible sequence: first the compact
-approval-time Run Status Card, then the Gate Transition Card, then exactly one
-native question or exact-text fallback. Both cards derive from one immutable,
-non-authorizing presentation snapshot produced after canonical selected-run,
-gate and durable-artefact readiness evaluation. The snapshot never selects a
-run, decides a gate, persists state or grants approval.
-
-The two distinct card blocks form one Approval Orientation Envelope in one
-immediately preceding assistant message. The agent must complete that message
-before invoking any native question tool or emitting an exact-text approval
-request. Splitting the cards across separate assistant turns or invoking the
-tool after only one card is a failed interaction, not a valid presentation.
-
-The first visible line of that envelope is the localized neutral decision title
-of the current user gate, rendered as a level-two Markdown heading or equivalent
-accessible host heading inside the compact approval-time Run Status Card.
-`AGDF Status`, `Run Status Card`, `Gate Transition Card`, raw gate identifiers
-and machine values are semantic or diagnostic labels only and must not become
-the primary heading. Approval-directed titles such as `Approve solution design`
-are also invalid. The decision title appears exactly once and does not replace,
-merge or reorder either required card block.
-
-The compact approval-time Run Status Card contains exactly five operational
-fields: selected run, readiness status, current gate, a localized human-readable
-required decision and one neutral instruction to choose approve, request revision
-or decline. It does not contain the exact approval value or quality outlook. It uses localized human-readable labels
-and must not contain evidence, diagnostic codes, raw control-state keys,
-allowed/forbidden inventories or machine values. The complete Run Status Card remains the operational,
-CLI and audit projection. Every ready-gate presentation renders the complete operational Run Status Card exactly once, between the compact approval-time Run Status Card and the Gate Transition Card, consumed verbatim from the code-owned status presentation; when it is undeliverable, the localized status-presentation failure line with its concrete diagnostic codes takes its place and the decision is still requested.
-The exact-approval once-only requirement applies to the compact approval-time Run Status Card and the Gate Transition Card only; the complete Run Status Card may carry the missing approval as audit data.
-
-The first scan across both cards reveals the requested decision, readiness,
-required approval, approval effect, remaining boundary and next transition.
-Identity and artefact references provide supporting context without competing
-with that sequence. Across the two cards, the exact `Approval: <GateName>` value
-appears exactly once, in the Gate Transition Card. The later native prompt or
-exact-text request may repeat it only as the required input.
-
-The canonical `interaction-presentation.js` owner builds and validates one
-immutable snapshot, then renders both complete Markdown blocks and the approval
-interaction. The public additive `approval_presentation` schema contains
-`schema_version`, selected run/revision/gate/locale identity, fixed sequence,
-both rendered blocks, canonical prompt/options/exact-text fallback and
-`authorizes: false`. It is a valid object only for a ready user gate and `null`
-otherwise. Agents and surface adapters transmit these blocks without rebuilding
-headings, fields, ordering, locale copy or Markdown.
-
-The Gate Transition Card is the second orientation message. It is derived from
-the same snapshot and canonical post-approval transition, but it is not another
-state model, persisted record, renderer or approval authority. It turns only
-the decision-relevant subset into concise product copy immediately before the
-host-native question or exact-text fallback.
-
-The card answers exactly three user questions, in this order:
-
-1. **Where am I?** A localized human-readable gate title, deterministic human
-   run title, selected `run_id` as secondary context, compact `UR · PRD · SD · TP`
-   artefact links and a clear ready-for-decision state.
-2. **What does this decision do?** The exact `Approval: <GateName>` value, its
-   concrete next outcome and the most important boundary that remains.
-3. **What happens next?** The immediate agent-controlled action and the next
-   actual user decision when one exists; otherwise a plain statement that no
-   further user action is required now.
-
-Use this compact composition:
+## Prepared decision presentation
 
-```text
-<localized gate title> · <human run title> · `<run_id>`
-<UR link or localized missing text> · <PRD link or localized missing text> · <SD link or localized missing text> · <TP link or localized missing text>
-<localized ready-for-decision line>
+Current presentation records use version 6. The existing run-presentation owner renders one immutable Markdown decision document: neutral title, one complete source-authored/localized summary, decision effect, one exact Chat decision route and supporting version/source identity. Never repeat the summary as a brief plus details, append operational cards or add another questionnaire. The separate companion string is a short location/title/version pointer without a copied summary or decision question. The document reader returns these exact prepared Markdown bytes; source artefacts remain separately available through bound authoring-input reads. Older versions retain their original envelope/snapshot/approval proof; do not regenerate historical bytes.
 
-<localized approve heading>
-`Approval: <GateName>` <localized concrete effect>. <localized remaining boundary>.
+Preparation is not display or delivery. With MCP, agdf_prepare/presentation.prepare opens no UI and returns a typed presentation.deliver continuation. Ordinary delivery immediately selects full_markdown and returns the whole prepared Markdown once. An optional agdf_decision_view opens only a labelled non-primary read-only preview of the same document. Its live view may acknowledge exact rendered bytes, current visibility, server nonce, owner epoch and independently bound current-surface identity through the scoped view channel. A model-supplied boolean, client name/version, UI advertisement or action qualification is insufficient. The current SDK adapter supplies no trustworthy current-surface identity, so it cannot claim confirmed UI delivery.
 
-<localized next heading>
-<localized immediate agent action>. <localized next user decision or no-action statement>.
-```
-
-Resolve all AGDF-owned explanatory text through the canonical Interaction
-Locale Registry. `en` and `de` are initial reviewed packs, not a closed locale
-list. A valid unsupported requested locale uses the complete English pack. Missing or invalid
-external dispatch input fails before governance evaluation; internal rendering without a
-request-specific language supplies explicit `en`. An incomplete or invalid registry fails closed.
-Gate identifiers, `run_id`, canonical paths and exact
-approval values are never translated. The visible gate title is localized;
-for example, the German title may be `Lösungsdesign` while the authorization
-value remains `Approval: SD`. Meaning, ordering and authority boundaries are
-identical across locale packs.
-
-The Gate Transition Card must not be a Markdown table or dashboard. It must not
-present raw control-state keys, machine status values, diagnostic codes,
-evidence lists, allowed/forbidden inventories or implementation detail that is
-not needed for the decision. It must not repeat the native question. The card
-normally fits in one title, one readiness line and two short content blocks.
-Run and gate identity may appear in both cards to anchor the shared snapshot;
-status rows, action inventories and transition prose must not be duplicated.
-
-For `Approval: TP`, the effect is permission to run pre-implementation
-Brownfield Analysis, implementation remains gated until that analysis passes,
-and the next block states plainly that no further user decision is required
-now. Brownfield Analysis must not be presented as a user gate.
-
-If snapshot validation or rendering fails, emit no partial card and forbid native
-invocation. Perform a fresh gate evaluation. Show only the localized exact-text
-request when the same gate remains ready and the canonical approval value is
-independently valid. Otherwise report the current non-ready reason and request no
-decision. Never patch, guess or model-reconstruct missing presentation content.
+presentation.deliver selects ui_primary only for a fresh matching live confirmation from that current surface. Chat then receives only the pointer. Otherwise it retires the probe and selects full_markdown. Selection is monotonic: late/foreign observations cannot change Markdown or restore a primary view. Replay returns historical delivery status without another summary/question. Explicit fallback first removes UI primary status/actions and retires the view, then returns the exact Markdown. Expiry, teardown, navigation and source changes invalidate view authority. Retained offline pixels cannot prove current display or reading. Readable but action-unqualified UI has disabled buttons and the exact Chat route. Display and delivery never constitute intent, approval, host qualification or release authority.
 
+The operational Run Status Card and Gate Transition Card remain deterministic read/audit projections. They are not additional blocks in the current prepared decision document. Historical format descriptions and locale fields do not require duplicating them in version 6.
 
 ## Native Interaction Contract
 
@@ -370,14 +287,12 @@ selected owner observed; it never supplies request applicability, target authori
 gate permission.
 
 Before presenting `gate_approval` for any user gate (`UR`, `PRD`, `SD`, `TP`,
-`QA`, or `UAT`), the agent must emit the compact localized Run Status Card and
-the localized Gate Transition Card as two distinct blocks in that order within
-one immediately preceding assistant message. Neither card is optional, hidden
-in the question text or replaced by a host button label. Do not invoke the
-native question tool until the complete two-card envelope is visible. Native
-buttons or exact-text fallback may appear only after both cards. Render the two
-cards once per eligible attempt; an unavailable or not-applied native control
-proceeds to exact text without repeating them.
+`QA`, or `UAT`), prepare the exact selected Run/revision and deliver the single
+Markdown decision document above. Confirmed current UI receives that document
+with only its short Chat pointer; every other case receives full Markdown in Chat.
+Operational status and historical transition cards are separate read/audit views;
+never prepend them to this decision or repeat its summary or question. Optional
+native controls must preserve this same document and deliberate decision authority.
 
 ### Approval Summary Source and Completeness
 
@@ -445,7 +360,7 @@ Before presenting `gate_approval`, the agent must:
 
 1. resolve exactly one selected run;
 2. run the canonical gate evaluation and confirm that the current gate's durable artefact is present and ready;
-3. first execute `run-present --run <run_id> --gate <gate> --revision <revision_id>`; retain its presentation_id and show its exact returned text. A `presentation_required` dispatch result may already carry the same preview as `presentation.semantic_block: approval_preview` with identical `summary_digest`; the agent may show it, but asks the gate question only after `run-present` returned a `presentation_id`. This contains the complete deterministic or embedded localized summary, bound by `summary_digest`, and a clickable link to the exact durable artefact with its digest, run, gate and revision; UAT summarizes and lists its existing evidence rows. Missing or invalid summary material makes presentation unavailable and returns a targeted non-authorizing recovery. This explicit writing operation prepares a binding but never proves human visibility. Then forward the exact single decision presentation for the current surface. Show purpose, proposed change, consequences, material risks and exact document access before one approving action/formula. Keep technical identity in details. Do not append another status/transition card or approval questionnaire; ordinary discussion stays in Chat;
+3. with available MCP use agdf_prepare/presentation.prepare followed by presentation.deliver as specified above; stop after forwarding the selected text. CLI/unsupported-host fallback: first execute `run-present --run <run_id> --gate <gate> --revision <revision_id>`; retain its presentation_id and show its exact returned text. A `presentation_required` dispatch result may already carry the same preview as `presentation.semantic_block: approval_preview` with identical `summary_digest`; the agent may show it, but asks the gate question only after `run-present` returned a `presentation_id`. This contains the complete deterministic or embedded localized summary, bound by `summary_digest`, and a clickable link to the exact durable artefact with its digest, run, gate and revision; UAT summarizes and lists its existing evidence rows. Missing or invalid summary material makes presentation unavailable and returns a targeted non-authorizing recovery. This explicit writing operation prepares a binding but never proves human visibility. Then forward the exact single decision presentation for the current surface. Show purpose, proposed change, consequences, material risks and exact document access before one approving action/formula. Keep technical identity in details. Do not append another status/transition card or approval questionnaire; ordinary discussion stays in Chat;
 4. wait for deliberate user input without a timeout, default, preselection, hook-supplied answer or agent-to-agent substitute;
 5. re-run canonical gate evaluation against the same `run_id` and expected gate immediately before persistence;
 6. reject missing evidence, ambiguous or wrong run, wrong gate, stale state and any response that is no longer valid;
@@ -457,6 +372,11 @@ Before presenting `gate_approval`, the agent must:
    work even when it awaits evidence, approval, or repair; it is not evidence that a previous gate was
    approved. Stop at the next decision or blocker in the same turn. Do not wait for “continue”.
 
+A run closure follows the same deliberate-reply rule without being a gate approval. Show the
+returned `run-close` or `closure.preview` text verbatim, wait for the owner's reply and apply only
+with that verbatim reply as the confirmation; the agent never supplies `Close runs: <preview_id>`
+itself, and the receipt records the same cooperative assurance as an approval.
+
 For a ready `gate_approval`, interaction kind and native capability are separate. Evaluate callability,
 deliberate wait safety and canonical approval-value transport before invocation. `native_attempt_required`
 is true only when current evidence proves `exact_option_value` or `separate_label_and_value` transport
@@ -686,7 +606,7 @@ For one same-scope match redispatch intake_mode resume with run_id and expected_
 the inventory. The dispatcher rechecks target, active lifecycle, integrity and revision before gate
 presentation or continuation. A changed assignment returns fresh evidence for comparison; it does
 not silently adopt the newer scope or another run. Missing or invalid inventory blocks assignment
-and never becomes a no-match result. For a clear independent scope with no match use intake_mode
+and never becomes a no-match result. A new intake uses `run-<original-operation-uuid>` as its prospective ID. The current `run-create --title ... --operation <uuid>` command derives that exact ID; arbitrary named Run creation is unsupported. For a clear independent scope with no match use intake_mode
 new and an unused run_id, even when unrelated runs exist, without asking the user to select an ID
 or authorize bookkeeping again. If plausible scopes overlap, ask one focused question about the
 requested work; do not offer a technical Run-ID choice. Status and explicit run-selection requests
@@ -744,14 +664,11 @@ remains an explicit evidence gap; do not silently install, reconnect or claim co
 
 ### Bound native and remote Chat delivery
 
-The existing Core presentation owner returns one source-authored decision brief and the complete
-validated summary. Only a qualified native card actually displayed on this current request surface supports `presentation_delivery.mode: native_plus_chat`: show the native card and forward one independently decidable private Chat summary, announcing either its approval button or the exact gate formula. A capability advertisement, emitted resource, render-only card or Mac-only display does not prove current or iPad visibility. Unconfirmed/unsupported surface receives the complete `full_chat` decision once, with no invisible-button instructions. Later optional native opening uses the same presentation; it creates no second request or authority. Never append
-another approval questionnaire, status card or technical transition dump to this decision moment.
-Rendering support, App-action qualification and current business eligibility remain separate.
+Use the version-6 prepared decision delivery contract above. Rendering support, observed current-surface display, primary delivery, action qualification, current eligibility and human intent are separate states. Never infer an opened current card from capability or qualification, or copy the full summary into its Chat pointer.
 
 When the human asks “Dokument lesen” / “Read document”, use existing `agdf_inspect` operation
 `presentation-document` with the returned target/Run/gate/revision/presentation binding. Deliver
-the exact original-language bytes as complete ordered chunks, following every `next_cursor` and
+the exact prepared Markdown bytes as complete ordered chunks, following every `next_cursor` and
 showing completeness and version provenance. Do not replace it with the current filesystem file,
 a paraphrase or a Mac-only link. Discussing or reading never decides. If exact remote material or
 synchronized Chat access is unavailable, explain that limitation and do not invite blind approval.

package/generated/submissions/openai/agdf/meta/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/submissions/openai/agdf/meta/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/submissions/openai/agdf/meta/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/submissions/openai/agdf/meta/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/submissions/openai/agdf/meta/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/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

@@ -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/submissions/openai/agdf/meta/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/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": 453,
+  "max_bytes": 4717872,
+  "rationale": "PR #50 integration follow-up: fresh canonical initialization seeds no shared Backlog in either layout; historical v4 material recovery has an explicit legacy fixture. Exact generated Copilot closure: 453 files / 4717872 bytes (-112 from 7aff94dc), no reserve; time, schema and safety limits unchanged."
 }

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

@@ -148,6 +148,13 @@
       "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"
     }
   }
 }

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.30.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