create-agdf 0.4.0 → 0.4.2

package/generated/.github/skills/agdf-runtime-contract.md

@@ -52,6 +52,18 @@ It must not introduce a second gate model or override `agdf-gate-check`, `delive
 
 `quality_outlook` must not unlock gates, imply QA pass, or substitute for missing evidence.
 
+## Delivery Path Search
+
+Delivery Path Search is an optional read-only planning step for high-impact decisions with several materially different next actions.
+
+- It consumes current AGDF state and must reject gate-illegal candidates before model evaluation.
+- It returns one advisory recommendation or `no_safe_recommendation`.
+- It must report budgets, stopping reason and `full | tool_enforced | instruction_only` enforcement.
+- Model scores are judgements, not measurements.
+- Search output is evidence only. Canonical `agdf-gate-check` independently decides what may proceed.
+- The bounded first-release algorithm must not be labelled MCTS.
+- Surface adapters may translate transport and presentation, but must not fork scoring, search or gate semantics.
+
 The field names above are the stable machine-readable contract used by JSON
 reports and automation. Human-facing Markdown must present the same projection
 with readable labels such as `Current gate`, `Allowed now`, `Blocked by`,
@@ -254,6 +266,7 @@ When a run affects project memory or a Context Graph, use:
 - `Situation:` short plain-language summary when the impact is non-trivial
 - `context_graph_impact`: `none | link_only | update_existing_node | new_node_required | sot_drift`
 - `context_graph_refs`
+- `context_graph_reconciliation`: `resolved | not_applicable | open_gap`
 - `context_graph_required_action`: `none | link | update | create | resolve_drift`
 - `context_graph_gate_effect`: `none | warning | revise | block`
 - `context_graph_evidence`
@@ -261,6 +274,17 @@ When a run affects project memory or a Context Graph, use:
 Do not create a new node for a mere version, a general chat summary, or a local observation without a concrete next clean step.
 `sot_drift` must not pass silently as a warning.
 
+### Context Graph Reconciliation
+
+Relevant-run closeout must reconcile Context Graph impact before presenting a clean delivery handoff.
+
+- Use `not_applicable` only when `context_graph_impact: none` and no durable graph knowledge is claimed.
+- Use `resolved` when required graph work is complete and concrete refs are present.
+- Use `open_gap` when graph work remains pending, refs are missing, or a node/update must still be curated.
+- `link`, `update`, `create` and `resolve_drift` require either `resolved` evidence or an explicit `open_gap`.
+- Resolved `link_only`, `update_existing_node` and `new_node_required` states require concrete `context_graph_refs`; `none`, empty refs or vague future-action language are not enough.
+- OR and delivery-closeout must not present commit-ready, release-ready or otherwise clean handoff while `context_graph_reconciliation: open_gap` remains.
+
 ## Control Scaffold
 
 When a repository needs durable AGDF state, use the plugin-local `control/` scaffold as the starting point.

package/generated/.opencode/AGDF.md

@@ -11,6 +11,7 @@ OpenCode project agents do not have a plugin namespace.
 
 Therefore generated OpenCode agent names use the AGDF prefix:
 
+- `agdf-delivery-path-search`
 - `agdf-brownfield-analysis`
 - `agdf-clean-implementation-review`
 - `agdf-code-review`
@@ -48,6 +49,7 @@ Structured Delivery Mode must respect gates, reviews and closeout discipline.
 ## Skill Routing
 | Skill | Use For | Boundary |
 |---|---|---|
+| `agdf-delivery-path-search` | high-impact planning decisions with several plausible next delivery steps before implementation | read-only advisory search; never grants gate permission or replaces gate-check |
 | `agdf-brownfield-analysis` | after gate-check permits Brownfield Review or implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners, risks and Mode/Slice Decision; never bypasses gate-check; Brownfield Review is not implementation permission |
 | `agdf-clean-implementation-review` | inspect workarounds, fallbacks, parallel structures or symptom fixes | not a TP or QA substitute |
 | `agdf-code-review` | mandatory CR step after code changes, focused on defects, regression and security findings | does not replace TP review, clean review or QA |
@@ -105,6 +107,7 @@ For relevant runs that change durable state, code, artefacts or gate status:
 - The generated AGDF agents are `mode: subagent` workflow controls for internal routing. They are not OpenCode Skills under `.opencode/skills/` and are not intended to appear as primary menu agents.
 - The visible user entry point is repository instruction loading plus direct subagent handoff, for example `@agdf-gate-check` for new build/change intent or unclear approval.
 - The AGDF OpenCode plugin is loaded from npm through `opencode.json` `plugin: ["create-agdf"]`.
+- Use `npx --yes @agdf/cli@latest opencode-status --json` to verify global config, package loadability, active session signals and repository surface presence separately.
 - OpenCode permissions keep `edit` and `bash` on explicit approval by default.
 - Shared output and gate rules live in `.opencode/agdf-runtime-contract.md`.
 - Do not paste full control files, templates or artefact bodies into chat unless the user explicitly asks for the full content; summarize and link paths instead.

package/generated/.opencode/README.md

@@ -9,6 +9,8 @@ These files were generated from the AGDF source repository for OpenCode.
 - `.opencode/agents/` contains AGDF subagents generated from the canonical AGDF skills.
 - These files intentionally do not install OpenCode Skills under `.opencode/skills/`; the AGDF agents are background workflow controls, not primary menu agents.
 - Use `@agdf-gate-check` as the visible entry point for new build/change intent or unclear approval.
+- Use `npx --yes @agdf/cli@latest opencode-status --json` to distinguish global hook configuration, package loadability, session activity and this repository surface.
+- Use `npx --yes @agdf/cli@latest gate-check --status-card` for compact interactive gate state; reserve full `--json` output for automation or audit evidence.
 - `.opencode/agdf-runtime-contract.md` is the shared gate and output contract.
 
 ## Agents
@@ -17,6 +19,7 @@ These files were generated from the AGDF source repository for OpenCode.
 - `agdf-clean-implementation-review`
 - `agdf-code-review`
 - `agdf-delivery-closeout`
+- `agdf-delivery-path-search`
 - `agdf-gate-check`
 - `agdf-qa-gate`
 - `agdf-release-or`

package/generated/.opencode/agdf-runtime-contract.md

@@ -52,6 +52,18 @@ It must not introduce a second gate model or override `agdf-gate-check`, `delive
 
 `quality_outlook` must not unlock gates, imply QA pass, or substitute for missing evidence.
 
