gsdd-cli 0.19.1 → 0.19.2

package/bin/lib/health-truth.mjs

@@ -94,7 +94,7 @@ export function runTruthChecks(planningDir, frameworkDir, actualCheckIds, option
     warnings.push({
       id: 'W11',
       severity: 'WARN',
-      message: `Installed generated runtime and workflow-helper surfaces drift from current render output (${summarizeRuntimeFreshnessIssues(options.runtimeFreshnessReport)})`,
+      message: `Renderer-backed generated runtime and workflow-helper surfaces drift from current render output (${summarizeRuntimeFreshnessIssues(options.runtimeFreshnessReport)})`,
       fix: getRuntimeFreshnessRepairGuidance(options.runtimeFreshnessReport),
     });
   }

package/bin/lib/health.mjs

@@ -164,10 +164,10 @@ export function createCmdHealth(ctx) {
         if (!cat.hashes) continue;
         const result = detectModifications(cat.dir, cat.hashes);
         if (result.modified.length > 0) {
-          warnings.push({ id: 'W2', severity: 'WARN', message: `${cat.name}: ${result.modified.length} file(s) modified locally (${result.modified.join(', ')})`, fix: `Intentional? Run \`${cat.fixCommand}\` to reset` });
+          warnings.push({ id: 'W2', severity: 'WARN', message: `${cat.name}: ${result.modified.length} manifest-tracked installed file(s) modified locally (${result.modified.join(', ')})`, fix: `Intentional? Run \`${cat.fixCommand}\` to reset` });
         }
         if (result.missing.length > 0) {
-          warnings.push({ id: 'W3', severity: 'WARN', message: `${cat.name}: ${result.missing.length} file(s) missing from disk (${result.missing.join(', ')})`, fix: `Run \`${cat.fixCommand}\` to restore` });
+          warnings.push({ id: 'W3', severity: 'WARN', message: `${cat.name}: ${result.missing.length} manifest-tracked installed file(s) missing from disk (${result.missing.join(', ')})`, fix: `Run \`${cat.fixCommand}\` to restore` });
         }
       }
     }
@@ -201,16 +201,9 @@ export function createCmdHealth(ctx) {
       }
     }
 
-    // W6: No adapter surfaces detected
-    const adapterPaths = [
-      join(cwd, '.agents', 'skills'),
-      join(cwd, '.claude'),
-      join(cwd, '.opencode'),
-      join(cwd, '.codex'),
-    ];
-    const hasAnyAdapter = adapterPaths.some((p) => existsSync(p));
-    if (!hasAnyAdapter) {
-      warnings.push({ id: 'W6', severity: 'WARN', message: 'No adapter surfaces detected', fix: 'Run `npx -y gsdd-cli init --tools <platform>`' });
+    // W6: No generated workflow adapter surfaces detected
+    if (!hasAnyGeneratedWorkflowSurface(cwd)) {
+      warnings.push({ id: 'W6', severity: 'WARN', message: 'No generated workflow adapter surfaces detected', fix: 'Run `npx -y gsdd-cli init --tools <platform>`' });
     }
 
     const runtimeFreshnessReport = configOk && Array.isArray(ctx.workflows)
@@ -245,15 +238,15 @@ export function createCmdHealth(ctx) {
       });
     }
 
-    // I3: Which adapters are installed
-    const installedAdapters = [];
-    if (existsSync(join(cwd, '.agents', 'skills'))) installedAdapters.push('open-standard-skills');
-    if (existsSync(join(cwd, '.claude'))) installedAdapters.push('claude');
-    if (existsSync(join(cwd, '.opencode'))) installedAdapters.push('opencode');
-    if (existsSync(join(cwd, '.codex'))) installedAdapters.push('codex');
-    if (existsSync(join(cwd, 'AGENTS.md'))) installedAdapters.push('agents');
-    if (installedAdapters.length > 0) {
-      info.push({ id: 'I3', severity: 'INFO', message: `Adapters installed: ${installedAdapters.join(', ')}` });
+    // I3: Which runtime/governance surfaces are installed
+    const installedSurfaces = [];
+    if (hasGeneratedSkillSurface(cwd)) installedSurfaces.push('open-standard-skills');
+    if (hasGeneratedClaudeSurface(cwd)) installedSurfaces.push('claude');
+    if (hasGeneratedOpenCodeSurface(cwd)) installedSurfaces.push('opencode');
+    if (hasGeneratedCodexSurface(cwd)) installedSurfaces.push('codex');
+    if (existsSync(join(cwd, 'AGENTS.md'))) installedSurfaces.push('root AGENTS.md governance-only');
+    if (installedSurfaces.length > 0) {
+      info.push({ id: 'I3', severity: 'INFO', message: `Installed runtime/governance surfaces: ${installedSurfaces.join(', ')}` });
     }
 
     // --- Verdict ---
@@ -281,6 +274,78 @@ export function createCmdHealth(ctx) {
   };
 }
 
