npm - wogiflow - Versions diffs - 2.23.0 → 2.25.0 - Mend

wogiflow 2.23.0 → 2.25.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (14) hide show

package/.claude/commands/wogi-decide.md +40 -0
package/.claude/commands/wogi-epics.md +12 -0
package/.claude/commands/wogi-extract-review.md +25 -0
package/.claude/commands/wogi-feature.md +35 -0
package/.claude/commands/wogi-init.md +29 -0
package/.claude/commands/wogi-learn.md +46 -0
package/.claude/commands/wogi-onboard.md +26 -0
package/.claude/commands/wogi-plan.md +28 -0
package/.claude/commands/wogi-test-browser.md +11 -0
package/.claude/commands/wogi-test-generate.md +11 -0
package/.claude/commands/wogi-test.md +25 -0
package/.claude/commands/wogi-triage.md +41 -0
package/package.json +2 -2
package/scripts/flow-extraction-review.js +51 -0

package/.claude/commands/wogi-decide.md CHANGED Viewed

@@ -304,6 +304,46 @@ In `config.json`:
 }
 ```
+## Rule-Creation Adversary (v2.25.0+ — OPTIONAL but recommended for ambiguous rules)
+When creating a non-trivial rule (anything beyond pure preference-setting like "always use semicolons"), spawn an adversary on a different model (default `sonnet` via `config.researchReasoningGate.tier3.adversaryModel`) to stress-test the proposed rule BEFORE it lands in `decisions.md`.
+```
+Spawn Agent (subagent_type: general-purpose, model: <adversaryModel>):
+Input:
+  Proposed rule title: <title>
+  Proposed rule body: <body>
+  User's original phrasing: <literal request>
+Prompt:
+  You are the rule-creation adversary.
+  1. Edge cases: name 3 situations where following this rule would produce
+     worse outcomes than NOT following it.
+  2. Interpretation: are there 2+ reasonable interpretations? If yes, list
+     them and pick the one the user most likely meant.
+  3. Scope creep: could this rule be over-applied to situations the user
+     didn't intend? Suggest scope qualifiers.
+  4. Verdict:
+     - ACCEPT   — ship as-is
+     - CLARIFY  — multiple interpretations; ask user
+     - NARROW   — over-application risk; add scope qualifiers
+     - REJECT   — edge cases dominate; more harm than good
+  Output JSON: {
+    "verdict", "edge_cases", "interpretations",
+    "scope_qualifiers", "suggested_revision"
+  }
+```
+Process:
+- **ACCEPT** → proceed with rule creation
+- **CLARIFY** → ask user to pick interpretation
+- **NARROW** → show scope qualifier; ask user to approve
+- **REJECT** → surface edge cases; require explicit override
+Fail-open: adversary unavailable → proceed with standard flow. User confirmation is still present.
 ## Files
 | Action | File |

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

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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-init.md CHANGED Viewed

@@ -1209,3 +1209,32 @@ Say "show me the rules" or "what patterns are we using?" anytime.
 ### If user cancels mid-wizard
 - Save progress to `.workflow/state/setup-progress.json`
 - Next run can offer to resume
+## v2.25.0+ — Modern Config Scaffolding (MANDATORY)
+New projects MUST be initialized with the following modern-stack config blocks explicitly written to `.workflow/config.json` so users can see + tune them (defaults-only inheritance is fine for behavior, but visibility matters for learning):
+```json
+{
+  "intentGroundedReasoning": { "enabled": true },
+  "taskBoundaryReset": {
+    "enabled": true,
+    "maxRestartsPerSession": 50
+  },
+  "storyFlow": {
+    "consumerImpactAnalysis": { "enabled": true, "breakingThreshold": 5 },
+    "scopeConfidenceAudit": { "enabled": true },
+    "itemReconciliation": { "enabled": true, "minItems": 3 }
+  },
+  "longInputGate": { "enabled": true, "lineThreshold": 40 },
+  "researchReasoningGate": {
+    "enabled": true,
+    "tier2": { "enabled": true },
+    "tier3": { "enabled": true, "adversaryModel": "sonnet" }
+  }
+}
+```
+These capabilities (IGR, task-boundary restart, P0 story gates, long-input routing, research reasoning gate) have proven out in 2.22+ releases. New users should NOT have to manually enable them via `flow migrate-igr` or equivalent — they are active from the first session.
+If onboarding a workspace (multi-repo), also ensure `workspace.autoPickupChannelDispatches: true` and the 2.22.x restart-handoff settings are present.

package/.claude/commands/wogi-learn.md CHANGED Viewed

@@ -275,6 +275,52 @@ In `config.json`:
 }
 ```
