create-agdf 0.8.7 → 0.9.0

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

@@ -13,7 +13,11 @@ The search is advisory and read-only. Canonical AGDF `gate-check` remains the on
 
 ## Runtime Contract
 
-Use `../../meta/agdf-runtime-contract.md` for canonical gate state, output discipline and Delivery Path Search boundaries. This skill must not maintain a second gate or scoring model.
+Use these focused runtime-contract modules:
+
+- `../../meta/contracts/control-scaffold.md`
+- `../../meta/contracts/gate-transition.md`
+- `../../meta/contracts/quality.md`
 
 ## Trigger
 

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

@@ -18,8 +18,14 @@ Determine the earliest blocking user approval gate and derive:
 This skill must not create later artefacts such as PRD, SD, TP, CD, CR, QA, or UAT when the gate does not allow them.
 
 ## Runtime Contract
-Use `../../meta/agdf-runtime-contract.md` for gate terms, closeout discipline, and non-duplication rules.
-The canonical gate order and transition model live only in the Runtime Contract. This skill evaluates the current state against that model; it must not maintain a second complete gate table.
+Use these focused runtime-contract modules:
+
+- `../../meta/contracts/gate-transition.md`
+- `../../meta/contracts/interaction.md`
+- `../../meta/contracts/control-scaffold.md`
+- `../../meta/contracts/modes.md`
+- `../../meta/contracts/quality.md`
+The canonical gate order and transition model live only in `../../meta/contracts/gate-transition.md`. This skill evaluates the current state against that model; it must not maintain a second complete gate table.
 
 ## Agent-Native Control Path
 
@@ -69,7 +75,7 @@ For a ready `gate_approval`:
 7. Distinguish internal process steps from user decisions in natural language. For example, after `Approval: TP`, say that pre-implementation Brownfield Analysis runs next and that no further user action is required now; do not expose `next_user_gate: none` or `user_action_required: no`, and do not ask for a second approval for Brownfield Analysis.
 8. Ask exactly one question that names the selected `run_id` and `current_gate`.
 9. Offer options in stable order: exact `Approval: <GateName>`, localized revise and localized decline. Add explicit cancel only where supported after decline; otherwise host dismissal maps to cancel. Never preselect, skip, auto-submit or reorder an option.
-10. Use the surface adapter declared in the canonical plugin definition only when it can wait for deliberate input without auto-resolution; otherwise request the same exact approval in concise text.
+10. Use the surface adapter declared in the canonical plugin definition only when it can wait for deliberate input without auto-resolution and can transport `exact_option_value` or `separate_label_and_value`; never invoke a `decorated_label_only` adapter. Otherwise request the same exact approval in concise text.
 11. Render both cards once in that single complete assistant message. Never merge, reverse, omit or duplicate them; the action heading does not replace either card. If the native attempt is unavailable or not applied, continue to exact text without repeating either card.
 12. Re-run gate evaluation for the same run and expected gate after the response and immediately before persistence.
 13. Reject a missing artefact, ambiguous or wrong run, wrong gate, stale expected gate, timeout/default, hook-supplied answer, agent message, technical permission outcome or plan approval.
@@ -88,7 +94,7 @@ For the transition card, use the complete resolved locale pack. The initial Germ
 
 The primary option is derived exactly as `Approval: <GateName>` from the evaluated current gate; only explanatory copy and non-authoritative outcome labels are localized. Concrete localized copy belongs to the user-facing interaction layer or the approved delivery artefact, not to English runtime rules.
 
-Make exactly one native-attempt for the ready gate. If the host does not render,
+Make exactly one native-attempt for the eligible ready gate. If the host does not render,
 apply or safely return the native question on that attempt, switch immediately
 to the exact textual approval. Do not ask the user to request the buttons again
 and do not create a retry loop or simulated control.
@@ -102,7 +108,7 @@ only after fresh run/gate/artefact revalidation; never retry automatically.
 
 Surface behavior:
 
-- Codex: invoke the native short-question/request-user-input control on the first eligible attempt when callable, ask one gate question and omit auto-resolution; if it is not rendered or applied, use exact text immediately.
+- Codex: invoke the native short-question/request-user-input control only when preflight proves `exact_option_value` or `separate_label_and_value`, and omit auto-resolution. The canonical `decorated_label_only` capability must use exact text without invoking the adapter. `Approval: <GateName> (Recommended)` is never a valid option or approval.
 - Claude Code: invoke `AskUserQuestion` on the first eligible attempt only when no timeout can auto-continue and no hook supplies `answers` or `updatedInput`; if it is not rendered or applied, use exact text immediately. Claude permissions and `ExitPlanMode` remain separate.
 - OpenCode: use built-in `question` when permitted. Preserve explicit `permission.question` denial and use exact text in that case. `once`, `always`, `reject` and auto mode never become gate input.
 - Other, unavailable or non-interactive surfaces: use exact textual approval and wait for a new explicit user response.