+function hasAnyGeneratedWorkflowSurface(cwd) {
+  return hasGeneratedSkillSurface(cwd)
+    || hasGeneratedClaudeEntrySurface(cwd)
+    || hasGeneratedOpenCodeEntrySurface(cwd);
+}
+
+function hasGeneratedSkillSurface(cwd) {
+  return hasGeneratedSkillDirectory(join(cwd, '.agents', 'skills'));
+}
+
+function hasGeneratedClaudeSurface(cwd) {
+  return hasGeneratedClaudeEntrySurface(cwd)
+    || hasGeneratedMarkdownFile(join(cwd, '.claude', 'agents'));
+}
+
+function hasGeneratedClaudeEntrySurface(cwd) {
+  return hasGeneratedSkillDirectory(join(cwd, '.claude', 'skills'))
+    || hasGeneratedMarkdownFile(join(cwd, '.claude', 'commands'));
+}
+
+function hasGeneratedOpenCodeSurface(cwd) {
+  return hasGeneratedOpenCodeEntrySurface(cwd)
+    || hasGeneratedMarkdownFile(join(cwd, '.opencode', 'agents'));
+}
+
+function hasGeneratedOpenCodeEntrySurface(cwd) {
+  return hasGeneratedMarkdownFile(join(cwd, '.opencode', 'commands'))
+}
+
+function hasGeneratedCodexSurface(cwd) {
+  return hasGeneratedTomlFile(join(cwd, '.codex', 'agents'));
+}
+
+function hasGeneratedSkillDirectory(dir) {
+  try {
+    return readdirSync(dir, { withFileTypes: true }).some((entry) => {
+      return entry.isDirectory()
+        && entry.name.startsWith('gsdd-')
+        && existsSync(join(dir, entry.name, 'SKILL.md'));
+    });
+  } catch {
+    return false;
+  }
+}
+
+function hasGeneratedMarkdownFile(dir) {
+  try {
+    return readdirSync(dir, { withFileTypes: true }).some((entry) => {
+      return entry.isFile() && entry.name.startsWith('gsdd-') && entry.name.endsWith('.md');
+    });
+  } catch {
+    return false;
+  }
+}
+
+function hasGeneratedTomlFile(dir) {
+  try {
+    return readdirSync(dir, { withFileTypes: true }).some((entry) => {
+      return entry.isFile() && entry.name.startsWith('gsdd-') && entry.name.endsWith('.toml');
+    });
+  } catch {
+    return false;
+  }
+}
+
 function isFrameworkSourceRepo(cwd) {
-  return existsSync(join(cwd, 'distilled', 'templates')) && existsSync(join(cwd, 'distilled', 'workflows'));
+  if (!existsSync(join(cwd, 'distilled', 'templates')) || !existsSync(join(cwd, 'distilled', 'workflows'))) return false;
+  if (!existsSync(join(cwd, 'bin', 'gsdd.mjs')) || !existsSync(join(cwd, 'package.json'))) return false;
+  try {
+    const pkg = JSON.parse(readFileSync(join(cwd, 'package.json'), 'utf-8'));
+    return pkg.name === 'gsdd-cli';
+  } catch {
+    return false;
+  }
 }

package/distilled/DESIGN.md

@@ -958,20 +958,20 @@ Implementation lives under `bin/lib/`:
 | E8 | ERROR | `.planning/templates/` missing critical root files (`spec.md`, `roadmap.md`, `auth-matrix.md`) |
 | E9 | ERROR | `.planning/templates/brownfield-change/` missing or missing critical files (`CHANGE.md`, `HANDOFF.md`, `VERIFICATION.md`) |
 | W1 | WARN | `generation-manifest.json` missing |
