create-agdf 0.4.7 → 0.4.9

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
@@ -2200,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/README.md

@@ -80,5 +80,6 @@ npx --yes @agdf/cli@latest gate-check --json
 - `SOT_REGISTRY.md` decides which document owns which domain.
 - `CONTEXT_GRAPH.md` records durable project knowledge only when it has evidence and an exit criterion.
 - `AGENT_QUALITY_CONTRACTS.json` names reusable block, revise and warning conditions.
+- `AGDF_RUN.md` can be edited concurrently from different machines or sessions. Give it a `.gitattributes` entry (`.agdf/control/AGDF_RUN.md merge=union`, git's built-in union driver — no local `git config` registration needed, unlike a custom named driver) so concurrent edits merge automatically instead of blocking. Always re-run `doctor`/`gate-check` and visually skim the merged file after a merge or pull that could have touched it: a union merge on conflicting lines (e.g. two different `current_gate` values) keeps both lines rather than erroring, and `doctor` reads only the first match per field, so it will not by itself flag that duplication — it only catches missing or structurally malformed fields.
 
 Do not duplicate full product documentation in this scaffold. Link to the authoritative artefact instead.

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

@@ -27,6 +27,25 @@ Use this compact output shape when no formal gate artefact is required:
 
 Do not add a separate `Quality outlook` line for pure Quick Tasks unless the task became a relevant run.
 
+### Non-Normative Trivial Change Boundary
+
+A `quick_task` whose entire diff stays fully outside all of the following paths may close using only
+the compact output shape above, and must not create, rewrite or expand any of `AGDF_RUN.md`'s core
+sections (Run Meta, Objective, Current Control State, Source And Scope State, Run Status Card,
+Approvals, Artefacts, Mode/Slice Decision, Artefact Chain, Evidence, Missing Evidence, Risks, Context
+Graph Impact, Knowledge Persistence Decision, Closeout):
+
+- `plugin/skills/**`
+- `plugin/control/templates/**`
+- `plugin/meta/**`
+- `create-agdf/lib/**`
+- `create-agdf/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.
+
 ## Run Status Card
 
 When a run needs an operational status view, use the Run Status Card as a compact projection of existing control state.
@@ -181,6 +200,11 @@ A relevant run is any run that changes durable state, creates or updates an AGDF
 OR is not mandatory for a pure explanation, read-only inspection, small review, or local debugging step that produces no durable state change and no gate consequence.
 When in doubt, use a short OR-lite only if it clarifies gate state, evidence, risk, or the next permissible step.
 
+A `quick_task` fully inside the Non-Normative Trivial Change Boundary above stays exempt from the full
+`AGDF_RUN.md` ceremony even when it is otherwise a relevant run. If `AGDF_RUN.md` currently reflects
+another active run, append exactly one line to that run's `Prior Run Pointers` section noting what
+changed and that it is unrelated; do not edit any other section or any other existing line.
+
 ## Gate Rules
 
 - User gates: `UR -> PRD -> SD -> TP -> QA -> UAT`

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

@@ -27,6 +27,25 @@ Use this compact output shape when no formal gate artefact is required:
 
 Do not add a separate `Quality outlook` line for pure Quick Tasks unless the task became a relevant run.
 
+### Non-Normative Trivial Change Boundary
+
+A `quick_task` whose entire diff stays fully outside all of the following paths may close using only
+the compact output shape above, and must not create, rewrite or expand any of `AGDF_RUN.md`'s core
+sections (Run Meta, Objective, Current Control State, Source And Scope State, Run Status Card,
+Approvals, Artefacts, Mode/Slice Decision, Artefact Chain, Evidence, Missing Evidence, Risks, Context
+Graph Impact, Knowledge Persistence Decision, Closeout):
+
+- `plugin/skills/**`
+- `plugin/control/templates/**`
+- `plugin/meta/**`
+- `create-agdf/lib/**`
+- `create-agdf/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.
+
 ## Run Status Card
 
 When a run needs an operational status view, use the Run Status Card as a compact projection of existing control state.
@@ -181,6 +200,11 @@ A relevant run is any run that changes durable state, creates or updates an AGDF
 OR is not mandatory for a pure explanation, read-only inspection, small review, or local debugging step that produces no durable state change and no gate consequence.
 When in doubt, use a short OR-lite only if it clarifies gate state, evidence, risk, or the next permissible step.
 
+A `quick_task` fully inside the Non-Normative Trivial Change Boundary above stays exempt from the full
+`AGDF_RUN.md` ceremony even when it is otherwise a relevant run. If `AGDF_RUN.md` currently reflects
+another active run, append exactly one line to that run's `Prior Run Pointers` section noting what
+changed and that it is unrelated; do not edit any other section or any other existing line.
+
 ## Gate Rules
 
 - User gates: `UR -> PRD -> SD -> TP -> QA -> UAT`

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.7",
-  "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
+  "version": "0.4.9",
+  "description": "Codex-first operating system for governed AI-assisted delivery.",
   "author": {
-    "name": "AI-native Governance & Delivery Framework",
+    "name": "Arndt Gold",
     "url": "https://agdf.iself.eu"
   },
   "homepage": "https://agdf.iself.eu",
@@ -20,9 +20,9 @@
   "hooks": "./hooks/hooks.json",
   "interface": {
     "displayName": "AI Governance & Delivery Framework",
-    "shortDescription": "Codex-first workflow skills for gated, auditable AI-assisted delivery.",
-    "longDescription": "AI Governance & Delivery Framework (AGDF) packages reusable Codex-first skills, control templates and machine-readable repository checks for gate decisions, Brownfield analysis, task-plan review, solution-integrity review, QA decisions, durable run state and auditable delivery closeout.",
-    "developerName": "AI-native Governance & Delivery Framework",
+    "shortDescription": "Codex-first operating system for governed AI-assisted delivery.",
+    "longDescription": "AI Governance & Delivery Framework (AGDF) brings an operating system for governed AI-assisted delivery to Codex, combining workflow skills, control templates and machine-readable repository checks for gate decisions, Brownfield analysis, task-plan review, QA decisions, durable run state and auditable delivery closeout.",
+    "developerName": "Arndt Gold",
     "category": "Productivity",
     "capabilities": [
       "Read",
@@ -32,10 +32,9 @@
     "composerIcon": "./assets/agdf-icon.svg",
     "logo": "./assets/agdf-logo.svg",
     "defaultPrompt": [
-      "Run an AGDF gate check for this request.",
-      "Create an AGDF control scaffold for this repository.",
-      "Use AGDF Brownfield analysis before implementation.",
-      "Close this run with an AGDF orchestration report."
+      "Start this request under AGDF governance.",
+      "Create durable AGDF control state for this repository.",
+      "Close this delivery run with an auditable AGDF report."
     ],
     "brandColor": "#14B8A6"
   }

package/generated/plugins/agdf/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/generated/plugins/agdf/control/README.md

@@ -80,5 +80,6 @@ npx --yes @agdf/cli@latest gate-check --json
 - `SOT_REGISTRY.md` decides which document owns which domain.
 - `CONTEXT_GRAPH.md` records durable project knowledge only when it has evidence and an exit criterion.
 - `AGENT_QUALITY_CONTRACTS.json` names reusable block, revise and warning conditions.
+- `AGDF_RUN.md` can be edited concurrently from different machines or sessions. Give it a `.gitattributes` entry (`.agdf/control/AGDF_RUN.md merge=union`, git's built-in union driver — no local `git config` registration needed, unlike a custom named driver) so concurrent edits merge automatically instead of blocking. Always re-run `doctor`/`gate-check` and visually skim the merged file after a merge or pull that could have touched it: a union merge on conflicting lines (e.g. two different `current_gate` values) keeps both lines rather than erroring, and `doctor` reads only the first match per field, so it will not by itself flag that duplication — it only catches missing or structurally malformed fields.
 
 Do not duplicate full product documentation in this scaffold. Link to the authoritative artefact instead.

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,13 +1,13 @@
 {
   "schemaVersion": 1,
   "id": "agdf",
-  "version": "0.4.7",
+  "version": "0.4.9",
   "displayName": "AI Governance & Delivery Framework",
-  "developerName": "AI-native Governance & Delivery Framework",
-  "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
-  "claudeDescription": "Codex-first workflow skills and control templates for gated, auditable AI-assisted software delivery.",
-  "shortDescription": "Codex-first workflow skills for gated, auditable AI-assisted delivery.",
-  "longDescription": "AI Governance & Delivery Framework (AGDF) packages reusable Codex-first skills, control templates and machine-readable repository checks for gate decisions, Brownfield analysis, task-plan review, solution-integrity review, QA decisions, durable run state and auditable delivery closeout.",
+  "developerName": "Arndt Gold",
+  "description": "Codex-first operating system for governed AI-assisted delivery.",
+  "claudeDescription": "AI Governance & Delivery Framework (AGDF) brings an operating system for governed AI-assisted delivery to Claude Code, combining workflow skills, control templates and machine-readable repository checks for gate decisions, Brownfield analysis, task-plan review, QA decisions, durable run state and auditable closeout.",
+  "shortDescription": "Codex-first operating system for governed AI-assisted delivery.",
+  "longDescription": "AI Governance & Delivery Framework (AGDF) brings an operating system for governed AI-assisted delivery to Codex, combining workflow skills, control templates and machine-readable repository checks for gate decisions, Brownfield analysis, task-plan review, QA decisions, durable run state and auditable delivery closeout.",
   "homepage": "https://agdf.iself.eu",
   "repository": "https://github.com/arndtgold/ai-native-governance-delivery-framework",
   "license": "Apache-2.0",
@@ -21,7 +21,7 @@
   "category": "Productivity",
   "brandColor": "#14B8A6",
   "author": {
-    "name": "AI-native Governance & Delivery Framework",
+    "name": "Arndt Gold",
     "url": "https://agdf.iself.eu"
   },
   "codex": {
@@ -35,10 +35,9 @@
       "Write"
     ],
     "defaultPrompt": [
-      "Run an AGDF gate check for this request.",
-      "Create an AGDF control scaffold for this repository.",
-      "Use AGDF Brownfield analysis before implementation.",
-      "Close this run with an AGDF orchestration report."
+      "Start this request under AGDF governance.",
+      "Create durable AGDF control state for this repository.",
+      "Close this delivery run with an auditable AGDF report."
     ],
     "hooks": "hooks/hooks.json"
   },

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

@@ -27,6 +27,25 @@ Use this compact output shape when no formal gate artefact is required:
 
 Do not add a separate `Quality outlook` line for pure Quick Tasks unless the task became a relevant run.
 
+### Non-Normative Trivial Change Boundary
+
+A `quick_task` whose entire diff stays fully outside all of the following paths may close using only
+the compact output shape above, and must not create, rewrite or expand any of `AGDF_RUN.md`'s core
+sections (Run Meta, Objective, Current Control State, Source And Scope State, Run Status Card,
+Approvals, Artefacts, Mode/Slice Decision, Artefact Chain, Evidence, Missing Evidence, Risks, Context
+Graph Impact, Knowledge Persistence Decision, Closeout):
+
+- `plugin/skills/**`
+- `plugin/control/templates/**`
+- `plugin/meta/**`
+- `create-agdf/lib/**`
+- `create-agdf/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.
+
 ## Run Status Card
 
 When a run needs an operational status view, use the Run Status Card as a compact projection of existing control state.
@@ -181,6 +200,11 @@ A relevant run is any run that changes durable state, creates or updates an AGDF
 OR is not mandatory for a pure explanation, read-only inspection, small review, or local debugging step that produces no durable state change and no gate consequence.
 When in doubt, use a short OR-lite only if it clarifies gate state, evidence, risk, or the next permissible step.
 
+A `quick_task` fully inside the Non-Normative Trivial Change Boundary above stays exempt from the full
+`AGDF_RUN.md` ceremony even when it is otherwise a relevant run. If `AGDF_RUN.md` currently reflects
+another active run, append exactly one line to that run's `Prior Run Pointers` section noting what
+changed and that it is unrelated; do not edit any other section or any other existing line.
+
 ## Gate Rules
 
 - User gates: `UR -> PRD -> SD -> TP -> QA -> UAT`

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.7",
+  "version": "0.4.9",
   "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": [