create-agdf 0.1.6 → 0.1.7

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

@@ -22,7 +22,7 @@ It reports:
 - Context Graph impact
 - open risks, blockers, retained fallbacks, and exit criteria
 - next permissible step
-- whether further quality follow-up is useful
+- whether further quality follow-up or a separate delivery closeout is useful
 
 ## Runtime Contract
 Use `../agdf-runtime-contract.md` for Quality Contract output, Context Graph fields, gate terms, and non-duplication rules.
@@ -85,7 +85,7 @@ If information is missing, state the gap instead of guessing.
 8. Name retained fallbacks and exit criteria.
 9. Set exactly one next permissible step.
 10. Set exactly one quality outlook.
-11. Add a commit-ready handoff only when code changes exist and the delivery state allows it.
+11. 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:
@@ -106,14 +106,6 @@ Use a compact structure:
 
 When Context Graph impact is relevant, include the fields from `../agdf-runtime-contract.md`.
 
-For code-changing closeouts that are commit-near, append:
-
-```text
-Commit title:
-Commit body:
-Migration/Rollout note:
-```
-
 ## Forbidden
 This skill must not:
 
@@ -121,4 +113,5 @@ This skill must not:
 - call `CD+Tests` complete, QA-ready, or release-ready
 - hide missing approvals
 - provide later-gate content while an earlier gate blocks
+- produce the operative commit/PR handoff owned by `agdf-delivery-closeout`
 - execute commit, push, or PR actions

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

@@ -24,7 +24,8 @@ Structured Delivery must not bypass missing approvals.
 - `CD+Tests` is implementation and test status only, not a delivery signal.
 - `agdf-code-review` standardizes the mandatory `CR` step, but does not replace QA.
 - `agdf-qa-gate` decides final `pass | revise | block`.
-- `agdf-release-or` reports the run, but does not replace QA.
+- `agdf-release-or` reports the run, but does not replace QA or produce the operative commit/PR handoff.
+- `agdf-delivery-closeout` owns the operative Git handoff text when QA/OR/UAT state allows it.
 
 ## Quality Contract Output
 

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

@@ -1,6 +1,6 @@
 {
   "name": "agdf",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
   "author": {
     "name": "AI-native Governance & Delivery Framework",
@@ -11,6 +11,7 @@
   "license": "Apache-2.0",
   "keywords": ["agentic", "governance", "delivery", "ai-native", "brownfield"],
   "skills": "./skills/",
+  "hooks": "./hooks/hooks.json",
   "interface": {
     "displayName": "AI Governance & Delivery Framework",
     "shortDescription": "Codex-first workflow skills for gated, auditable AI-assisted delivery.",

package/generated/plugins/agdf/hooks/hooks.json

@@ -5,7 +5,7 @@
                 "hooks": [
                     {
                         "type":         "command",
-                        "command":      "bash -lc 'for hook in \"${CODEX_HOME:-$HOME/.codex}\"/plugins/cache/*/agdf/*/hooks/session-start.sh \"$PWD/plugins/agdf/hooks/session-start.sh\" \"$(dirname \"$0\")/session-start.sh\"; do [ -f \"$hook\" ] && exec bash \"$hook\"; done; exit 0'",
+                        "command":      "bash -lc 'hook=\"${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}/hooks/session-start.sh\"; if [ -f \"$hook\" ]; then exec bash \"$hook\"; fi; hook=\"$PWD/plugins/agdf/hooks/session-start.sh\"; if [ -f \"$hook\" ]; then exec bash \"$hook\"; fi; exit 0'",
                         "statusMessage": "Loading AGDF..."
                     }
                 ]

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

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "id": "agdf",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "displayName": "AI Governance & Delivery Framework",
   "developerName": "AI-native Governance & Delivery Framework",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",

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

@@ -24,7 +24,8 @@ Structured Delivery must not bypass missing approvals.
 - `CD+Tests` is implementation and test status only, not a delivery signal.
 - `code-review` standardizes the mandatory `CR` step, but does not replace QA.
 - `qa-gate` decides final `pass | revise | block`.
-- `release-or` reports the run, but does not replace QA.
+- `release-or` reports the run, but does not replace QA or produce the operative commit/PR handoff.
+- `delivery-closeout` owns the operative Git handoff text when QA/OR/UAT state allows it.
 
 ## Quality Contract Output
 

package/generated/plugins/agdf/meta/agdf-tenets.md

@@ -16,7 +16,12 @@ you *MUST* honor the following **GENERIC TENETS**:
     Implementation should not be based on vague intent.
     A stable product contract defines accepted scope, acceptance criteria,
     non-goals, constraints and success measurement.
-    Without an approved PRD, no implementation may begin.
+    For Structured Delivery or product-semantically relevant implementation,
+    no implementation may begin without an approved PRD or an explicitly
+    equivalent product contract.
+    Quick Task Mode may still handle narrow local fixes, reviews, debugging
+    and tooling maintenance when no new product meaning, user capability,
+    architecture, policy or persistence decision is introduced.
 
 -   **Fail Closed**:
     When a necessary approval, input, or quality statement is missing,

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

@@ -22,7 +22,7 @@ It reports:
 - Context Graph impact
 - open risks, blockers, retained fallbacks, and exit criteria
 - next permissible step
-- whether further quality follow-up is useful
+- whether further quality follow-up or a separate delivery closeout is useful
 
 ## Runtime Contract
 Use `../../meta/agdf-runtime-contract.md` for Quality Contract output, Context Graph fields, gate terms, and non-duplication rules.
@@ -85,7 +85,7 @@ If information is missing, state the gap instead of guessing.
 8. Name retained fallbacks and exit criteria.
 9. Set exactly one next permissible step.
 10. Set exactly one quality outlook.
-11. Add a commit-ready handoff only when code changes exist and the delivery state allows it.
+11. 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:
@@ -106,14 +106,6 @@ Use a compact structure:
 
 When Context Graph impact is relevant, include the fields from `../../meta/agdf-runtime-contract.md`.
 
-For code-changing closeouts that are commit-near, append:
-
-```text
-Commit title:
-Commit body:
-Migration/Rollout note:
-```
-
 ## Forbidden
 This skill must not:
 
@@ -121,4 +113,5 @@ This skill must not:
 - call `CD+Tests` complete, QA-ready, or release-ready
 - hide missing approvals
 - provide later-gate content while an earlier gate blocks
+- produce the operative commit/PR handoff owned by `delivery-closeout`
 - execute commit, push, or PR actions

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-agdf",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "Bootstrap AGDF repository-local Codex plugin marketplaces, Copilot instructions, skills and control templates.",
   "type": "module",
   "files": [