-| W2 | WARN | Template files modified locally (hash mismatch vs manifest) |
-| W3 | WARN | Template/role files missing from disk but listed in manifest |
+| W2 | WARN | Manifest-tracked installed templates/helpers modified locally (hash mismatch vs manifest) |
+| W3 | WARN | Manifest-tracked installed templates/helpers missing from disk but listed in manifest |
 | W4 | WARN | Active non-archived phases marked in progress/done are missing from `.planning/phases/` |
 | W5 | WARN | Phase artifact set has PLAN but no matching SUMMARY (stale in-progress) |
-| W6 | WARN | No adapter surfaces detected |
+| W6 | WARN | No generated workflow adapter surfaces detected |
 | W7 | WARN | `distilled/DESIGN.md` health check table differs from implemented check IDs |
 | W8 | WARN | `distilled/README.md` workflow inventory differs from `distilled/workflows/` |
 | W9 | WARN | `.internal-research/gaps.md` references missing repo-local paths |
 | W10 | WARN | ROADMAP lifecycle status drift, including requirement checkbox and overview/detail phase status mismatches |
-| W11 | WARN | Installed generated runtime/helper surfaces drift from current render output |
+| W11 | WARN | Renderer-backed generated runtime/helper surfaces drift from current render output |
 | W12 | WARN | Planning state drifted since last recorded session (fingerprint mismatch) |
 | I1 | INFO | Generation manifest `frameworkVersion` differs from current `FRAMEWORK_VERSION` |
 | I2 | INFO | Phase completion count from ROADMAP |
-| I3 | INFO | Which adapters are installed |
+| I3 | INFO | Which runtime/governance surfaces are installed |
 
 **Verdict logic:**
 - Any ERROR → `broken` (exit code 1)
@@ -994,7 +994,9 @@ Implementation lives under `bin/lib/`:
 
 5. **Reuses existing modules.** `readManifest()` and `detectModifications()` from `manifest.mjs` handle W1-W3. `isProjectInitialized()` pattern from `models.mjs` handles the pre-init guard. Truth checks stay read-only and operate on repo-local artifacts only when those framework files exist.
 
-6. **Framework-source mode skips installed-project template checks.** Inside the GSDD framework repo itself, `distilled/templates/` is the source of truth and `.planning/templates/` is intentionally absent. `npx -y gsdd-cli health` therefore skips the installed-project template/manifest checks (E3-E9, W1-W3) in framework-source mode instead of producing false positives during self-health runs.
+6. **Framework-source mode skips installed-project template checks only for the actual source repo.** Inside the GSDD framework repo itself, `distilled/templates/` is the source of truth and `.planning/templates/` can be intentionally absent. `npx -y gsdd-cli health` therefore skips installed-project template/manifest checks (E3-E9, W1-W3) only when source-repo identity signals also match (`package.json` name plus CLI source), avoiding false suppression in copied or unusual initialized repos that happen to contain `distilled/templates` and `distilled/workflows`.
+
+7. **Generated adapters and governance are reported separately.** W6 checks generated workflow entry surfaces (`.agents/skills`, Claude skills/commands, OpenCode commands) and does not treat root `AGENTS.md`, native checker agents, or Codex native checker TOML as workflow adapters. Codex CLI uses `.agents/skills` as its workflow entry path. I3 may still report native agents and root `AGENTS.md` as installed runtime/governance surfaces so users understand what exists without confusing those files with executable workflow discovery.
 
 **What was removed vs GSD:**
 - `--repair` flag and associated repair actions

package/distilled/workflows/new-project.md

@@ -20,7 +20,7 @@ When `autoAdvance: true`, this workflow runs non-interactively:
 
 5. **Keep quality gates:** All quality checks in `<spec_creation>` and `<roadmap_creation>` still apply. Thoroughness is preserved; only user wait-points are removed.
 
-6. **After completion:** Report what was created and any assumptions inferred from the brief. Do NOT auto-advance to planning — the user or CI system decides when to start planning.
+6. **After completion:** Report what was created and any assumptions inferred from the brief. Do NOT auto-progress into plan, execute, verify, release, or delivery. The user or CI system must start any later lifecycle workflow explicitly.
 
 All other sections (`<detect_mode>`, `<codebase_context>`, `<research>`, `<spec_creation>`, `<roadmap_creation>`, `<success_criteria>`) execute normally. Auto mode bypasses: the `<questioning>` section, both `<approval_gate>` blocks, the user question in `<project_principles>`, and the user question in `<capability_gates>`. All other workflow logic executes normally.
 </auto_mode>
