create-agdf 0.4.6 → 0.4.8

package/bin/create-agdf.js

@@ -9,6 +9,7 @@ import process from "node:process";
 import { searchInputFromControl } from "../lib/delivery-path-search/state-adapter.js";
 import { runDeliveryPathSearch } from "../lib/delivery-path-search/search-engine.js";
 import { codexEvaluator } from "../lib/delivery-path-search/evaluators/codex.js";
+import { claudeEvaluator } from "../lib/delivery-path-search/evaluators/claude.js";
 import { fixtureEvaluator } from "../lib/delivery-path-search/evaluators/protocol.js";
 import { enforcementForSurface } from "../lib/delivery-path-search/surfaces/capabilities.js";
 import { persistSearchResult } from "../lib/delivery-path-search/persistence.js";
@@ -175,6 +176,7 @@ Preferred AGDF CLI:
   npx --yes @agdf/cli@latest doctor
   npx --yes @agdf/cli@latest gate-check --json
   npx --yes @agdf/cli@latest delivery-path-search --surface codex --json
+  npx --yes @agdf/cli@latest delivery-path-search --surface claude --json
 
 Scaffold-compatible npm create usage:
   npm create agdf@latest -- codex
@@ -191,6 +193,7 @@ Scaffold-compatible npm create usage:
   npm create agdf@latest -- gate-check
   npm create agdf@latest -- delivery-map
   npm create agdf@latest -- delivery-path-search --surface codex
+  npm create agdf@latest -- delivery-path-search --surface claude
 
 Backward-compatible create-agdf usage:
   npx --yes create-agdf@latest doctor --json
@@ -1723,6 +1726,40 @@ function deriveQualityOutlook(runState, findings = []) {
   return "No additional quality follow-up identified from the current control state.";
 }
 