+## Delivery Path Search
+
+Delivery Path Search is an optional read-only planning step for high-impact decisions with several materially different next actions.
+
+- It consumes current AGDF state and must reject gate-illegal candidates before model evaluation.
+- It returns one advisory recommendation or `no_safe_recommendation`.
+- It must report budgets, stopping reason and `full | tool_enforced | instruction_only` enforcement.
+- Model scores are judgements, not measurements.
+- Search output is evidence only. Canonical `agdf-gate-check` independently decides what may proceed.
+- The bounded first-release algorithm must not be labelled MCTS.
+- Surface adapters may translate transport and presentation, but must not fork scoring, search or gate semantics.
+
 The field names above are the stable machine-readable contract used by JSON
 reports and automation. Human-facing Markdown must present the same projection
 with readable labels such as `Current gate`, `Allowed now`, `Blocked by`,
@@ -254,6 +266,7 @@ When a run affects project memory or a Context Graph, use:
 - `Situation:` short plain-language summary when the impact is non-trivial
 - `context_graph_impact`: `none | link_only | update_existing_node | new_node_required | sot_drift`
 - `context_graph_refs`
+- `context_graph_reconciliation`: `resolved | not_applicable | open_gap`
 - `context_graph_required_action`: `none | link | update | create | resolve_drift`
 - `context_graph_gate_effect`: `none | warning | revise | block`
 - `context_graph_evidence`
@@ -261,6 +274,17 @@ When a run affects project memory or a Context Graph, use:
 Do not create a new node for a mere version, a general chat summary, or a local observation without a concrete next clean step.
 `sot_drift` must not pass silently as a warning.
 
+### Context Graph Reconciliation
+
+Relevant-run closeout must reconcile Context Graph impact before presenting a clean delivery handoff.
+
+- Use `not_applicable` only when `context_graph_impact: none` and no durable graph knowledge is claimed.
+- Use `resolved` when required graph work is complete and concrete refs are present.
+- Use `open_gap` when graph work remains pending, refs are missing, or a node/update must still be curated.
+- `link`, `update`, `create` and `resolve_drift` require either `resolved` evidence or an explicit `open_gap`.
+- Resolved `link_only`, `update_existing_node` and `new_node_required` states require concrete `context_graph_refs`; `none`, empty refs or vague future-action language are not enough.
+- OR and delivery-closeout must not present commit-ready, release-ready or otherwise clean handoff while `context_graph_reconciliation: open_gap` remains.
+
 ## Control Scaffold
 
 When a repository needs durable AGDF state, use the plugin-local `control/` scaffold as the starting point.