@@ -33,8 +33,8 @@ Before starting, read these files (if they exist):
 4. Project root files: `package.json`, `README.md`, main entry point, `.gitignore`
 5. `.planning/config.json` — The deterministic project settings. Key fields:
    - `researchDepth`: balanced | fast | deep — controls research thoroughness
-   - `parallelization`: true | false � whether to run delegate work in parallel when the platform supports it; when false, run the same delegates sequentially
-   - `workflow.research`: true | false — whether to do SOTA research before spec
+   - `parallelization`: true | false - whether to run delegate work in parallel when the platform supports it; when false, run the same delegates sequentially
+   - `workflow.research`: true | false - whether to do domain research before spec
    - `workflow.planCheck`: true | false — whether plan-check agent runs later
    - `workflow.verifier`: true | false — whether verifier runs after execution
    - `modelProfile`: balanced | quality | budget — model selection hint
@@ -44,7 +44,6 @@ Before starting, read these files (if they exist):
 </load_context>
 
 <project_principles>
-**(SOTA Insight: Derived from Spec-Kit)**
 Before diving into technical specifications, establish the core governing principles of the project.
 If `autoAdvance: true` in `.planning/config.json`, skip this question. Infer core principles
 from the project brief (code quality signals, constraint language, scope decisions) and note
@@ -161,7 +160,7 @@ Before creating a spec, you MUST have clear answers to:
 - **3-5 rounds minimum** for non-trivial projects
 
 ### Categorizing Requirements (Crucial)
-As the user provides answers, you must mentally categorize the features they request using the SOTA framework:
+As the user provides answers, you must mentally categorize the features they request:
 1. **Table Stakes**: Features users absolutely expect. Without them, your product feels broken (e.g., password reset).
 2. **Differentiators**: Features that set this project apart from competitors.
 3. **Out of Scope**: Explicit anti-requirements for v1 to prevent scope creep.
@@ -202,28 +201,27 @@ MANDATORY STEP. After the goal is clarified but BEFORE writing any specs.
 
 **Check config first:** Read `.planning/config.json`.
 - If `workflow.research: false` → skip this section entirely, go to `<spec_creation>`.
-- If `researchDepth: "fast"` � use the same 4 specialists below, then synthesize `SUMMARY.md` inline. Faster and cheaper; acceptable for well-known domains.
-- If `researchDepth: "balanced"` or `"deep"` � use the same 4 specialists below plus the synthesizer (default).
+- If `researchDepth: "fast"` - use the same 4 specialists below, then synthesize `SUMMARY.md` inline. Faster and cheaper; acceptable for well-known domains.
+- If `researchDepth: "balanced"` or `"deep"` - use the same 4 specialists below plus the synthesizer (default).
 
-### Why Parallel Specialists, Not One Generalist
-**(SOTA: Anthropic Agent Teams, OpenAI Multi-Agents — 90.2% performance improvement for complex research tasks)**
+### Why Specialists, Not One Generalist
 
 DO NOT research in this main thread — noisy intermediate output pollutes the context window.
 DO NOT use a single generalist to write all research files — domain switching degrades quality.
 
 Use the same 4 specialized researchers every time. The difference is execution order and synthesis mode.
-- If `parallelization: true` and your platform supports parallel execution (`run_in_background=true`, async tasks, etc.) � run all 4 simultaneously.
-- If `parallelization: false` or your platform lacks parallel execution � run the same 4 researchers sequentially.
-- If `researchDepth: "fast"` � synthesize inline after the 4 researcher outputs return.
-- If `researchDepth: "balanced"` or `"deep"` � use the synthesizer delegate after the 4 researcher outputs are written.
+- If `parallelization: true` and your platform supports parallel execution (`run_in_background=true`, async tasks, etc.) - run all 4 simultaneously.
+- If `parallelization: false` or your platform lacks parallel execution - run the same 4 researchers sequentially.
+- If `researchDepth: "fast"` - synthesize inline after the 4 researcher outputs return.
+- If `researchDepth: "balanced"` or `"deep"` - use the synthesizer delegate after the 4 researcher outputs are written.
 
 
 ```
-◆ Spawning 4 researchers in parallel...
-  → Stack research        → .planning/research/STACK.md
-  → Features research     → .planning/research/FEATURES.md
-  → Architecture research → .planning/research/ARCHITECTURE.md
-  → Pitfalls research     → .planning/research/PITFALLS.md
+Spawning 4 researchers...
+  -> Stack research        -> .planning/research/STACK.md
+  -> Features research     -> .planning/research/FEATURES.md
+  -> Architecture research -> .planning/research/ARCHITECTURE.md
+  -> Pitfalls research     -> .planning/research/PITFALLS.md
 ```
 
 Ensure `.planning/research/` directory exists before spawning.