@@ -232,6 +238,7 @@ from the same snapshot and are shown exactly once.
 
 If this skill creates or updates control artefacts, do not paste full file bodies into the chat.
 List paths, summarize the decision, name the blocker or approval needed, and keep the durable content in the files.
+See the Runtime Contract §Chat and Tool-Call Discipline for tool-call batching and skill output compaction rules.
 
 ## Forbidden
 This skill must not:

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

@@ -22,7 +22,11 @@ It answers:
 - whether blockers, critical risks, or missing evidence remain
 
 ## Runtime Contract
-Use `../../meta/agdf-runtime-contract.md` for Quality Contract output, Context Graph fields, gate terms, and non-duplication rules.
+Use these focused runtime-contract modules:
+
+- `../../meta/contracts/quality.md`
+- `../../meta/contracts/context-graph.md`
+- `../../meta/contracts/gate-transition.md`
 
 QA-specific `decision` is exactly `pass | revise | block`.
 `pass` is allowed only when TP coverage, Brownfield fit, solution integrity, and relevant documentation/Context Graph impact are sufficiently evidenced.
@@ -100,7 +104,13 @@ Use this shape:
 - impact_codes:
 ```
 
-If Context Graph impact is relevant, include the fields from `../../meta/agdf-runtime-contract.md`.
+If Context Graph impact is relevant, include the fields from `../../meta/contracts/context-graph.md`.
+
+### Compact Chat Output
+
+At `pass`: one line — `QA: pass — <one-line summary>`. Reference the durable QA report
+path. Do not show the Quality Readiness projection or evidence inventory in chat.
+At `revise`/`block`: show the decisive dimension, reason and next action.
 
 ## Decision Guidance
 - `pass`: required TP tasks are done, evidence is strong, no blocking Brownfield or solution-integrity risk remains.

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

@@ -25,7 +25,12 @@ It reports:
 - whether further quality follow-up or a separate delivery closeout is useful
 
 ## Runtime Contract
-Use `../../meta/agdf-runtime-contract.md` for Quality Contract output, Context Graph fields, gate terms, and non-duplication rules.
+Use these focused runtime-contract modules:
+
+- `../../meta/contracts/closeout.md`
+- `../../meta/contracts/quality.md`
+- `../../meta/contracts/context-graph.md`
+- `../../meta/contracts/control-scaffold.md`
 
 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.
@@ -118,7 +123,7 @@ Use a compact structure:
 - quality_outlook:
 ```
 
-When Context Graph impact is relevant, include the fields from `../../meta/agdf-runtime-contract.md`.
+When Context Graph impact is relevant, include the fields from `../../meta/contracts/context-graph.md`.
 Include `context_graph_reconciliation` whenever Context Graph impact is present. If the value is `open_gap`, required next step must resolve or explicitly retain that gap before commit-ready or release-ready handoff.
 
 ## Forbidden

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

@@ -19,7 +19,11 @@ For each relevant task, this skill determines:
 This skill provides TP coverage. It is not the final QA decision.
 
 ## Runtime Contract
-Use `../../meta/agdf-runtime-contract.md` for Quality Contract output, Context Graph fields, gate terms, and non-duplication rules.
+Use these focused runtime-contract modules:
+
+- `../../meta/contracts/quality.md`
+- `../../meta/contracts/context-graph.md`
+- `../../meta/contracts/gate-transition.md`
 
 TP-specific output must evaluate every relevant `task_id` with completion status, AC coverage, evidence, missing evidence, and QA-relevant gaps.
 If `context_graph_required_action` is not `none`, the affected task is complete only if follow-up, evidence, or an intentionally open gap is visible.
@@ -105,6 +109,11 @@ Evidence confidence:
 - `medium`
 - `low`
 
+### Compact Chat Output
+
+At `pass`: one line — `TP Review: pass — <X>/<total> tasks fully_done`.
+At `revise`/`block`: show incomplete tasks with missing evidence.
+
 ## Forbidden
 This skill must not:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-agdf",
-  "version": "0.8.7",
+  "version": "0.9.0",
   "description": "Bootstrap AGDF repository-local plugin files, Copilot/OpenCode instructions, skills, control files and machine-readable checks.",
   "type": "module",
   "files": [