package/generated/.opencode/agents/agdf-delivery-closeout.md

@@ -32,6 +32,7 @@ Use `../agdf-runtime-contract.md` for closeout discipline, gate terms, Context G
 4. `Approval: UAT` unlocks an active commit offer when code changes exist.
 5. No commit handoff for runs without code changes.
 6. Always include exactly one next step and one quality outlook.
+7. If OR, QA or current run state reports `context_graph_reconciliation: open_gap`, do not provide a clean commit-ready handoff; set the next step to resolve or explicitly retain the Context Graph gap.
 
 ## When To Use
 - after `QA pass` with code changes
@@ -62,8 +63,10 @@ If code-change status is unclear, do not claim a commit handoff.
    - `uat_approved_with_code`
    - `uat_approved_without_code`
    - `non_delivery_closeout`
-2. Derive Git handoff only when code changes exist.
-3. Set exactly one next delivery step:
+2. Check Context Graph reconciliation from OR, QA, review and current run state.
+3. If reconciliation is `open_gap`, report the delivery status as not cleanly handoff-ready and do not derive commit-ready Git text.
+4. Derive Git handoff only when code changes exist and no unresolved Context Graph gap remains.
+5. Set exactly one next delivery step:
    - offer commit
    - offer push
    - offer PR
@@ -71,13 +74,15 @@ If code-change status is unclear, do not claim a commit handoff.
    - run QA/review
    - obtain UAT/approval
    - perform documentation follow-up
-4. Set quality outlook:
+   - resolve Context Graph gap
+6. Set quality outlook:
    - no further technical follow-up
    - more tests
    - refactoring
    - documentation sharpening
    - monitoring/runtime verification
-5. If `Approval: UAT` exists and code changes were delivered, actively offer the commit but do not run it.
+   - Context Graph reconciliation
+7. If `Approval: UAT` exists, code changes were delivered, and no Context Graph gap remains, actively offer the commit but do not run it.
 
 ## Output
 For code-changing runs:

package/generated/.opencode/agents/agdf-delivery-path-search.md

