create-agdf 0.4.5 → 0.4.7

package/bin/create-agdf.js

@@ -1723,6 +1723,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 +1769,7 @@ function buildStatusCard({
   findings = [],
 }) {
   const qualityOutlook = deriveQualityOutlook(runState, findings);
+  const postApproval = postApprovalTransition(missingApproval);
   return {
     mode: extractField(runState.content ?? "", "mode") || "unknown",
     status,
@@ -1744,6 +1779,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 +2024,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 +2070,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 +2130,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 +2139,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,

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/plugins/agdf/.codex-plugin/plugin.json

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

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

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "id": "agdf",
-  "version": "0.4.5",
+  "version": "0.4.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

@@ -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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-agdf",
-  "version": "0.4.5",
+  "version": "0.4.7",
   "description": "Bootstrap AGDF repository-local plugin files, Copilot/OpenCode instructions, skills, control files and machine-readable checks.",
   "type": "module",
   "files": [