+function postApprovalTransition(missingApproval) {
+  const transitions = new Map([
+    ["Approval: UR", {
+      next_gate_after_approval: "Brownfield Review",
+      allowed_after_approval: "Run Brownfield Review and record Mode/Slice Decision before PRD or implementation.",
+    }],
+    ["Approval: PRD", {
+      next_gate_after_approval: "SD",
+      allowed_after_approval: "Draft Solution Design; implementation remains forbidden.",
+    }],
+    ["Approval: SD", {
+      next_gate_after_approval: "TP",
+      allowed_after_approval: "Draft Task/Test Plan; implementation remains forbidden.",
+    }],
+    ["Approval: TP", {
+      next_gate_after_approval: "Brownfield Analysis",
+      allowed_after_approval: "Run implementation-prep Brownfield Analysis before CD+Tests.",
+    }],
+    ["Approval: QA", {
+      next_gate_after_approval: "UAT",
+      allowed_after_approval: "Request UAT when QA has passed; release remains gated.",
+    }],
+    ["Approval: UAT", {
+      next_gate_after_approval: "OR",
+      allowed_after_approval: "Produce OR or delivery closeout; VCS and release actions still require explicit instruction.",
+    }],
+  ]);
+
+  return transitions.get(missingApproval) ?? {
+    next_gate_after_approval: "none",
+    allowed_after_approval: "none",
+  };
+}
+
 function buildStatusCard({
   status,
   currentGate,
@@ -1735,6 +1772,7 @@ function buildStatusCard({
   findings = [],
 }) {
   const qualityOutlook = deriveQualityOutlook(runState, findings);
+  const postApproval = postApprovalTransition(missingApproval);
   return {
     mode: extractField(runState.content ?? "", "mode") || "unknown",
     status,
@@ -1744,6 +1782,8 @@ function buildStatusCard({
     forbidden_now: forbidden,
     blocking_condition: blockingReason || "none",
     missing_approval: missingApproval || "none",
+    next_gate_after_approval: postApproval.next_gate_after_approval,
+    allowed_after_approval: postApproval.allowed_after_approval,
     evidence: runState.evidence_refs,
     next_skill: nextSkillByGate[currentGate] ?? "gate-check",
     next_step: nextAllowedAction,
@@ -1987,12 +2027,16 @@ function evaluateGateCheck(targetDir) {
       : doctorRevise.next_step;
   }
 
+  const postApproval = postApprovalTransition(missingApproval);
+
   return {
     schema_version: "1",
     status,
     current_gate: currentGate,
     blocking_reason: blockingReason,
     missing_approval: missingApproval,
+    next_gate_after_approval: postApproval.next_gate_after_approval,
+    allowed_after_approval: postApproval.allowed_after_approval,
     allowed,
     forbidden,
     next_allowed_action: nextAllowedAction,
@@ -2029,6 +2073,8 @@ function printGateCheckStatusCard(report) {
   console.log(`Current gate: ${card.current_gate}`);
   console.log(`Blocked by: ${card.blocking_condition}`);
   console.log(`Missing approval: ${card.missing_approval}`);
+  if (card.next_gate_after_approval !== "none") console.log(`Next gate after approval: ${card.next_gate_after_approval}`);
+  if (card.allowed_after_approval !== "none") console.log(`Allowed after approval: ${card.allowed_after_approval}`);
   console.log(`Next skill: ${card.next_skill}`);
   console.log(`Next step: ${card.next_step}`);
   console.log(`Quality outlook: ${card.quality_outlook}`);
@@ -2087,6 +2133,7 @@ function evaluateDeliveryMap(targetDir) {
 
   const qualityOutlook = deriveQualityOutlook(runState, map.findings);
   const nextAllowedAction = isPlaceholderValue(runState.next_allowed_action) ? gateDecision.next_allowed_action : runState.next_allowed_action;
+  const postApproval = postApprovalTransition(gateDecision.missing_approval);
 
   return {
     schema_version: "1",
@@ -2095,6 +2142,8 @@ function evaluateDeliveryMap(targetDir) {
     target_dir: targetDir,
     current_gate: currentGate,
     next_allowed_action: nextAllowedAction,
+    next_gate_after_approval: postApproval.next_gate_after_approval,
+    allowed_after_approval: postApproval.allowed_after_approval,
     quality_outlook: qualityOutlook,
     status_card: buildStatusCard({
       status,
@@ -2154,9 +2203,11 @@ async function executeDeliveryPathSearch(options) {
     ? fixtureEvaluator(fixture.evaluations ?? {})
     : options.surface === "codex"
       ? codexEvaluator({ cwd: options.dir, model: options.model })
-      : null;
+      : options.surface === "claude"
+        ? claudeEvaluator({ cwd: options.dir, model: options.model })
+        : null;
   if (!evaluator) {
-    throw new Error(`${options.surface} has no executable evaluator in this release. Codex is the reference adapter; --fixture is available for deterministic contract testing.`);
+    throw new Error(`${options.surface} has no executable evaluator in this release. Codex and Claude are the reference adapters; --fixture is available for deterministic contract testing.`);
   }
   const result = await runDeliveryPathSearch(input, evaluator, { candidates: fixture?.candidates });
   if (options.persist) result.persistence = persistSearchResult(options.dir, result);

package/generated/.agdf/control/templates/MASTER_BACKLOG.md

@@ -15,6 +15,9 @@ This file is the living control pointer for active AGDF delivery work. Detailed
 9. Historical artefacts remain linkable but do not override the current pointer.
 10. If an item is superseded, mark the replacement.
 11. If active work grows beyond roughly ten items, triage the backlog.
+12. `Status` must be one of the human-readable labels `create-agdf/bin/create-agdf.js`'s `backlogStatusLabels` normalizes: Needs UR, Awaiting Brownfield Review, Awaiting PRD, Awaiting PRD Approval, Awaiting SD, Awaiting SD Approval, Awaiting TP, Awaiting TP Approval, In Progress, Blocked, Awaiting QA, Awaiting UAT, Completed, Superseded, Abandoned. That map is authoritative; this list only mirrors it for readability.
+13. `Artefacts` link labels must be one of `backlogArtefactLabels`: `ur`, `brownfield`, `prd`, `sd`, `tp`, `qa`, `or` (case-insensitive). Do not invent other labels such as a raw artefact filename.
+14. After writing or updating this file, run `doctor --json` (or the locally available equivalent) and resolve any `AGDF_BACKLOG_STATUS_UNKNOWN` or `AGDF_BACKLOG_ARTEFACT_LABEL_UNKNOWN` finding before treating the edit as done.
 
 ## Active Backlog
 

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

@@ -70,7 +70,7 @@ The CLI reports are validators and JSON evidence, not the primary user experienc
 15. Missing or incomplete control state must not push setup work back to the user. For a fresh request, draft the current minimal artefact in the response and request the exact approval. Initialize or write `.agdf/control/` only when durable control state is explicitly requested, already live for the repository, or required for a deterministic CLI/CI setup path. Implementation remains forbidden.
 16. Branch names, uncommitted diffs, generated summaries and chat history are not sufficient scope proof when durable artefacts or approvals are missing or conflicting.
 17. If multiple active scopes are plausible, list the evidenced competing lines and keep the current step at scope clarification or the earliest common safe gate.
-18. When maintaining `MASTER_BACKLOG.md`, use its canonical compact columns, readable status labels and document-relative Markdown links. Do not expose raw long paths or internal snake_case statuses in the human-facing table.
+18. When maintaining `MASTER_BACKLOG.md`, use its canonical compact columns, readable status labels and document-relative Markdown links. Do not expose raw long paths or internal snake_case statuses in the human-facing table. The canonical status/artefact label vocabulary is defined in the AGDF control scaffold's `MASTER_BACKLOG.md` template Rules section; do not invent other labels.
 19. Preserve legacy backlog compatibility through the CLI parser; do not create a second surface-specific backlog format.
 
 ## Gate Evaluation

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

@@ -46,6 +46,7 @@ Use the Runtime Contract definition of `Relevant Run` to decide whether OR is ma
 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.
+15. After writing or updating `MASTER_BACKLOG.md`, run `doctor --json` (or the locally available equivalent) and resolve any `AGDF_BACKLOG_STATUS_UNKNOWN` or `AGDF_BACKLOG_ARTEFACT_LABEL_UNKNOWN` finding before closeout. See the AGDF control scaffold's `MASTER_BACKLOG.md` template Rules section for the canonical status/artefact label vocabulary.
 
 ## When To Use
 - at the end of every relevant run

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

@@ -40,6 +40,8 @@ It must not introduce a second gate model or override `agdf-gate-check`, `delive
 - `forbidden_now`: outputs or actions currently forbidden
 - `blocking_condition`: current blocker or `none`
 - `missing_approval`: exact missing approval formula or `none`
+- `next_gate_after_approval`: the next user gate or internal step unlocked by the missing approval, or `none`
+- `allowed_after_approval`: concise description of what becomes allowed after the missing approval, or `none`
 - `evidence`: concrete evidence references currently visible
 - `next_skill`: next AGDF skill or `none`
 - `next_step`: the single next permissible process action
@@ -52,6 +54,13 @@ 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.
 
+`allowed_now` and `allowed_after_approval` are intentionally different:
+
+- `allowed_now` is current authority under the active gate.
+- `allowed_after_approval` is the immediate authority unlocked only after the exact `missing_approval` is supplied.
+
+`next_gate_after_approval` and `allowed_after_approval` must be `none` when no approval is missing, when the current step is internal, or when the run is in OR/completed handoff. They must not imply implementation, QA, release, commit, push or PR authority unless the existing gate model already allows that authority.
+
 ## Delivery Path Search
 
 Delivery Path Search is an optional read-only planning step for high-impact decisions with several materially different next actions.
@@ -69,7 +78,8 @@ reports and automation. Human-facing Markdown must present the same projection
 with readable labels such as `Current gate`, `Allowed now`, `Blocked by`,
 `Next step` and `Quality outlook`; do not expose snake_case keys as the visible
 Run Status Card. Keep that card compact: show `Status`, `Current gate`,
-`Allowed now`, `Blocked by`, `Missing approval`, `Next step` and
+`Allowed now`, `Blocked by`, `Missing approval`, `Next gate after approval`
+and `Allowed after approval` when a missing approval exists, `Next step` and
 `Quality outlook`. Keep mode, forbidden actions, evidence and next-skill detail
 in the surrounding control artefact when they are relevant.
 

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

@@ -40,6 +40,8 @@ It must not introduce a second gate model or override `agdf-gate-check`, `delive
 - `forbidden_now`: outputs or actions currently forbidden
 - `blocking_condition`: current blocker or `none`
 - `missing_approval`: exact missing approval formula or `none`
+- `next_gate_after_approval`: the next user gate or internal step unlocked by the missing approval, or `none`
+- `allowed_after_approval`: concise description of what becomes allowed after the missing approval, or `none`
 - `evidence`: concrete evidence references currently visible
 - `next_skill`: next AGDF skill or `none`
 - `next_step`: the single next permissible process action
@@ -52,6 +54,13 @@ 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.
 
+`allowed_now` and `allowed_after_approval` are intentionally different:
+
+- `allowed_now` is current authority under the active gate.
+- `allowed_after_approval` is the immediate authority unlocked only after the exact `missing_approval` is supplied.
+
+`next_gate_after_approval` and `allowed_after_approval` must be `none` when no approval is missing, when the current step is internal, or when the run is in OR/completed handoff. They must not imply implementation, QA, release, commit, push or PR authority unless the existing gate model already allows that authority.
+
 ## Delivery Path Search
 
 Delivery Path Search is an optional read-only planning step for high-impact decisions with several materially different next actions.
@@ -69,7 +78,8 @@ reports and automation. Human-facing Markdown must present the same projection
 with readable labels such as `Current gate`, `Allowed now`, `Blocked by`,
 `Next step` and `Quality outlook`; do not expose snake_case keys as the visible
 Run Status Card. Keep that card compact: show `Status`, `Current gate`,
-`Allowed now`, `Blocked by`, `Missing approval`, `Next step` and
+`Allowed now`, `Blocked by`, `Missing approval`, `Next gate after approval`
+and `Allowed after approval` when a missing approval exists, `Next step` and
 `Quality outlook`. Keep mode, forbidden actions, evidence and next-skill detail
 in the surrounding control artefact when they are relevant.
 

package/generated/.opencode/agents/agdf-gate-check.md

@@ -70,7 +70,7 @@ The CLI reports are validators and JSON evidence, not the primary user experienc
 15. Missing or incomplete control state must not push setup work back to the user. For a fresh request, draft the current minimal artefact in the response and request the exact approval. Initialize or write `.agdf/control/` only when durable control state is explicitly requested, already live for the repository, or required for a deterministic CLI/CI setup path. Implementation remains forbidden.
 16. Branch names, uncommitted diffs, generated summaries and chat history are not sufficient scope proof when durable artefacts or approvals are missing or conflicting.
 17. If multiple active scopes are plausible, list the evidenced competing lines and keep the current step at scope clarification or the earliest common safe gate.
-18. When maintaining `MASTER_BACKLOG.md`, use its canonical compact columns, readable status labels and document-relative Markdown links. Do not expose raw long paths or internal snake_case statuses in the human-facing table.
+18. When maintaining `MASTER_BACKLOG.md`, use its canonical compact columns, readable status labels and document-relative Markdown links. Do not expose raw long paths or internal snake_case statuses in the human-facing table. The canonical status/artefact label vocabulary is defined in the AGDF control scaffold's `MASTER_BACKLOG.md` template Rules section; do not invent other labels.
 19. Preserve legacy backlog compatibility through the CLI parser; do not create a second surface-specific backlog format.
 
 ## Gate Evaluation

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

@@ -46,6 +46,7 @@ Use the Runtime Contract definition of `Relevant Run` to decide whether OR is ma
 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.
+15. After writing or updating `MASTER_BACKLOG.md`, run `doctor --json` (or the locally available equivalent) and resolve any `AGDF_BACKLOG_STATUS_UNKNOWN` or `AGDF_BACKLOG_ARTEFACT_LABEL_UNKNOWN` finding before closeout. See the AGDF control scaffold's `MASTER_BACKLOG.md` template Rules section for the canonical status/artefact label vocabulary.
 
 ## When To Use
 - at the end of every relevant run

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

@@ -1,9 +1,9 @@
 {
   "name": "agdf",
-  "version": "0.4.6",
+  "version": "0.4.8",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
   "author": {
-    "name": "AI-native Governance & Delivery Framework",
+    "name": "Arndt Gold",
     "url": "https://agdf.iself.eu"
   },
   "homepage": "https://agdf.iself.eu",

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

@@ -15,6 +15,9 @@ This file is the living control pointer for active AGDF delivery work. Detailed
 9. Historical artefacts remain linkable but do not override the current pointer.
 10. If an item is superseded, mark the replacement.
 11. If active work grows beyond roughly ten items, triage the backlog.
+12. `Status` must be one of the human-readable labels `create-agdf/bin/create-agdf.js`'s `backlogStatusLabels` normalizes: Needs UR, Awaiting Brownfield Review, Awaiting PRD, Awaiting PRD Approval, Awaiting SD, Awaiting SD Approval, Awaiting TP, Awaiting TP Approval, In Progress, Blocked, Awaiting QA, Awaiting UAT, Completed, Superseded, Abandoned. That map is authoritative; this list only mirrors it for readability.
+13. `Artefacts` link labels must be one of `backlogArtefactLabels`: `ur`, `brownfield`, `prd`, `sd`, `tp`, `qa`, `or` (case-insensitive). Do not invent other labels such as a raw artefact filename.
+14. After writing or updating this file, run `doctor --json` (or the locally available equivalent) and resolve any `AGDF_BACKLOG_STATUS_UNKNOWN` or `AGDF_BACKLOG_ARTEFACT_LABEL_UNKNOWN` finding before treating the edit as done.
 
 ## Active Backlog
 

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

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "id": "agdf",
-  "version": "0.4.6",
+  "version": "0.4.8",
   "displayName": "AI Governance & Delivery Framework",
   "developerName": "AI-native Governance & Delivery Framework",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
@@ -21,7 +21,7 @@
   "category": "Productivity",
   "brandColor": "#14B8A6",
   "author": {
-    "name": "AI-native Governance & Delivery Framework",
+    "name": "Arndt Gold",
     "url": "https://agdf.iself.eu"
   },
   "codex": {

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

@@ -40,6 +40,8 @@ It must not introduce a second gate model or override `gate-check`, `delivery-ma
 - `forbidden_now`: outputs or actions currently forbidden
 - `blocking_condition`: current blocker or `none`
 - `missing_approval`: exact missing approval formula or `none`
+- `next_gate_after_approval`: the next user gate or internal step unlocked by the missing approval, or `none`
+- `allowed_after_approval`: concise description of what becomes allowed after the missing approval, or `none`
 - `evidence`: concrete evidence references currently visible
 - `next_skill`: next AGDF skill or `none`
 - `next_step`: the single next permissible process action
@@ -52,6 +54,13 @@ 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.
 
+`allowed_now` and `allowed_after_approval` are intentionally different:
+
+- `allowed_now` is current authority under the active gate.
+- `allowed_after_approval` is the immediate authority unlocked only after the exact `missing_approval` is supplied.
+
+`next_gate_after_approval` and `allowed_after_approval` must be `none` when no approval is missing, when the current step is internal, or when the run is in OR/completed handoff. They must not imply implementation, QA, release, commit, push or PR authority unless the existing gate model already allows that authority.
+
 ## Delivery Path Search
 
 Delivery Path Search is an optional read-only planning step for high-impact decisions with several materially different next actions.
@@ -69,7 +78,8 @@ reports and automation. Human-facing Markdown must present the same projection
 with readable labels such as `Current gate`, `Allowed now`, `Blocked by`,
 `Next step` and `Quality outlook`; do not expose snake_case keys as the visible
 Run Status Card. Keep that card compact: show `Status`, `Current gate`,
-`Allowed now`, `Blocked by`, `Missing approval`, `Next step` and
+`Allowed now`, `Blocked by`, `Missing approval`, `Next gate after approval`
+and `Allowed after approval` when a missing approval exists, `Next step` and
 `Quality outlook`. Keep mode, forbidden actions, evidence and next-skill detail
 in the surrounding control artefact when they are relevant.
 

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

@@ -70,7 +70,7 @@ The CLI reports are validators and JSON evidence, not the primary user experienc
 15. Missing or incomplete control state must not push setup work back to the user. For a fresh request, draft the current minimal artefact in the response and request the exact approval. Initialize or write `.agdf/control/` only when durable control state is explicitly requested, already live for the repository, or required for a deterministic CLI/CI setup path. Implementation remains forbidden.
 16. Branch names, uncommitted diffs, generated summaries and chat history are not sufficient scope proof when durable artefacts or approvals are missing or conflicting.
 17. If multiple active scopes are plausible, list the evidenced competing lines and keep the current step at scope clarification or the earliest common safe gate.
-18. When maintaining `MASTER_BACKLOG.md`, use its canonical compact columns, readable status labels and document-relative Markdown links. Do not expose raw long paths or internal snake_case statuses in the human-facing table.
+18. When maintaining `MASTER_BACKLOG.md`, use its canonical compact columns, readable status labels and document-relative Markdown links. Do not expose raw long paths or internal snake_case statuses in the human-facing table. The canonical status/artefact label vocabulary is defined in the AGDF control scaffold's `MASTER_BACKLOG.md` template Rules section; do not invent other labels.
 19. Preserve legacy backlog compatibility through the CLI parser; do not create a second surface-specific backlog format.
 
 ## Gate Evaluation

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

@@ -46,6 +46,7 @@ Use the Runtime Contract definition of `Relevant Run` to decide whether OR is ma
 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.
+15. After writing or updating `MASTER_BACKLOG.md`, run `doctor --json` (or the locally available equivalent) and resolve any `AGDF_BACKLOG_STATUS_UNKNOWN` or `AGDF_BACKLOG_ARTEFACT_LABEL_UNKNOWN` finding before closeout. See the AGDF control scaffold's `MASTER_BACKLOG.md` template Rules section for the canonical status/artefact label vocabulary.
 
 ## When To Use
 - at the end of every relevant run

package/lib/delivery-path-search/evaluators/claude.js

@@ -0,0 +1,58 @@
+import { execFileSync } from "node:child_process";
+import { evaluatorOutputSchema, validateEvaluation } from "../contracts.js";
+
+export function claudeEvaluator(options = {}) {
+  const claudeBin = options.claudeBin ?? "claude";
+  let runtime = "claude version unavailable";
+  try {
+    runtime = execFileSync(claudeBin, ["--version"], { encoding: "utf8", stdio: ["ignore", "pipe", "ignore"] }).trim();
+  } catch {}
+
+  function gitState() {
+    try {
+      return execFileSync("git", ["status", "--porcelain=v1", "-z"], {
+        cwd: options.cwd,
+        encoding: "utf8",
+        stdio: ["ignore", "pipe", "ignore"],
+      });
+    } catch {
+      return null;
+    }
+  }
+
+  return {
+    name: "claude",
+    metadata: { name: "claude", runtime, model: options.model ?? "configured-default" },
+    async evaluate(input, candidate) {
+      const prompt = [
+        "You are an evaluation-only component. Do not use tools, execute commands, or modify files.",
+        `Return JSON matching contract version ${input.contract_version}.`,
+        `Objective: ${input.objective}`,
+        `Current gate: ${input.current_gate}`,
+        `Candidate id: ${candidate.id}`,
+        `Candidate action: ${candidate.action}`,
+        "Score scope_fit, gate_readiness, risk_reduction, evidence_gain, testability, reversibility and cost from 0 to 5.",
+        "Cost 0 is low and 5 is high. uncertainty is 0 low to 5 high.",
+        "Keep rationale concise. child_actions must only contain actions permitted by the current gate.",
+      ].join("\n");
+      const args = [
+        "-p", "--disallowedTools", "Edit,Write,Bash",
+        "--output-format", "json", "--json-schema", JSON.stringify(evaluatorOutputSchema()),
+      ];
+      if (options.model) args.push("--model", options.model);
+      args.push(prompt);
+      const before = gitState();
+      const raw = execFileSync(claudeBin, args, {
+        cwd: options.cwd,
+        encoding: "utf8",
+        stdio: ["ignore", "pipe", "pipe"],
+        timeout: options.timeoutMs ?? 120000,
+      });
+      const after = gitState();
+      if (before !== null && after !== before) throw new Error("repository mutation detected during read-only evaluator run");
+      const response = JSON.parse(raw);
+      if (response.is_error) throw new Error(`claude evaluator returned an error: ${response.result ?? "unknown error"}`);
+      return validateEvaluation(JSON.parse(response.result), candidate.id);
+    },
+  };
+}

package/lib/delivery-path-search/surfaces/capabilities.js

@@ -3,7 +3,7 @@ import { validateEnforcement } from "../contracts.js";
 export function enforcementForSurface(surface, evidence = []) {
   const defaults = {
     codex: { level: "tool_enforced", evidence: ["codex exec --sandbox read-only --ephemeral"] },
-    claude: { level: "instruction_only", evidence: [] },
+    claude: { level: "tool_enforced", evidence: ["claude -p --disallowedTools Edit,Write,Bash"] },
     copilot: { level: "instruction_only", evidence: [] },
     opencode: { level: "instruction_only", evidence: [] },
     generic: { level: "instruction_only", evidence: [] },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-agdf",
-  "version": "0.4.6",
+  "version": "0.4.8",
   "description": "Bootstrap AGDF repository-local plugin files, Copilot/OpenCode instructions, skills, control files and machine-readable checks.",
   "type": "module",
   "files": [
@@ -22,8 +22,9 @@
   "scripts": {
     "sync-package-assets": "node ./scripts/sync-package-assets.js",
     "test:delivery-path-search": "node ./scripts/delivery-path-search-test.js",
+    "test:delivery-path-search-unit": "node ./scripts/delivery-path-search-unit-test.js",
     "test:routing": "npm run sync-package-assets && node ./scripts/test-routing.js",
-    "smoke-test": "npm run sync-package-assets && npm run test:delivery-path-search && node ./scripts/smoke-test.js && node ./scripts/test-routing.js",
+    "smoke-test": "npm run sync-package-assets && npm run test:delivery-path-search && npm run test:delivery-path-search-unit && node ./scripts/smoke-test.js && node ./scripts/test-routing.js",
     "prepack": "npm run sync-package-assets"
   },
   "keywords": [