@@ -0,0 +1,76 @@
+---
+description: high-impact planning decisions with several plausible next delivery steps before implementation
+mode: subagent
+---
+
+# Delivery Path Search
+
+## Purpose
+
+Search a bounded set of possible delivery paths before implementation and return one safest evidence-backed next step.
+
+The search is advisory and read-only. Canonical AGDF `agdf-gate-check` remains the only authority for whether the recommended step may proceed.
+
+## Runtime Contract
+
+Use `../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.
+
+## Trigger
+
+Use only when at least one applies:
+
+- high product, architecture, security, policy, persistence or release impact
+- several materially different next actions are plausible
+- a wrong decision would cause expensive rework
+- the best evidence-gathering or test action is unclear
+
+Skip for routine questions, obvious local fixes and approved implementation with one clear next action.
+
+## Workflow
+
+1. Run AGDF gate-check and inspect durable control state.
+2. Confirm that search is allowed and implementation is not occurring during exploration.
+3. Declare the active surface and its enforcement level.
+4. Invoke the shared CLI runtime:
+
+```bash
+npx --yes @agdf/cli@latest delivery-path-search --surface <surface> --json
+```
+
+5. Treat facts, repository evidence, assumptions and model judgements separately.
+6. Return exactly one recommendation or `no_safe_recommendation`.
+7. Run canonical AGDF gate-check after search. Never translate a recommendation into permission.
+
+## Enforcement
+
+Report exactly one:
+
+- `full`: trusted lifecycle controls prevent writes
+- `tool_enforced`: the evaluator receives read/evaluation tools only
+- `instruction_only`: write prevention is instructional and not technically proven
+
+Do not overstate the surface's guarantee.
+
+## Output
+
+Keep chat output compact:
+
+- recommendation or `no_safe_recommendation`
+- current gate
+- enforcement level
+- decisive evidence and assumptions
+- rejected alternatives and reasons
+- budgets and stopping reason
+- next AGDF gate action
+
+Persist only the redacted decision summary when durable evidence is required. Do not persist raw prompts, hidden reasoning, secrets or source snapshots.
+
+## Boundaries
+
+- This is bounded Delivery Path Search, not MCTS.
+- Do not modify repository files during search.
+- Do not execute evaluator-returned commands.
+- Do not invent default scores for invalid evaluator output.
+- Do not implement, approve or release based on search output.
+- Do not create agent-specific scoring, gate logic or skill copies.
+

package/generated/.opencode/agents/agdf-release-or.md

@@ -44,6 +44,8 @@ Use the Runtime Contract definition of `Relevant Run` to decide whether OR is ma
 10. `CD+Tests` is not completion.
 11. When moving a backlog item to Completed or Superseded, use the canonical human-readable table and link the final OR with a document-relative Markdown link.
 12. Keep machine status normalization in the CLI; do not write internal snake_case status values into the human-facing backlog.
+13. Reconcile Context Graph impact before clean closeout: report `context_graph_reconciliation: resolved | not_applicable | open_gap`.
+14. If Context Graph work remains unresolved, report it as an explicit open gap and do not describe the run as cleanly handoff-ready.
 
 ## When To Use
 - at the end of every relevant run
@@ -89,10 +91,11 @@ If information is missing, state the gap instead of guessing.
 6. Summarize Brownfield fit and solution integrity if reviewed.
 7. Summarize tests and verification.
 8. Summarize documentation and Context Graph impact if relevant.
-9. Name retained fallbacks and exit criteria.
-10. Set exactly one next permissible step.
-11. Set exactly one quality outlook.
-12. State whether `agdf-delivery-closeout` is the next operational handoff step when code changes exist and the delivery state allows it.
+9. Record Context Graph reconciliation as `resolved`, `not_applicable`, or `open_gap`.
+10. Name retained fallbacks and exit criteria.
+11. Set exactly one next permissible step.
+12. Set exactly one quality outlook.
+13. State whether `agdf-delivery-closeout` is the next operational handoff step when code changes exist and the delivery state allows it.
 
 ## Output
 Use a compact structure:
@@ -114,6 +117,7 @@ Use a compact structure:
 ```
 
 When Context Graph impact is relevant, include the fields from `../agdf-runtime-contract.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
 This skill must not:

package/generated/AGENTS.md

@@ -11,6 +11,7 @@ GitHub Copilot repository skills do not have a plugin namespace.
 
 Therefore generated Copilot skill names use the AGDF prefix:
 
+- `agdf-delivery-path-search`
 - `agdf-brownfield-analysis`
 - `agdf-clean-implementation-review`
 - `agdf-code-review`
@@ -48,6 +49,7 @@ Structured Delivery Mode must respect gates, reviews and closeout discipline.
 ## Skill Routing
 | Skill | Use For | Boundary |
 |---|---|---|
+| `agdf-delivery-path-search` | high-impact planning decisions with several plausible next delivery steps before implementation | read-only advisory search; never grants gate permission or replaces gate-check |
 | `agdf-brownfield-analysis` | after gate-check permits Brownfield Review or implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners, risks and Mode/Slice Decision; never bypasses gate-check; Brownfield Review is not implementation permission |
 | `agdf-clean-implementation-review` | inspect workarounds, fallbacks, parallel structures or symptom fixes | not a TP or QA substitute |
 | `agdf-code-review` | mandatory CR step after code changes, focused on defects, regression and security findings | does not replace TP review, clean review or QA |

package/generated/plugins/agdf/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agdf",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
   "author": {
     "name": "AI-native Governance & Delivery Framework",

package/generated/plugins/agdf/control/templates/AGDF_RUN.md

@@ -117,6 +117,7 @@ Keep the active work item traceable. A gate may open only when the previous gate
 
 - context_graph_impact: `none | link_only | update_existing_node | new_node_required | sot_drift`
 - context_graph_refs:
+- context_graph_reconciliation: `resolved | not_applicable | open_gap`
 - context_graph_required_action: `none | link | update | create | resolve_drift`
 - context_graph_gate_effect: `none | warning | revise | block`
 - context_graph_evidence:

package/generated/plugins/agdf/control/templates/artefacts/OR.md

@@ -81,6 +81,7 @@ This is a compact projection of the control state. It does not replace gate-chec
 
 - context_graph_impact: `none | link_only | update_existing_node | new_node_required | sot_drift`
 - context_graph_refs:
+- context_graph_reconciliation: `resolved | not_applicable | open_gap`
 - context_graph_required_action: `none | link | update | create | resolve_drift`
 - context_graph_gate_effect: `none | warning | revise | block`
 - context_graph_evidence:

package/generated/plugins/agdf/meta/agdf-agent-router.md

@@ -12,6 +12,7 @@ Codex and Claude Code already provide the `agdf` plugin namespace.
 Therefore plugin skill names are intentionally unprefixed:
 
 - `gate-check`
+- `delivery-path-search`
 - `brownfield-analysis`
 - `task-plan-review`
 - `clean-implementation-review`
@@ -49,6 +50,7 @@ Structured Delivery Mode must respect gates, reviews and closeout discipline.
 ## Skill Routing
 | Skill | Use For | Boundary |
 |---|---|---|
+| `delivery-path-search` | high-impact planning decisions with several plausible next delivery steps before implementation | read-only advisory search; never grants gate permission or replaces gate-check |
 | `brownfield-analysis` | after gate-check permits Brownfield Review or implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners, risks and Mode/Slice Decision; never bypasses gate-check; Brownfield Review is not implementation permission |
 | `clean-implementation-review` | inspect workarounds, fallbacks, parallel structures or symptom fixes | not a TP or QA substitute |
 | `code-review` | mandatory CR step after code changes, focused on defects, regression and security findings | does not replace TP review, clean review or QA |

package/generated/plugins/agdf/meta/agdf-plugin.definition.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "id": "agdf",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "displayName": "AI Governance & Delivery Framework",
   "developerName": "AI-native Governance & Delivery Framework",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
@@ -61,6 +61,11 @@
     }
   },
   "skillSet": [
+    {
+      "slug": "delivery-path-search",
+      "useFor": "high-impact planning decisions with several plausible next delivery steps before implementation",
+      "boundary": "read-only advisory search; never grants gate permission or replaces gate-check"
+    },
     {
       "slug": "brownfield-analysis",
       "useFor": "after gate-check permits Brownfield Review or implementation preparation, before non-trivial changes in existing systems",

package/generated/plugins/agdf/meta/agdf-runtime-contract.md

@@ -52,6 +52,18 @@ It must not introduce a second gate model or override `gate-check`, `delivery-ma
 
 `quality_outlook` must not unlock gates, imply QA pass, or substitute for missing evidence.
 
