create-agdf 0.13.7 → 0.14.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "create-agdf",
-  "version": "0.13.7",
-  "description": "Bootstrap AGDF repository-local plugin files, Copilot/OpenCode instructions, skills, control files and machine-readable checks.",
+  "version": "0.14.1",
+  "description": "Install AGDF plugins, bootstrap supported repository surfaces and validate durable governance state.",
   "type": "module",
   "files": [
     "bin",
@@ -24,6 +24,7 @@
     "build:public-plugin": "node ./scripts/build-public-plugin.js",
     "install:claude": "node ./scripts/install-local-plugin.js claude",
     "install:codex": "node ./scripts/install-local-plugin.js codex",
+    "install:copilot": "node ./scripts/install-local-plugin.js copilot",
     "install:opencode": "node ./scripts/install-local-plugin.js opencode",
     "test:release-version-coherence": "node ./scripts/release-version-coherence-test.js",
     "test:public-plugin": "node ./scripts/public-plugin-test.js",
@@ -32,6 +33,7 @@
     "test:delivery-path-search-unit": "node ./scripts/delivery-path-search-unit-test.js",
     "test:delivery-path-search-generator": "node ./scripts/delivery-path-search-generator-test.js",
     "test:opencode-hardening": "node ./scripts/opencode-hardening-test.js",
+    "test:runtime-check-consent": "node ./scripts/runtime-check-consent-test.js",
     "test:cli-modularization": "node ./scripts/cli-modularization-test.js",
     "test:local-validator": "node ./scripts/local-validator-test.js",
     "test:local-marketplace": "node ./scripts/local-marketplace-test.js",
@@ -39,6 +41,7 @@
     "test:package-contents": "node ./scripts/package-contents-test.js",
     "test:package-build": "node ./scripts/package-build-test.js",
     "test:lifecycle": "node ./scripts/lifecycle-test.js",
+    "test:copilot-repository-retention": "node ./scripts/copilot-repository-retention-test.js",
     "test:control-state": "node ./scripts/control-state-test.js",
     "test:parent-reconciliation": "node ./scripts/parent-reconciliation-test.js",
     "test:interaction-presentation": "node ./scripts/interaction-presentation-test.js",
@@ -54,7 +57,7 @@
     "test:proportionality": "node ./scripts/proportionality-benchmark-test.js",
     "test:release-bootstrap": "node ./scripts/release-bootstrap-smoke-test.js",
     "test:routing": "npm run sync-package-assets && node ./scripts/test-routing.js",
-    "smoke-test": "npm run release:prepare && npm run test:cli-modularization && npm run test:local-validator && npm run test:local-marketplace && npm run test:local-development-install && npm run test:package-build && npm run test:package-contents && npm run test:lifecycle && npm run test:control-state && npm run test:parent-reconciliation && npm run test:interaction-presentation && npm run test:verified-change && npm run test:runtime-integrity-layout && npm run test:runtime-integrity-negative && npm run test:agent-skills-conformance && npm run test:skill-evals && npm run eval:skills && npm run test:proportionality && npm run test:delivery-path-search && npm run test:delivery-path-search-unit && npm run test:delivery-path-search-generator && npm run test:opencode-hardening && node ./scripts/smoke-test.js && node ./scripts/test-routing.js",
+    "smoke-test": "npm run release:prepare && npm run test:cli-modularization && npm run test:local-validator && npm run test:local-marketplace && npm run test:local-development-install && npm run test:package-build && npm run test:package-contents && npm run test:lifecycle && npm run test:copilot-repository-retention && npm run test:control-state && npm run test:parent-reconciliation && npm run test:interaction-presentation && npm run test:verified-change && npm run test:runtime-integrity-layout && npm run test:runtime-integrity-negative && npm run test:agent-skills-conformance && npm run test:skill-evals && npm run eval:skills && npm run test:proportionality && npm run test:delivery-path-search && npm run test:delivery-path-search-unit && npm run test:delivery-path-search-generator && npm run test:opencode-hardening && node ./scripts/smoke-test.js && node ./scripts/test-routing.js",
     "prepack": "npm run release:prepare"
   },
   "keywords": [

package/generated/.github/copilot-instructions.md

@@ -1,16 +0,0 @@
-# AGDF Copilot instructions
-
-AGDF is active in this repository.
-
-- Treat `AGENTS.md` as the primary repository instruction source.
-- Use `.github/skills/` for AGDF task workflows instead of inventing parallel process rules.
-- Use `.agdf/control/` for durable run state, backlog pointers, source-of-truth ownership, Context Graph knowledge and quality contracts.
-- AGDF is agent-native first and CLI-verifiable by design.
-- Apply AGDF natively from `AGENTS.md`, repository skills and live `.agdf/control/` state before reaching for helper commands.
-- Before non-trivial implementation or formal delivery work, determine whether the request is a Quick Task or Structured Delivery.
-- If approval, evidence, ownership or the next allowed action is unclear, run the AGDF gate-check workflow before creating later artefacts or code.
-- Use `doctor --json`, `gate-check --json` or `delivery-map --json` as deterministic validators for CI, PR evidence, regression checks and audit trails, not as the primary workflow.
-- Do not infer gate approval from generic consent such as "ok", "go ahead", "do it", "continue", "leg los" or "approved".
-- Do not treat chat history as the source of truth for gate state, approvals, evidence or delivery status.
-- 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.
-- For deterministic ready-gate rendering, prefer an installed `agdf gate-check --approval-envelope`; use `agdf gate-check --json` for native-adapter input, automation or audit evidence. Reserve `npx ...@latest` for bootstrap, installation, refresh or a missing local executable.

package/generated/.github/instructions/agdf-governance.instructions.md

@@ -1,14 +0,0 @@
----
-applyTo: "AGENTS.md,AGENTS.agdf.md,.agdf/**,.github/skills/**,.github/copilot-instructions.md,.github/instructions/**"
----
-
-# AGDF governance artefacts
-
-These files are control artefacts, not general documentation.
-
-- Keep AGDF rules sourced from `AGENTS.md`, `.github/skills/` and `.github/skills/agdf-runtime-contract.md`.
-- Do not duplicate the full gate model, Quality Contract table or Context Graph relationship language in new files.
-- Keep generated AGDF files small, reviewable and linked to the owning source of truth.
-- Preserve the rule that missing approval, missing evidence or unclear ownership blocks later delivery steps.
-- Preserve the rule that gates cannot be skipped by generic consent, urgency or a request to start.
-- If changing AGDF bootstrap behaviour, update the generated files, smoke test and affected setup documentation together.

package/generated/.github/skills/README.md

@@ -1,20 +0,0 @@
-# AGDF repository skills
-
-These repository skills were generated from the AGDF source repository and are intended to be checked into this repository.
-
-## Skills
-
-- `agdf-brownfield-analysis`
-- `agdf-clean-implementation-review`
-- `agdf-code-review`
-- `agdf-delivery-closeout`
-- `agdf-delivery-path-search`
-- `agdf-gate-check`
-- `agdf-qa-gate`
-- `agdf-release-or`
-- `agdf-task-plan-review`
-- `agdf-ux-intent-definition`
-
-## Runtime contract
-
-Shared output and gate rules for this checkout live in `agdf-runtime-contract.md`.

package/generated/AGENTS.md

@@ -1,113 +0,0 @@
-# AGENTS.md
-
-## Role
-You are an autonomous agent operating in an AGDF-governed delivery system.
-
-Use the plugin skills as workflow controls, not as documentation shortcuts.
-Your goal is trustworthy progress: reduce uncertainty, establish evidence, preserve artefacts, verify outcomes and make the next allowed step explicit.
-
-## Surface Convention
-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-ux-intent-definition`
-- `agdf-clean-implementation-review`
-- `agdf-code-review`
-- `agdf-delivery-closeout`
-- `agdf-gate-check`
-- `agdf-qa-gate`
-- `agdf-release-or`
-- `agdf-task-plan-review`
-
-Do not remove that prefix in Copilot-facing repository skills.
-Codex and Claude Code plugin surfaces use the same canonical router with unprefixed skill names because their plugin namespace already carries `agdf`.
-## Mode Selection
-Default entry rule: a new user intent to build, add, change, extend, refactor or otherwise deliver something starts with `agdf-gate-check` unless it is clearly only a question, explanation, local inspection, or explicitly scoped review.
-
-Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics. Use Verified Change only after approved UR and Brownfield Review when the Runtime Contract's compact record can prove bounded ownership, clean-at-baseline paths, prohibited-impact absence and deterministic validation.
-
-Use Structured Delivery Mode for new capabilities, architecture, policy, persistence, release-critical work, formal artefacts or explicit approvals.
-
-Any new product semantics, functional change or user-visible behaviour change requires a durable UR first.
-Persist it in `.agdf/control/` or link it from there to the target repository's authoritative source of truth before PRD, SD, TP, Brownfield Analysis or implementation.
-Treat approval text and durable artefact presence as separate checks for UR, PRD, SD, TP and QA report decisions.
-Do not infer approval from "ok", "go ahead", "do it", "approved", "continue", "leg los" or similar wording.
-Those phrases may express intent to proceed, but they do not unlock a gate unless the exact gate formula is present.
-Do not infer active scope from branch names, uncommitted workspace deltas, chat history or generated summaries when durable artefacts point elsewhere.
-If multiple active scopes are plausible, list the evidenced lines and route to `agdf-gate-check` or workstate clarification instead of choosing silently.
-After `Approval: UR`, run lightweight Brownfield Review before PRD when Brownfield, ownership, runtime, policy, persistence, architecture, UI or UX impact is possible.
-Brownfield Review must produce a Mode/Slice Decision: `quick_task`, `verified_change`, `structured_slice`, `structured_delivery` or `block`.
-That same review records the shared UI/UX impact classification. Run `agdf-ux-intent-definition` before
-PRD readiness for medium/high impact and for low impact with ambiguous mandatory PRD semantics. It is
-an internal analytical step, not a gate or product authority; a required blocked result keeps PRD
-readiness closed.
-Make that decision visible before coding or drafting later artefacts: state the selected path, scope reason, evidence and next required gate in the live control state or linked artefact.
-Do not assume the full PRD/SD/TP chain before that decision; use only as much gate depth as the reviewed change size justifies. A user-visible change is not automatically Verified Change eligible; any missing or ambiguous record condition escalates to the declared structured target before implementation.
-
-Quick Task Mode must still use the Runtime Contract mini-output: `result`, `evidence`, `risk`, `next_step`.
-Narrow defect work may use the Runtime Contract's Bug Lightweight Track only when a durable bug artefact or linked authoritative issue carries reproduction, actual behavior, expected behavior, fix boundary and evidence plan.
-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-ux-intent-definition` | after approved UR and post-UR routing for medium/high UI/UX impact or ambiguous low-impact product semantics before PRD readiness | non-authorizing analytical PRD input; never creates product intent, gate permission, technical design or a parallel product source of truth |
-| `agdf-clean-implementation-review` | evidence dimension: inspect whether the solution is structurally clean | supports Quality Readiness; not a TP or QA substitute |
-| `agdf-code-review` | evidence dimension: review the actual diff for defects, regression and security findings | supports Quality Readiness; does not replace QA |
-| `agdf-delivery-closeout` | commit/PR-near handoff after QA/OR/UAT | never performs VCS actions automatically |
-| `agdf-gate-check` | new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts or skip Mode/Slice Decision after Brownfield Review |
-| `agdf-qa-gate` | sole final Quality Readiness decision | only instance for `pass | revise | block` |
-| `agdf-release-or` | auditable closeout for every relevant run | not a QA substitute |
-| `agdf-task-plan-review` | evidence dimension: verify whether the approved Task Plan was fulfilled | supports Quality Readiness; no final QA decision |
-
-Select exactly one primary skill first.
-Add more only when they cover a distinct concrete risk dimension.
-Do not choose `agdf-brownfield-analysis` as the first primary skill for a fresh "I want to build/change X" prompt unless `agdf-gate-check` or existing live AGDF control state already makes implementation preparation the next allowed action.
-Never jump directly from `Approval: UR`, implicit consent, or a generic "start" request to implementation. Route to Brownfield Review, then a visible Mode/Slice Decision with evidence, then the smallest safe next gate or Quick Task execution.
-
-## Runtime Contract
-For repeated output, gate, Quality Contract and Context Graph rules, use:
-
-- `contracts/task-target-resolution.md` for primary target authority before repository activation
-- `contracts/gate-transition.md` for gate terms, Brownfield routing and transition rules
-- `contracts/interaction.md` for status cards, approval orientation and native interaction
-- `contracts/modes.md` for delivery-mode boundaries
-- `contracts/quality.md` for quality and output discipline
-- `contracts/context-graph.md` for persistence and reconciliation
-- `contracts/control-scaffold.md` for run state, CLI verification and Delivery Map
-- `contracts/closeout.md` for relevant-run and closeout boundaries
-
-`agdf-runtime-contract.md` remains the compatibility manifest for these modules.
-
-Skills may include short reminders, but they must not carry a second complete rule or code table.
-
-## Durable Control State
-When the target repository uses the AGDF control scaffold, keep live control files under `.agdf/control/`.
-Use templates as starting points only.
-
-Do not let chat history become the source of truth for gate state, approvals, evidence, backlog status or durable Brownfield knowledge.
-
-AGDF is agent-native first and CLI-verifiable by design: read the live control state, apply the active skill and make the next allowed step explicit.
-Use `init` only when durable control state is explicitly requested, the repository already uses `.agdf/control/` as its live AGDF working state, or a deterministic CLI/CI setup path is being executed.
-Use `doctor --json`, `gate-check --json` or `delivery-map --json` as deterministic validators for CI, PR evidence, regression checks or audit trails, not as a substitute for the router or skills.
-At run closeout, route new durable knowledge explicitly as `context_graph`, `sot_registry`, `scope_artifact`, `open_questions` or `none`.
-
-## Closeout
-For Quick Task Mode, close with the Runtime Contract mini-output only:
-
-- `result`
-- `evidence`
-- `risk`
-- `next_step`
-
-For relevant runs that change durable state, code, artefacts or gate status:
-
-- run relevant checks or state the test gap
-- never commit, push or open a PR automatically
-- include exactly one `Next step:`
-- include exactly one `Quality outlook:`