@@ -234,7 +232,7 @@ Parallel: (use parallelization value from .planning/config.json)
 Context: Project goal: [user's stated goal]. Milestone context: [greenfield|subsequent]. DO NOT share conversation history.
 Instruction: Read `.planning/templates/delegates/researcher-stack.md` for full task instructions. Apply the project goal and milestone context provided above.
 Output: `.planning/research/STACK.md`
-Return: 3-5 sentence summary to Orchestrator.
+Return: 3-5 sentence summary to Orchestrator; full findings stay in the output artifact.
 Guardrails: Max Agent Hops = 3.
 </delegate>
 
@@ -244,7 +242,7 @@ Parallel: (use parallelization value from .planning/config.json)
 Context: Project goal: [user's stated goal]. Milestone context: [greenfield|subsequent]. DO NOT share conversation history.
 Instruction: Read `.planning/templates/delegates/researcher-features.md` for full task instructions. Apply the project goal and milestone context provided above.
 Output: `.planning/research/FEATURES.md`
-Return: 3-5 sentence summary to Orchestrator.
+Return: 3-5 sentence summary to Orchestrator; full findings stay in the output artifact.
 Guardrails: Max Agent Hops = 3.
 </delegate>
 
@@ -254,7 +252,7 @@ Parallel: (use parallelization value from .planning/config.json)
 Context: Project goal: [user's stated goal]. Milestone context: [greenfield|subsequent]. DO NOT share conversation history.
 Instruction: Read `.planning/templates/delegates/researcher-architecture.md` for full task instructions. Apply the project goal and milestone context provided above.
 Output: `.planning/research/ARCHITECTURE.md`
-Return: 3-5 sentence summary to Orchestrator.
+Return: 3-5 sentence summary to Orchestrator; full findings stay in the output artifact.
 Guardrails: Max Agent Hops = 3.
 </delegate>
 
@@ -264,14 +262,14 @@ Parallel: (use parallelization value from .planning/config.json)
 Context: Project goal: [user's stated goal]. Milestone context: [greenfield|subsequent]. DO NOT share conversation history.
 Instruction: Read `.planning/templates/delegates/researcher-pitfalls.md` for full task instructions. Apply the project goal and milestone context provided above.
 Output: `.planning/research/PITFALLS.md`
-Return: 3-5 sentence summary to Orchestrator.
+Return: 3-5 sentence summary to Orchestrator; full findings stay in the output artifact.
 Guardrails: Max Agent Hops = 3.
 </delegate>
 
 **After all 4 researchers complete**, synthesize based on `researchDepth`:
 
 **If `researchDepth: "fast"`:** Synthesize inline.
-You hold 4 × 3-5 sentence summaries. Write `.planning/research/SUMMARY.md` directly using `.planning/templates/research/summary.md`. Cross-reference the summaries. Do NOT spawn another agent.
+You hold 4 x 3-5 sentence summaries. Write `.planning/research/SUMMARY.md` directly using `.planning/templates/research/summary.md`. Cross-reference the summaries. Do NOT spawn another agent.
 
 **If `researchDepth: "balanced"` or `"deep"`:** Spawn synthesizer to read the full research files.
 
@@ -281,7 +279,7 @@ Parallel: false
 Context: Researcher summaries returned above. DO NOT share conversation history.
 Instruction: Read `.planning/templates/delegates/researcher-synthesizer.md` for full task instructions.
 Output: `.planning/research/SUMMARY.md`
-Return: 5-7 bullet key findings to Orchestrator.
+Return: 5-7 bullet key findings to Orchestrator; full synthesis stays in the output artifact.
 Guardrails: Max Agent Hops = 2. Do not do new research — synthesize only.
 </delegate>
 
@@ -293,7 +291,7 @@ Display key findings before moving to spec creation.
 - [ ] All 4 specialist files written to `.planning/research/`
 - [ ] SUMMARY.md written with "Implications for Roadmap" section populated
 - [ ] Negative claims verified with current web docs (not training data)
-- [ ] Confidence levels assigned: ✅ verified, ⚠️ likely, ❓ uncertain
+- [ ] Confidence levels assigned: verified | likely | uncertain
 
 **Commit**: `docs: add domain research`
 </research>
@@ -301,7 +299,7 @@ Display key findings before moving to spec creation.
 **STOP. Research is complete. Do NOT write any application code. Proceed to spec creation below. Your job now is to produce SPEC.md and ROADMAP.md — not to build the project.**
 
 <data_schema_definition>
-Before writing SPEC.md, define core Data Models/Typed Schemas *(SOTA: GitHub Blog — "Multi-agent workflows often fail")*. Multi-agent systems require typed schemas to pass reliable state. These schemas MUST be included in SPEC.md (see item 7 in `<spec_creation>` below). Also define Done-When verification criteria for every requirement (see item 8). *SPEC.md defines WHAT, not HOW — do not include implementation tasks.*
+Before writing SPEC.md, define core Data Models/Typed Schemas. Multi-agent handoffs require typed schemas to pass reliable state. These schemas MUST be included in SPEC.md (see item 7 in `<spec_creation>` below). Also define Done-When verification criteria for every requirement (see item 8). *SPEC.md defines WHAT, not HOW - do not include implementation tasks.*
 </data_schema_definition>
 
 <spec_creation>
@@ -312,15 +310,14 @@ After the subagent research completes, synthesize EVERYTHING into `SPEC.md`:
 3. **Requirements have IDs**: `AUTH-01`, `DATA-02`, `UI-03`
 4. **Requirements are ordered** by priority within each category
 5. **Out of Scope is populated** — includes things the developer explicitly said "not now" AND anti-features found in Research.
-6. **Key Decisions are logged** — any choices made during questioning or dictated by the SOTA research.
-7. **Typed Data Schemas** *(SOTA: GitHub Blog — "Multi-agent workflows often fail")*: explicitly define the core Data Models/Typed Schemas the project will use (e.g., `type UserProfile = { id: number; plan: 'free' | 'pro' }`). Multi-agent systems require typed schemas to pass reliable state; natural language instructions fail across agent handoffs. *SPEC.md defines WHAT, not HOW — do not include implementation tasks.*
-8. **Done-When Verification Chain** *(SOTA: Cyanluna)*: For EVERY requirement in the "Must Have (v1)" section, define a clear, verifiable `[Done-When: ...]` criterion. "User can log in" must become "User can log in [Done-When: Login form submits, JWT is received, and User is redirected to Dashboard]". No exceptions.
+6. **Key Decisions are logged** — any choices made during questioning or dictated by the research.
+7. **Typed Data Schemas**: explicitly define the core Data Models/Typed Schemas the project will use (e.g., `type UserProfile = { id: number; plan: 'free' | 'pro' }`). Multi-agent handoffs require typed schemas to pass reliable state; natural language instructions fail across agent handoffs. *SPEC.md defines WHAT, not HOW - do not include implementation tasks.*
+8. **Done-When Verification Chain**: For EVERY requirement in the "Must Have (v1)" section, define a clear, verifiable `[Done-When: ...]` criterion. "User can log in" must become "User can log in [Done-When: Login form submits, JWT is received, and User is redirected to Dashboard]". No exceptions.
 9. **Capability & Security Gates**: Handle per the `<capability_gates>` section at the end of this `<spec_creation>` block.
 10. **Authorization Matrix (optional)**: For projects with multiple user roles or protected resources, create `.planning/AUTH_MATRIX.md` using the template at `.planning/templates/auth-matrix.md`. The integration checker will use this matrix for systematic auth verification during milestone audits.
 11. **ROADMAP phase status is initialized** with Phase 1 marked `[ ]` / not started using the roadmap template's phase-status language.
 
 <capability_gates>
-**(SOTA Insight: Derived from OpenFang - "16 Security Systems & Capability Gates")**
 Before finishing SPEC.md, explicitly define what the agents are NOT allowed to do automatically without human approval.
 If `autoAdvance: true`, skip this question. Add a deferred placeholder to SPEC.md:
 "## Capability & Security Gates\n_Deferred — auto mode cannot elicit gate preferences; requires explicit review before production deployment._"
@@ -410,7 +407,7 @@ Init is DONE when ALL of these are true:
 
 - [ ] Codebase audit completed (brownfield) OR greenfield confirmed
 - [ ] Developer was questioned in depth (3+ rounds for non-trivial projects) — [interactive only; skip when autoAdvance: true]
-- [ ] Research subagent spawned and SOTA patterns retrieved
+- [ ] Research subagent spawned and domain patterns retrieved
 - [ ] `SPEC.md` exists with testable requirements, out-of-scope, and current state
 - [ ] SPEC.md was reviewed and approved by the developer — [interactive only; skip when autoAdvance: true]
 - [ ] ROADMAP.md exists with phases, success criteria, and requirement mapping

package/distilled/workflows/quick.md

@@ -169,9 +169,9 @@ Read `.planning/config.json`.
 If the checker returns `issues_found` with blockers and this is the first cycle:
 1. Send the issue list back to the planner for targeted revision of the plan file.
 2. Re-run the checker once more.
-3. If blockers remain after 1 revision cycle, store `$CHECKER_ISSUES` for display in the plan preview. Do NOT block — the user decides in Step 3.7.
+3. If blockers remain after 1 revision cycle, store `$CHECKER_ISSUES` for display in the plan preview and set `$RISK_ACCEPTANCE_REQUIRED=true`. Do not execute from default Enter; the user must explicitly accept the known risk in Step 3.7.
 
-If the checker returns `passed`, or `workflow.planCheck` is false, `$CHECKER_ISSUES` is empty.
+If the checker returns `passed`, or `workflow.planCheck` is false, `$CHECKER_ISSUES` is empty and `$RISK_ACCEPTANCE_REQUIRED=false`.
 
 ---
 
@@ -222,14 +222,18 @@ If `$CHECKER_ISSUES` is non-empty, append:
 Plan check issues: {$CHECKER_ISSUES}
 ```
 
-Present options (default-yes — pressing Enter proceeds):
-- If `$SCOPE_WARNING` is empty: `[Enter to proceed / edit description / abort]`
-- If `$SCOPE_WARNING` contains `/gsdd-new-project`: `[Enter to proceed / switch to /gsdd-new-project / edit description / abort]`
+Present options:
+- If `$CHECKER_ISSUES` is non-empty: `[type "proceed despite issues" to execute / edit description / abort]`
+- Otherwise if `$SCOPE_WARNING` is empty: `[Enter to proceed / edit description / abort]`
+- Otherwise if `$SCOPE_WARNING` contains `/gsdd-new-project`: `[Enter to proceed / switch to /gsdd-new-project / edit description / abort]`
 - Otherwise if `$SCOPE_WARNING` contains `/gsdd-map-codebase`: `[Enter to proceed / switch to /gsdd-map-codebase / edit description / abort]`
 - Otherwise if `$SCOPE_WARNING` is non-empty: `[Enter to proceed / switch to /gsdd-plan / edit description / abort]`
 
+Default-yes applies only when `$CHECKER_ISSUES` is empty. When unresolved checker blockers remain, pressing Enter must not execute; repeat the issues and ask for `proceed despite issues`, `edit description`, or `abort`.
+
 Handle response:
-- **Enter (or "yes"):** proceed to Step 4.
+- **Enter (or "yes") when `$CHECKER_ISSUES` is empty:** proceed to Step 4.
+- **"proceed despite issues" when `$CHECKER_ISSUES` is non-empty:** proceed to Step 4 and record the explicit risk acceptance in the quick summary.
 - **"edit description":** clean up the task directory, then return to Step 1 with `$DESCRIPTION` pre-filled as the starting point.
 - **"switch to /gsdd-new-project":** clean up the task directory, then stop quick workflow and report: "Use `/gsdd-new-project` to define or intentionally widen the work into full lifecycle planning. Task description: {$DESCRIPTION}"
 - **"switch to /gsdd-map-codebase":** clean up the task directory, then stop quick workflow and report: "Use `/gsdd-map-codebase` for a deeper brownfield baseline before quick work. Task description: {$DESCRIPTION}"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gsdd-cli",
-  "version": "0.19.1",
+  "version": "0.19.2",
   "description": "Workspine — a repo-native delivery spine for long-horizon AI-assisted work, with directly validated support for Claude Code, Codex CLI, and OpenCode, published as gsdd-cli.",
   "type": "module",
   "bin": {