+## Delivery Path Search
+
+Delivery Path Search is an optional read-only planning step for high-impact decisions with several materially different next actions.
+
+- It consumes current AGDF state and must reject gate-illegal candidates before model evaluation.
+- It returns one advisory recommendation or `no_safe_recommendation`.
+- It must report budgets, stopping reason and `full | tool_enforced | instruction_only` enforcement.
+- Model scores are judgements, not measurements.
+- Search output is evidence only. Canonical `gate-check` independently decides what may proceed.
+- The bounded first-release algorithm must not be labelled MCTS.
+- Surface adapters may translate transport and presentation, but must not fork scoring, search or gate semantics.
+
 The field names above are the stable machine-readable contract used by JSON
 reports and automation. Human-facing Markdown must present the same projection
 with readable labels such as `Current gate`, `Allowed now`, `Blocked by`,
@@ -254,6 +266,7 @@ When a run affects project memory or a Context Graph, use:
 - `Situation:` short plain-language summary when the impact is non-trivial
 - `context_graph_impact`: `none | link_only | update_existing_node | new_node_required | sot_drift`
 - `context_graph_refs`
+- `context_graph_reconciliation`: `resolved | not_applicable | open_gap`
 - `context_graph_required_action`: `none | link | update | create | resolve_drift`
 - `context_graph_gate_effect`: `none | warning | revise | block`
 - `context_graph_evidence`
@@ -261,6 +274,17 @@ When a run affects project memory or a Context Graph, use:
 Do not create a new node for a mere version, a general chat summary, or a local observation without a concrete next clean step.
 `sot_drift` must not pass silently as a warning.
 
