wogiflow 2.23.0 → 2.24.0

package/.claude/commands/wogi-epics.md

@@ -165,6 +165,18 @@ You MAY:
 
 **If the user provides 9 items, the epic MUST contain 9 stories (or items grouped into stories where every item appears as an acceptance criterion). Verify this with a reconciliation count before proceeding.**
 
+## P0 Specification-Quality Gates (v2.24.0+)
+
+Before finalizing an epic, run the same P0 gates `/wogi-story` uses (`scripts/flow-story-gates.js`):
+
+1. **Long Input Gate** — ≥40 lines or ≥5 items → route to `/wogi-extract-review`
+2. **Item Reconciliation** — already enforced via Anti-Deferral above; use `gates.reconcileItems()` to generate the manifest mechanically
+3. **Consumer Impact** — if epic description contains refactor/rename/migrate/etc. → grep consumers, list breaking count, recommend phased migration at ≥5
+4. **Scope-Confidence** — extract "new X"/"existing Y" assumptions → classify against codebase → surface CONTRADICTED/UNVERIFIED as Pending Clarifications
+5. **Intent Bootstrap Coordination** — schedule IGR bootstrap if missing; respects existing session-state flag
+
+All fail-open. Call `require('wogiflow/scripts/flow-story-gates')` directly in the epic-creation flow.
+
 ## Tips
 
 - **Start with epics for major features** - Break down into stories before implementation

package/.claude/commands/wogi-extract-review.md

@@ -182,6 +182,31 @@ Contradictions are resolved automatically using temporal ordering:
 
 The superseded statement is marked and excluded from story generation.
 
+## Item Manifest Export (v2.24.0+)
+
+After review is complete, the confirmed items can be exported as an **Item Manifest** in the format `/wogi-story`'s P0 item-reconciliation gate consumes directly. This closes the re-extraction loop — when `/wogi-start` routes a long input to `/wogi-extract-review`, the resulting manifest is handed to `/wogi-story` with `bypassLongInput: true` so story creation doesn't re-route back to extraction.
+
+```bash
+flow extract-zero-loss manifest    # JSON: { items, count, bypassLongInput, sourceSessionId, intentBootstrapScheduled }
+```
+
+AI flow:
+```
+User pastes large input
+  ↓
+/wogi-start detects line/item threshold → routes to /wogi-extract-review
+  ↓
+Extract → review → confirm completeness
+  ↓
+flow extract-zero-loss manifest → JSON
+  ↓
+/wogi-story --full-input=<manifest.items.join('\n')> --bypass-long-input
+  ↓
+Item Reconciliation gate sees bypassLongInput, skips Gate 1, runs Gates 2-5 normally
+```
+
+The manifest also carries an `intentBootstrapScheduled` flag so `/wogi-story` won't re-prompt the user if /wogi-extract-review already scheduled IGR bootstrap.
+
 ## Files
 
 | File | Location |

package/.claude/commands/wogi-feature.md

@@ -145,6 +145,41 @@ node node_modules/wogiflow/scripts/flow-feature.js progress ft-a1b2c3d4
 | → | In Progress (1-99%) |
 | ✓ | Completed (100%) |
 