+## Promotion Adversary (v2.25.0+ — MANDATORY)
+Before promoting a pattern from `feedback-patterns.md` to `decisions.md`, run a **Promotion Adversary** on a different model. Rationale: same-model self-critique rubber-stamps. The adversary checks whether the N events that triggered promotion share an actual root cause (genuine recurrence) vs. superficial similarity with different underlying causes (false recurrence — common when the pattern detector just matched keywords).
+```
+Spawn Agent (subagent_type: general-purpose,
+             model: config.researchReasoningGate.tier3.adversaryModel, default 'sonnet'):
+Input:
+  Proposed rule: <title + body>
+  Triggering events: [
+    { date, request, correction },
+    { date, request, correction },
+    { date, request, correction }
+  ]
+Prompt:
+  You are the rule-promotion adversary.
+  Do these N events actually share a root cause, or are they superficially
+  similar events with different underlying issues?
+  1. For each event: describe the root cause in your own words.
+  2. List what's common to all N root causes.
+  3. List what's different between them.
+  4. Verdict:
+     - SAME_PATTERN  — genuine recurrence; rule is well-founded
+     - MIXED         — N-1 match but one event has a different root cause
+     - DIFFERENT     — surface-similar only; no unifying pattern
+  Output JSON:
+  {
+    "verdict": "SAME_PATTERN" | "MIXED" | "DIFFERENT",
+    "root_causes": [...],
+    "commonalities": [...],
+    "differences": [...],
+    "suggested_rule_scope": "as_proposed" | "narrower" | "split_into_N"
+  }
+```
+Process the verdict:
+- **SAME_PATTERN** → proceed with promotion as-is
+- **MIXED** → ask the user: "Adversary flags event #X as different root cause. Promote rule anyway, narrow scope, or split into multiple rules?"
+- **DIFFERENT** → DO NOT auto-promote. Surface adversary output; require explicit user confirmation.
+Fail-open: if adversary cannot be spawned (missing API key, network), proceed with standard promotion and log a warning. The threshold check + user confirmation still apply.
 ## Files
 | Action | File |

package/.claude/commands/wogi-onboard.md CHANGED Viewed

@@ -1077,3 +1077,29 @@ AskUserQuestion({
   }]
 });
 ```
+## v2.25.0+ — Modern Config Scaffolding (MANDATORY)
+When generating `.workflow/config.json` for a fresh project, include these 2.22+ capability blocks so new users inherit the current-best defaults:
+```json
+{
+  "intentGroundedReasoning": { "enabled": true },
+  "taskBoundaryReset": { "enabled": true, "maxRestartsPerSession": 50 },
+  "storyFlow": {
+    "consumerImpactAnalysis": { "enabled": true, "breakingThreshold": 5 },
+    "scopeConfidenceAudit": { "enabled": true },
+    "itemReconciliation": { "enabled": true, "minItems": 3 }
+  },
+  "longInputGate": { "enabled": true, "lineThreshold": 40 },
+  "researchReasoningGate": {
+    "enabled": true,
+    "tier2": { "enabled": true },
+    "tier3": { "enabled": true, "adversaryModel": "sonnet" }
+  }
+}
+```
+These drive IGR (Architect + Adversary + Truth Gate), task-boundary context reset via the `wogi-claude` wrapper, `/wogi-story` P0 spec gates, auto-routing of long inputs to `/wogi-extract-review`, and the research reasoning gate's assumption-surfacing + cross-model adversary. All have proven out across the 2.22.x release series; new users should not have to discover them one at a time.
+For multi-repo workspaces, also scaffold `workspace.autoPickupChannelDispatches: true` and leave the other `workspace.*` defaults intact — they include the 2.22.2 restart-handoff protocol.

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

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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/.claude/commands/wogi-triage.md CHANGED Viewed

@@ -356,3 +356,44 @@ Each finding is displayed using these fields from `last-review.json`:
 | File | `finding.file` + `finding.line` | "src/api.ts:45" |
 | Issue | `finding.issue` | "Raw JSON.parse without try-catch" |
 | Recommendation | `finding.recommendation` | "Use safeJsonParse from flow-utils.js" |
+## Anti-Deferral Enforcement (v2.25.0+ — MANDATORY)
+The **Review-Findings Anti-Deferral Rule** (`.workflow/state/decisions.md`, 2026-04-15) extends to `/wogi-triage` mechanically in v2.25.0+. Prevents the rubber-stamp pattern where the AI silently drops findings from "fix all" requests.
+**Enforcement rules**:
+1. **"Defer" / "skip" requires explicit user confirmation with a reason.** When the AI or user proposes to defer a finding, the triage flow MUST prompt:
+   ```
+   Defer finding wf-review-XXXX?
+     Severity: HIGH
+     Reason required: [user input]
+     [Confirm defer] [Cancel — fix now]
+   ```
+   Auto-defer without reason is FORBIDDEN.
+2. **"Fix all" / "Option 1" / equivalent means fix ALL.** If the user requests bulk processing:
+   - Ship a fix for every finding with evidence-tier ≥ 1
+   - If any finding is too large, STOP and ask: "Finding X requires ~Y minutes of work. Ship now, split to its own release, or defer (needs reason)?"
+   - Never silently convert a finding to "deferred" in commit messages or release notes
+3. **Commit/release consistency check.** Before finalizing, scan the commit message / release notes against the findings list. If the message claims "fixes F1, F2, F3, M1" but M1 isn't in the diff, BLOCK with:
+   ```
+   Commit message claims M1 is fixed, but M1 does not appear in the diff.
+   Options: [Fix M1 now] [Remove M1 from message] [Acknowledge + proceed]
+   ```
+4. **Triage output includes a Deferral Audit Trail**:
+   ```
+   ━━━ TRIAGE SUMMARY ━━━
+   Fixed: 12
+   Deferred (with reasons): 2
+     • M3 — "requires restructure, tracked as wf-XXXXXXXX" (user-confirmed)
+     • L5 — "out of scope for current release" (user-confirmed)
+   Silently dropped: 0 ← MUST be 0
+   ━━━━━━━━━━━━━━━━━━━━━━
+   ```
+Historical incident (v2.17.4 release, 2026-04-15): commit message claimed "fix all findings" but M1 and M3 were silently dropped. The v2.25.0+ mechanical enforcement makes that failure mode architecturally impossible — the flow stops and asks rather than letting the AI make an autonomous defer decision.
+Skip only if `config.triage.antiDeferralEnforcement.enabled` is explicitly `false` (default: true).

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "wogiflow",
-  "version": "2.23.0",
+  "version": "2.25.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 tests/flow-wave3-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 CHANGED Viewed

@@ -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:');