+### Context Graph Reconciliation
+
+Relevant-run closeout must reconcile Context Graph impact before presenting a clean delivery handoff.
+
+- Use `not_applicable` only when `context_graph_impact: none` and no durable graph knowledge is claimed.
+- Use `resolved` when required graph work is complete and concrete refs are present.
+- Use `open_gap` when graph work remains pending, refs are missing, or a node/update must still be curated.
+- `link`, `update`, `create` and `resolve_drift` require either `resolved` evidence or an explicit `open_gap`.
+- Resolved `link_only`, `update_existing_node` and `new_node_required` states require concrete `context_graph_refs`; `none`, empty refs or vague future-action language are not enough.
+- OR and delivery-closeout must not present commit-ready, release-ready or otherwise clean handoff while `context_graph_reconciliation: open_gap` remains.
+
 ## Control Scaffold
 
 When a repository needs durable AGDF state, use the plugin-local `control/` scaffold as the starting point.

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

@@ -32,6 +32,7 @@ Use `../../meta/agdf-runtime-contract.md` for closeout discipline, gate terms, C
 4. `Approval: UAT` unlocks an active commit offer when code changes exist.
 5. No commit handoff for runs without code changes.
 6. Always include exactly one next step and one quality outlook.
+7. If OR, QA or current run state reports `context_graph_reconciliation: open_gap`, do not provide a clean commit-ready handoff; set the next step to resolve or explicitly retain the Context Graph gap.
 
 ## When To Use
 - after `QA pass` with code changes
@@ -62,8 +63,10 @@ If code-change status is unclear, do not claim a commit handoff.
    - `uat_approved_with_code`
    - `uat_approved_without_code`
    - `non_delivery_closeout`
-2. Derive Git handoff only when code changes exist.
-3. Set exactly one next delivery step:
+2. Check Context Graph reconciliation from OR, QA, review and current run state.
+3. If reconciliation is `open_gap`, report the delivery status as not cleanly handoff-ready and do not derive commit-ready Git text.
+4. Derive Git handoff only when code changes exist and no unresolved Context Graph gap remains.
+5. Set exactly one next delivery step:
    - offer commit
    - offer push
    - offer PR
@@ -71,13 +74,15 @@ If code-change status is unclear, do not claim a commit handoff.
    - run QA/review
    - obtain UAT/approval
    - perform documentation follow-up
-4. Set quality outlook:
+   - resolve Context Graph gap
+6. Set quality outlook:
    - no further technical follow-up
    - more tests
    - refactoring
    - documentation sharpening
    - monitoring/runtime verification
-5. If `Approval: UAT` exists and code changes were delivered, actively offer the commit but do not run it.
+   - Context Graph reconciliation
+7. If `Approval: UAT` exists, code changes were delivered, and no Context Graph gap remains, actively offer the commit but do not run it.
 
 ## Output
 For code-changing runs:

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

@@ -0,0 +1,75 @@
+---
+name: delivery-path-search
+description: Use this skill for high-impact planning decisions when several materially different next delivery steps are plausible and comparing scope, risk, evidence, tests, cost and gate readiness would reduce expensive rework. Do not use for routine tasks, during implementation, or as gate permission.
+---
+
+# Delivery Path Search
+
+## Purpose
+
+Search a bounded set of possible delivery paths before implementation and return one safest evidence-backed next step.
+
+The search is advisory and read-only. Canonical AGDF `gate-check` remains the only authority for whether the recommended step may proceed.
+
+## 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.
+
+## Trigger
+
+Use only when at least one applies:
+
+- high product, architecture, security, policy, persistence or release impact
+- several materially different next actions are plausible
+- a wrong decision would cause expensive rework
+- the best evidence-gathering or test action is unclear
+
+Skip for routine questions, obvious local fixes and approved implementation with one clear next action.
+
+## Workflow
+
+1. Run AGDF gate-check and inspect durable control state.
+2. Confirm that search is allowed and implementation is not occurring during exploration.
+3. Declare the active surface and its enforcement level.
+4. Invoke the shared CLI runtime:
+
+```bash
+npx --yes @agdf/cli@latest delivery-path-search --surface <surface> --json
+```
+
+5. Treat facts, repository evidence, assumptions and model judgements separately.
+6. Return exactly one recommendation or `no_safe_recommendation`.
+7. Run canonical AGDF gate-check after search. Never translate a recommendation into permission.
+
+## Enforcement
+
+Report exactly one:
+
+- `full`: trusted lifecycle controls prevent writes
+- `tool_enforced`: the evaluator receives read/evaluation tools only
+- `instruction_only`: write prevention is instructional and not technically proven
+
+Do not overstate the surface's guarantee.
+
+## Output
+
+Keep chat output compact:
+
+- recommendation or `no_safe_recommendation`
+- current gate
+- enforcement level
+- decisive evidence and assumptions
+- rejected alternatives and reasons
+- budgets and stopping reason
+- next AGDF gate action
+
+Persist only the redacted decision summary when durable evidence is required. Do not persist raw prompts, hidden reasoning, secrets or source snapshots.
+
+## Boundaries
+
+- This is bounded Delivery Path Search, not MCTS.
+- Do not modify repository files during search.
+- Do not execute evaluator-returned commands.
+- Do not invent default scores for invalid evaluator output.
+- Do not implement, approve or release based on search output.
+- Do not create agent-specific scoring, gate logic or skill copies.

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