+## Anti-Deferral Rule (MANDATORY — v2.24.0+)
+
+**When creating a feature from user input, EVERY item the user provided MUST become a tracked story within the feature.**
+
+You must NEVER:
+- Create stories for items 1-3 and silently skip items 4-6 because you judged them as "enhancements"
+- Label items as "deferred" or "long-term" and exclude them from the feature
+- Apply your own priority filter to decide which items deserve stories
+
+You MAY:
+- Assign different priorities (P0/P1/P2/P3) — but ALL items get stories
+- Suggest an execution order — but ALL items are tracked in the feature
+- Ask the user "Should I defer items 4-6?" — explicit user consent is the ONLY valid reason to exclude items
+
+**If the user provides 5 items, the feature MUST contain 5 stories (or items grouped into stories where every item appears as an acceptance criterion).** Verify with a reconciliation count before proceeding.
+
+## P0 Specification-Quality Gates (v2.24.0+)
+
+When creating a feature from user input, apply the same P0 gates `/wogi-story` uses (from `scripts/flow-story-gates.js`):
+
+1. **Long Input Gate** — ≥40 lines or ≥5 items → route to `/wogi-extract-review` first
+2. **Item Reconciliation** — ≥3 items → enumerate items as a manifest + verify every item maps to at least one story
+3. **Consumer Impact Analysis** — if the feature title/description contains refactor/rename/migrate/replace/consolidate/split/extract/move keywords → run `git grep` on seeded filenames, list likely consumers, recommend phased migration if ≥5 breaking consumers
+4. **Scope-Confidence Audit** — extract "new X"/"existing Y"/"the Z service" assumptions from the description, classify against codebase (VERIFIED/CONTRADICTED/UNVERIFIED), write to a Pending Clarifications section on the feature
+5. **Intent Bootstrap Coordination** — if IGR is enabled and artifacts missing, schedule bootstrap via session-state flag (do NOT duplicate-prompt)
+
+All gates fail-open. Use `flow-story-gates.js` directly:
+
+```javascript
+const gates = require('wogiflow/scripts/flow-story-gates');
+gates.reconcileItems(userInput);
+gates.analyzeConsumerImpact(title + ' ' + description);
+gates.auditScopeConfidence(description);
+```
+
 ## Tips
 
 - **Features represent user-facing capabilities** - Not technical components

package/.claude/commands/wogi-plan.md

@@ -182,6 +182,34 @@ When `/wogi-plan` is invoked with a description argument, it should:
 1. Create the plan structure in `.workflow/plans/`
 2. Enter Claude Code plan mode with the description: `EnterPlanMode` with the plan context
 