@@ -0,0 +1,5 @@
+# Delivery Path Search
+
+Use this workflow before implementation when competing high-impact delivery paths need an evidence-backed comparison.
+
+It is read-only and advisory. The canonical AGDF gate-check still decides what may happen next.

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

@@ -44,6 +44,8 @@ Use the Runtime Contract definition of `Relevant Run` to decide whether OR is ma
 10. `CD+Tests` is not completion.
 11. When moving a backlog item to Completed or Superseded, use the canonical human-readable table and link the final OR with a document-relative Markdown link.
 12. Keep machine status normalization in the CLI; do not write internal snake_case status values into the human-facing backlog.
+13. Reconcile Context Graph impact before clean closeout: report `context_graph_reconciliation: resolved | not_applicable | open_gap`.
+14. If Context Graph work remains unresolved, report it as an explicit open gap and do not describe the run as cleanly handoff-ready.
 
 ## When To Use
 - at the end of every relevant run
@@ -89,10 +91,11 @@ If information is missing, state the gap instead of guessing.
 6. Summarize Brownfield fit and solution integrity if reviewed.
 7. Summarize tests and verification.
 8. Summarize documentation and Context Graph impact if relevant.
-9. Name retained fallbacks and exit criteria.
-10. Set exactly one next permissible step.
-11. Set exactly one quality outlook.
-12. State whether `delivery-closeout` is the next operational handoff step when code changes exist and the delivery state allows it.
+9. Record Context Graph reconciliation as `resolved`, `not_applicable`, or `open_gap`.
+10. Name retained fallbacks and exit criteria.
+11. Set exactly one next permissible step.
+12. Set exactly one quality outlook.
+13. State whether `delivery-closeout` is the next operational handoff step when code changes exist and the delivery state allows it.
 
 ## Output
 Use a compact structure:
@@ -114,6 +117,7 @@ Use a compact structure:
 ```
 
 When Context Graph impact is relevant, include the fields from `../../meta/agdf-runtime-contract.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
 This skill must not:

package/lib/delivery-path-search/candidate-policy.js

@@ -0,0 +1,34 @@
+import { validateCandidate } from "./contracts.js";
+
+function normalized(value) {
+  return String(value).toLowerCase().replace(/[`*_]/g, "").replace(/\s+/g, " ").trim();
+}
+
+export function candidateLegality(candidateValue, input) {
+  const candidate = validateCandidate(candidateValue);
+  const action = normalized(candidate.action);
+  const forbiddenMatch = input.forbidden_actions.find((item) => {
+    const forbidden = normalized(item);
+    return forbidden && action === forbidden;
+  });
+  if (forbiddenMatch) return { legal: false, reason: `forbidden_by_gate: ${forbiddenMatch}`, candidate };
+
+  const allowedMatch = input.allowed_actions.some((item) => {
+    const allowed = normalized(item);
+    return allowed && action === allowed;
+  });
+  if (!allowedMatch) return { legal: false, reason: "not_in_allowed_actions", candidate };
+  return { legal: true, reason: "allowed_by_current_gate", candidate };
+}
+
+export function candidatesFromInput(input) {
+  return input.allowed_actions.slice(0, input.budgets.max_candidates).map((action, index) => ({
+    id: `candidate-${index + 1}`,
+    action,
+    expected_evidence: input.evidence_refs,
+    tests: [],
+    assumptions: [],
+    depth: 0,
+    parent_id: null,
+  }));
+}