+## Anti-Deferral Rule (MANDATORY — v2.24.0+)
+
+**When creating a plan from user input, EVERY item the user provided MUST become a tracked epic or feature within the plan.**
+
+You must NEVER:
+- Create epics for items 1-3 and silently skip items 4-7 because you judged them as "enhancements" or "long-term"
+- Label items as "deferred" and exclude them from the plan
+- Apply your own filter to decide which items deserve tracking
+
+You MAY:
+- Assign different priorities (P0/P1/P2/P3) — but ALL items get epics/features
+- Suggest an execution order — but ALL items are tracked in the plan
+- Ask the user "Should I defer items 4-7?" — explicit user consent is the ONLY valid reason to exclude items
+
+**If the user provides 7 items, the plan MUST contain 7 tracked sub-items (epics or features, possibly grouped where every item appears as a criterion).** Verify with a reconciliation count before proceeding.
+
+## P0 Specification-Quality Gates (v2.24.0+)
+
+When creating a plan from user input, apply the same P0 gates `/wogi-story` uses (`scripts/flow-story-gates.js`):
+
+1. **Long Input Gate** — ≥40 lines or ≥5 items → route to `/wogi-extract-review`
+2. **Item Reconciliation** — ≥3 items → enumerate manifest + verify every item maps
+3. **Consumer Impact** — refactor keywords trigger a grep; ≥5 breaking consumers → recommend phased migration
+4. **Scope-Confidence** — extract "new X"/"existing Y"/"the Z service" claims; classify against codebase; surface contradictions as Pending Clarifications
+5. **Intent Bootstrap Coordination** — schedule IGR bootstrap if missing (don't re-prompt)
+
+All fail-open.
+
 ## Tips
 
 - **Plans are for strategic visibility** - Track high-level progress

package/.claude/commands/wogi-test-browser.md

@@ -328,3 +328,14 @@ Controlled by `.workflow/config.json`:
 - **WebMCP assertions**: ~100 tokens per step (tool call + JSON assertion)
 - **Savings**: ~95% token reduction for a 10-step test flow
 - **Bonus**: Deterministic results (no visual diff ambiguity)
+
+## Evidence Tier (v2.24.0+)
+
+A successful `/wogi-test-browser` run emits **Evidence Tier 4 (SHIPPED)** — the highest tier on the Completion Truth Gate scale. Browser-driven WebMCP tests exercise real DOM interactions with real event listeners, network calls, and state transitions.
+
+When reporting results:
+```json
+{ "evidenceTier": 4, "evidenceTierLabel": "SHIPPED" }
+```
+
+See `/wogi-test` for the full tier scale. L0/L1 tasks touching UI should reach Tier 4 before closing; Truth Gate (Step 3.9) will downgrade "done" claims that don't.

package/.claude/commands/wogi-test-generate.md

@@ -99,4 +99,15 @@ During `/wogi-start` Step 3, verify:
 - Run generated tests AFTER implementing → they should all pass
 - If any test passes before implementation → WARNING: test may be trivial
 
+## Evidence Tier (v2.24.0+)
+
+Generated tests that only assert structural properties (class exists, function has signature) emit **Evidence Tier 1 (STATIC)**. Tests that exercise actual behavior emit **Evidence Tier 2 (COMPILED)** once they pass. To reach Tier 3+ (interactive / shipped), tests must make real network or DOM calls — see `/wogi-test` (API/UI) and `/wogi-test-browser` for those.
+
+When recording test results in `.workflow/verifications/`, include:
+```json
+{ "evidenceTier": 1|2, "evidenceTierLabel": "STATIC"|"COMPILED" }
+```
+
+The Completion Truth Gate reads these labels to decide whether "tests pass" is sufficient to accept a "done" claim. L0/L1 tasks cannot close on Tier 1 alone.
+
 ARGUMENTS: {args}

package/.claude/commands/wogi-test.md

@@ -285,6 +285,31 @@ Include results in the summary:
 Generated Tests: [passed]/[total] passed
 ```
 
+## Evidence Tiers (v2.24.0+)
+
+Every test invocation should emit an **evidence tier** label that the Completion Truth Gate (Step 3.9 in `/wogi-start`) uses to accept or downgrade "done" claims. A task that claims completion without sufficient tier evidence gets surfaced as "implemented (unverified)" rather than rubber-stamped as done.
+
+| Tier | Label | What it means | Source |
+|------|-------|---------------|--------|
+| 0 | NONE | No test ran or all tests silently skipped | N/A |
+| 1 | STATIC | Code parses / type-checks cleanly | `flow lint`, `flow typecheck` |
+| 2 | COMPILED | Unit tests pass | `flow-test-integrity.js` generated/unit tests |
+| 3 | INTERACTIVE | API calls succeed end-to-end (HTTP round-trips, DB reads) | `flow-test-api.js`, `flow-test-ui.js` backend hits |
+| 4 | SHIPPED | UI interaction succeeds in a real browser (click, submit, see result) | `flow-test-ui.js` browser E2E |
+
+Output format (JSON mode):
+```json
+{
+  "passed": true,
+  "results": [...],
+  "evidenceTier": 3,
+  "evidenceTierLabel": "INTERACTIVE",
+  "gates": { "static": true, "unit": true, "api": true, "ui": false }
+}
+```
+
+Any `/wogi-start` task closing with `evidenceTier < 3` for features that touch UI or a service boundary will be flagged by the Truth Gate. L3 tasks (refactor/chore) accept tier 1–2. L0/L1 tasks require tier 3+.
+
 ## Important Notes
 
 - Testing is **disabled by default** — zero overhead for projects that don't use it

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wogiflow",
-  "version": "2.23.0",
+  "version": "2.24.0",
   "description": "AI-powered development workflow management system with multi-model support",
   "main": "lib/index.js",
   "bin": {
@@ -10,7 +10,7 @@
   },
   "scripts": {
     "flow": "./scripts/flow",
-    "test": "NODE_ENV=test node --test tests/auto-compact-prompt.test.js tests/flow-paths.test.js tests/flow-io.test.js tests/flow-config-loader.test.js tests/flow-damage-control.test.js tests/flow-output.test.js tests/flow-constants.test.js tests/flow-session-state.test.js tests/flow-hooks-integration.test.js tests/flow-utils.test.js tests/flow-security.test.js tests/flow-memory-db.test.js tests/flow-durable-session.test.js tests/flow-skill-matcher.test.js tests/flow-bridge.test.js tests/flow-proactive-compact.test.js tests/flow-cascade-completion.test.js tests/flow-capture-gate.test.js tests/flow-correction-detector-hybrid.test.js tests/flow-promote.test.js tests/flow-archive-runs.test.js tests/flow-memory.test.js tests/flow-hooks-pre-tool-helpers.test.js tests/flow-hooks-bugfix-scope-gate.test.js tests/flow-hooks-routing-gate.test.js tests/flow-hooks-phase-read-gate.test.js tests/flow-hooks-commit-log-gate.test.js tests/flow-hooks-deploy-gate.test.js tests/flow-hooks-todowrite-gate.test.js tests/flow-hooks-git-safety-gate.test.js tests/flow-hooks-scope-mutation-gate.test.js tests/flow-hooks-strike-gate.test.js tests/flow-hooks-component-check.test.js tests/flow-hooks-scope-gate.test.js tests/flow-hooks-implementation-gate.test.js tests/flow-hooks-research-gate.test.js tests/flow-hooks-loop-check.test.js tests/flow-hooks-manager-boundary-gate.test.js tests/flow-hooks-phase-gate.test.js tests/flow-hooks-pre-tool-orchestrator.test.js tests/flow-hooks-observation-capture.test.js tests/flow-hooks-task-gate.test.js tests/flow-durable-session-suspension.test.js tests/flow-health-mcp-scopes.test.js tests/flow-lean-config.test.js tests/flow-workspace-autopickup.test.js tests/flow-worker-boundary-gate.test.js tests/flow-worker-question-classifier.test.js tests/flow-completion-truth-gate-contradictions.test.js tests/flow-structure-sensor.test.js tests/flow-workspace-dispatch-tracking.test.js tests/flow-story-gates.test.js tests/flow-workspace-restart-handoff.test.js tests/flow-wogi-claude-wrapper.test.js tests/flow-wave1-integrations.test.js && NODE_ENV=test node tests/run-quality-gates.test.js",
+    "test": "NODE_ENV=test node --test tests/auto-compact-prompt.test.js tests/flow-paths.test.js tests/flow-io.test.js tests/flow-config-loader.test.js tests/flow-damage-control.test.js tests/flow-output.test.js tests/flow-constants.test.js tests/flow-session-state.test.js tests/flow-hooks-integration.test.js tests/flow-utils.test.js tests/flow-security.test.js tests/flow-memory-db.test.js tests/flow-durable-session.test.js tests/flow-skill-matcher.test.js tests/flow-bridge.test.js tests/flow-proactive-compact.test.js tests/flow-cascade-completion.test.js tests/flow-capture-gate.test.js tests/flow-correction-detector-hybrid.test.js tests/flow-promote.test.js tests/flow-archive-runs.test.js tests/flow-memory.test.js tests/flow-hooks-pre-tool-helpers.test.js tests/flow-hooks-bugfix-scope-gate.test.js tests/flow-hooks-routing-gate.test.js tests/flow-hooks-phase-read-gate.test.js tests/flow-hooks-commit-log-gate.test.js tests/flow-hooks-deploy-gate.test.js tests/flow-hooks-todowrite-gate.test.js tests/flow-hooks-git-safety-gate.test.js tests/flow-hooks-scope-mutation-gate.test.js tests/flow-hooks-strike-gate.test.js tests/flow-hooks-component-check.test.js tests/flow-hooks-scope-gate.test.js tests/flow-hooks-implementation-gate.test.js tests/flow-hooks-research-gate.test.js tests/flow-hooks-loop-check.test.js tests/flow-hooks-manager-boundary-gate.test.js tests/flow-hooks-phase-gate.test.js tests/flow-hooks-pre-tool-orchestrator.test.js tests/flow-hooks-observation-capture.test.js tests/flow-hooks-task-gate.test.js tests/flow-durable-session-suspension.test.js tests/flow-health-mcp-scopes.test.js tests/flow-lean-config.test.js tests/flow-workspace-autopickup.test.js tests/flow-worker-boundary-gate.test.js tests/flow-worker-question-classifier.test.js tests/flow-completion-truth-gate-contradictions.test.js tests/flow-structure-sensor.test.js tests/flow-workspace-dispatch-tracking.test.js tests/flow-story-gates.test.js tests/flow-workspace-restart-handoff.test.js tests/flow-wogi-claude-wrapper.test.js tests/flow-wave1-integrations.test.js tests/flow-wave2-integrations.test.js && NODE_ENV=test node tests/run-quality-gates.test.js",
     "test:syntax": "find scripts/ lib/ -name '*.js' -not -path '*/node_modules/*' -exec node --check {} +",
     "lint": "eslint scripts/ lib/ tests/",
     "lint:ci": "eslint scripts/ lib/ tests/ --max-warnings 0",

package/scripts/flow-extraction-review.js

@@ -390,6 +390,46 @@ function getConfirmedTasks() {
     }));
 }
 
+/**
+ * v2.24.0 — Export confirmed items as an "Item Manifest" compatible with
+ * /wogi-story's item-reconciliation gate (wf-63c0f4cc). Downstream callers
+ * (/wogi-story, /wogi-epics, /wogi-feature, /wogi-plan) can pass this to
+ * their P0 gates as `fullInput` and mark `bypassLongInput: true` so the
+ * re-extraction loop is skipped.
+ *
+ * @returns {{items: Array<string>, count: number, bypassLongInput: true, sourceSessionId: string, intentBootstrapScheduled: boolean}}
+ */
+function exportAsItemManifest() {
+  const session = loadReviewSession();
+  if (!session) throw new Error('No review session active');
+  if (!session.completeness_confirmed) {
+    throw new Error('Cannot export manifest: review not yet confirmed as complete');
+  }
+
+  const items = session.items
+    .filter(i => i.review_status === 'confirmed')
+    .map(i => (i.text || '').trim())
+    .filter(Boolean);
+
+  // Coordinate with Intent Bootstrap (see flow-story-gates.coordinateIntentBootstrap)
+  // so /wogi-start doesn't re-prompt if the user already scheduled bootstrap via
+  // /wogi-story during this session.
+  let intentBootstrapScheduled = false;
+  try {
+    const gates = require('./flow-story-gates');
+    const result = gates.coordinateIntentBootstrap();
+    intentBootstrapScheduled = !!(result && result.scheduled);
+  } catch (_err) { /* non-critical */ }
+
+  return {
+    items,
+    count: items.length,
+    bypassLongInput: true,
+    sourceSessionId: session.id || null,
+    intentBootstrapScheduled
+  };
+}
+
 // =============================================================================
 // DISPLAY HELPERS
 // =============================================================================
@@ -779,6 +819,7 @@ module.exports = {
 
   // Get results
   getConfirmedTasks,
+  exportAsItemManifest,  // v2.24.0 — Wave 2 alignment with /wogi-story P0 gates
 
   // Display
   formatReviewStatus,
@@ -858,6 +899,16 @@ if (require.main === module) {
       }
       break;
 
+    case 'manifest':
+      // v2.24.0 — export Item Manifest for downstream /wogi-story coordination
+      try {
+        const manifest = exportAsItemManifest();
+        console.log(JSON.stringify(manifest, null, 2));
+      } catch (err) {
+        console.error(`${c.red}✗ ${err.message}${c.reset}`);
+      }
+      break;
+
     default:
       console.log('Extraction Review Module');
       console.log('Commands:');