valent-pipeline 0.6.0 → 0.6.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "valent-pipeline",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "v3 multi-agent AI pipeline for software development lifecycle",
   "type": "module",
   "bin": {

package/pipeline/docs/cost-and-resumability-improvements.md

@@ -0,0 +1,313 @@
+# Workflow Improvement Plan — Cost & Resumability
+
+> **Status:** Proposal / design doc
+> **Scope:** `valent-pipeline` orchestrators (`plan` / `sprint` / `retro`), gate model assignment, and the path to a multi-provider runner.
+> **Author's thesis (yours, and it's correct):** *Because the pipeline is gated, cheap models can do far more of the work.* The gates are the quality backstop, so the expensive model only needs to show up where **judgment** happens — not where **finding** or **building** happens. Everything below is an elaboration of that one idea, plus a resumability layer so a 2–4M-token sprint never has to start over.
+
+---
+
+## 1. The two problems, stated precisely
+
+| # | Problem | Root cause in the current design |
+|---|---------|----------------------------------|
+| 1 | **Resumability** after a network glitch or context exhaustion | Resume relies on the Workflow journal + `resumeFromRunId`, which is **same-session only** and **in-memory**. If the session itself dies (context exhaustion → new session) or the host process is killed, the journal/runId is gone and there is no durable, cross-session ledger of "which stories already shipped." A single transient agent failure inside a sequential gate **throws and kills the whole run** rather than retrying. |
+| 2 | **Cost** — ~1M tokens per planning run, 2–4M per sprint | Opus is the default for **every gate** (`READINESS`, `CRITIC`, `JUDGE`, `INTEGRATION`), and the most expensive gate — `CRITIC` — runs **3 full Opus passes + an Opus triage**, and **re-runs all of that** on every rejection cycle (up to `maxRejectionCycles`, default 5). The rejection loop tail is the single largest cost center. Nothing deterministic (linters, type-checkers, static analysis) runs *before* Opus, so Opus pays tokens to find mechanical issues a free tool would catch. |
+
+These interact: a robust **idempotent checkpoint** layer (Problem 1) *also* saves cost, because a resumed sprint skips already-shipped stories instead of re-billing them.
+
+---
+
+## 2. Cost anatomy — where the tokens actually go
+
+**Current model assignment** (`sprint.workflow.js:224-230`):
+
+```js
+const DEFAULT_MODELS = {
+  READINESS: 'opus', CRITIC: 'opus', JUDGE: 'opus', INTEGRATION: 'opus',   // ← gates: all Opus
+  REQS: 'sonnet', UXA: 'sonnet', 'QA-A': 'sonnet', 'QA-B': 'sonnet',
+  BEND: 'sonnet', FEND: 'sonnet', DATA: 'sonnet', 'MCP-DEV': 'sonnet',
+  LIBDEV: 'sonnet', DOCGEN: 'sonnet', IAC: 'sonnet', MOBILE: 'sonnet',
+  RESOLVE: 'haiku',
+}
+```
+
+**Current API prices (2026):**
+
+| Model | Input $/M | Output $/M | Cached input $/M (≈90% off) | Batch (−50%) |
+|-------|----------:|-----------:|----------------------------:|-------------:|
+| Opus 4.8   | $5  | $25 | ~$0.50 | $2.50 / $12.50 |
+| Sonnet 4.6 | $3  | $15 | ~$0.30 | $1.50 / $7.50 |
+| Haiku 4.5  | $1  | $5  | ~$0.10 | $0.50 / $2.50 |
+
+**Per-story Opus cost, directional, *zero rework*** (input largely uncached on first pass):
+
+| Gate | Opus calls | Rough $ / story |
+|------|-----------:|----------------:|
+| READINESS (1 pass) | 1 | ~$0.28 |
+| **CRITIC (3 passes + triage)** | **4** | **~$1.25** |
+| JUDGE (1 pass) | 1 | ~$0.33 |
+| **Total Opus (no rework)** | **6** | **~$1.86** |
+
+Now add the loop. **Each CRITIC rejection cycle re-runs all 3 passes + triage** (`runCriticGate`, `sprint.workflow.js:519-566`). Two cycles ≈ **+$2.50**, and CRITIC alone becomes ~70% of the story's Opus spend. **The rejection-loop tail is the thing to attack first.**
+
+> **Takeaway:** Of the 6 Opus calls per clean story, only **3 are genuine judgment calls** (the READINESS decision, the CRITIC *triage*, the JUDGE *ship decision*). The other 3 (the CRITIC *hunting* passes) are *finding* work that a cheaper model — or a free deterministic tool — can do most of. That gap is the savings.
+
+---
+
+## 3. Cost levers, highest ROI first
+
+### Lever 1 — Deterministic pre-gates (free, non-LLM) before any Opus runs
+
+Run linters, type-checkers, and static analysis as a **blocking gate between Build and CRITIC**. Dev agents must produce a clean lint/type/compile/test-build before a single Opus token is spent reviewing.
+
+| Tool | Cost | Catches (deterministically) |
+|------|------|------------------------------|
+| **Semgrep** | Free ≤10 contributors (OSS engine free) | Injection, secrets, taint flows, unsafe APIs, ~security rules |
+| **ESLint / tsc** | Free | Type errors, null/undefined, unused, unreachable, many real bugs |
+| **Ruff / Bandit** (Python) | Free | Lint + Python security |
+| Compiler / `tsc --noEmit` | Free | Whole class of "doesn't even type-check" rejections |
+
+**Why this is #1:** It directly shrinks the **rejection-loop tail** — the most expensive thing in the system. Every mechanical defect a linter catches is a CRITIC rejection cycle (3 Opus passes + triage) that *never happens*. It also lets CRITIC's prompt explicitly say *"lint/types/security-static already passed; focus only on semantic correctness and AC coverage,"* which shrinks each remaining Opus pass.
+
+**Where:** new `pre-critic-gate` step invoked in `runStory` between the Build barrier and `runCriticGate` (`sprint.workflow.js`, around the Build→Critic transition). The dev agents already run tests; add the static suite to their `handoff` step and make CRITIC refuse to start until the pre-gate verdict is green.
+
+### Lever 2 — Split *find* from *judge*; make Opus the exception-handler, not the default
+
+Re-tier `CRITIC` so the **hunting** passes run cheap and only **judgment** runs on Opus:
+
+```yaml
+# pipeline-config.yaml (proposed `models` override — already supported by buildModelMap)
+models:
+  haiku:  [RESOLVE, CRITIC_BLIND]        # blind-hunt is mechanical: naming, dead code, copy-paste
+  sonnet: [REQS, UXA, QA-A, QA-B, BEND, FEND, ...,
+           CRITIC_EDGE, CRITIC_ACCEPT,   # edge-case + acceptance-audit on Sonnet
+           JUDGE_EVIDENCE]               # evidence cross-referencing is mechanical counting
+  opus:   [CRITIC_TRIAGE,                # adjudication = judgment → keep Opus
+           JUDGE_DECIDE, READINESS]      # the actual ship/ready decisions
+```
+
+This requires splitting the monolithic `CRITIC` and `JUDGE` roles into sub-roles the model map can target (the 3-pass structure already exists as separate agents at `sprint.workflow.js:519-566` — give each pass its own role key). The triage step stays Opus because that's where duplicates collapse and severity is decided — the genuine judgment.
+
+**Escalation rule (the gate-thesis, made literal):** run the cheap pass; **escalate a finding to Opus only when** the cheap model marks it High-severity *or* flags low confidence. A clean diff that passes lint + Sonnet review + full AC coverage may need **zero Opus** — Opus becomes an adjudicator invoked on exceptions, not the default reviewer. Projected CRITIC cut: **~40–60%** with no loss of the Opus backstop on actual decisions.
+
+Apply the same split to `JUDGE`: Sonnet does the *evidence cross-reference* (does the test count match the spec, is every AC traced — mechanical counting), Opus makes only the final SHIP/REJECT call, and only when evidence is ambiguous.
+
+### Lever 3 — Targeted re-review on rejection (kill the loop tail)
+
+Today a rejection re-runs **all 3 CRITIC passes + triage** (`runCriticGate`). Instead: **persist the open findings**, and on rework, run a **verify-only pass** that checks *just the previously-failed findings* against the new diff. Full re-hunt only if the dev's fix touched files outside the flagged set.
+
+- Re-review cost drops from ~100% of a full CRITIC to ~20%.
+- Combined with Lever 1 (fewer rejections to begin with) this collapses the cost tail.
+- Lower `maxRejectionCycles` from 5 → 2–3 and **escalate to a human/Opus-once** instead of looping a 4th time; the 4th–5th cycles are almost never productive and are pure Opus burn.
+
+### Lever 4 — Offload review to flat-rate / free external reviewers
+
+Use an external reviewer as the **blind-hunt pass** (or a pre-CRITIC filter), so that pass costs a flat fee or $0 instead of Opus tokens:
+
+| Tool | Pricing | Local/CLI | Needs your LLM key? | Catches |
+|------|---------|-----------|---------------------|---------|
+| **CodeRabbit CLI** | **$0.25 / file** reviewed (credit add-on); SaaS Pro $24/dev/mo, Pro+ $48 | CLI client → their cloud (needs API key, not offline) | No — flat per-file | Race conditions, memory leaks, security vulns, actionable fixes |
+| **Qodo Merge** (ex-PR-Agent) | **Free tier 250 credits/mo**; Teams $30/user/mo (2500 credits). PR-Agent OSS is **self-hostable, BYO key** | Yes — IDE/local review + self-host/air-gapped | OSS path: yes (your key) | PR review, context-aware; Opus=5 credits/req, Grok-4=4 credits/req on managed tier |
+| **Greptile** | $30/seat/mo, 50 reviews incl., then $1/review | Cloud; enterprise self-host | Managed | Codebase-context review |
+| **Sourcery** | Free for OSS; Team $24/seat/mo (**BYO LLM** on Team) | Yes — CLI | Team tier: yes (your key) | **Rule-based refactoring** (deterministic) + AI review |
+| **Native Claude Code `/code-review`** | In-session tokens only | Yes — runs on the local diff | Uses your Claude session | Correctness bugs + reuse/simplification at chosen effort |
+
+**Recommendation:** CodeRabbit CLI ($0.25/file, predictable) or self-hosted **PR-Agent** (free, your key) as the **blind-hunt replacement**. They run on the diff, return structured findings, and slot straight into the existing `verdict.schema.json` gate machinery — the orchestrator doesn't care who produced the verdict as long as it matches the schema. The native `/code-review` skill is the zero-integration option for a first experiment.
+
+### Lever 5 — Multi-provider CLI arbitrage (Codex / Cursor / Grok) — *subsidized usage across providers*
+
+This is the big structural play, and it's feasible **because Workflow `agent()` subagents have Bash**. An agent can shell out to another vendor's headless CLI, wait, and parse the result back into the handoff schema. The orchestrator stays pure (all IO happens *inside* the agent, which is journal-replay-safe); the subagent becomes a thin **"shell driver."**
+
+**Subsidized runners to target:**
+- `codex exec "<prompt>"` — OpenAI **Codex CLI**, non-interactive/headless, billable against a **ChatGPT Plus/Pro/Team subscription** (flat-rate, not per-token API).
+- `cursor-agent` — **Cursor CLI** headless, subsidized by a Cursor subscription.
+- **Grok CLI** — xAI, subsidized by an X/Grok subscription.
+
+**The arbitrage:** route the cheap-but-bulky work (dev/build passes, blind-hunt, test scaffolding, doc lookups) to whichever flat-rate subscription you're *already paying for*, so those tokens are **$0 marginal**. Keep Claude **Opus only on the irreducible judgment gates**. If Codex/Cursor does the *building* on a flat subscription, the entire Sonnet dev line can leave the per-token API bill.
+
+**Architecture — generalize `modelFor(role)` into `runnerFor(role)`:**
+
+```yaml
+# pipeline-config.yaml (proposed)
+runners:
+  codex:   { cmd: "codex exec",       auth: subscription }   # flat-rate
+  cursor:  { cmd: "cursor-agent",     auth: subscription }
+  grok:    { cmd: "grok",             auth: subscription }
+  claude:  { cmd: native }                                   # in-session subagent
+roles:
+  BEND:          { runner: codex,  fallback: claude:sonnet }  # build on flat-rate sub
+  CRITIC_BLIND:  { runner: cursor, fallback: claude:haiku }   # blind hunt on flat-rate sub
+  CRITIC_TRIAGE: { runner: claude, model: opus }              # judgment stays Opus
+  JUDGE_DECIDE:  { runner: claude, model: opus }
+```
+
+The handoff/verdict schemas (`schemas/handoff.schema.json`, `schemas/verdict.schema.json`) are the **normalization layer** — a Codex-produced review and an Opus-produced review are interchangeable to the gate logic as long as both emit the schema. Long external runs use `run_in_background: true` + `Monitor`.
+
+**Guardrails (this is exactly your gate-thesis):** quality variance across providers is *fine* precisely because the Opus gate is the backstop. A cheaper/subsidized provider that produces weaker work just gets caught and rejected by CRITIC/JUDGE — you trade a little more rework risk for near-zero marginal token cost on the bulk. Keep a `fallback` so a missing/failing CLI degrades to a native Claude agent rather than killing the run.
+
+### Lever 6 — Ref MCP to cut rework *and* context bloat
+
+Wire **Ref MCP** (`ref_search_documentation`, `ref_read_url`) into the dev agents (BEND/FEND/DATA/…) and CRITIC. Two distinct savings:
+
+1. **Fewer rejection cycles.** A large share of CRITIC/JUDGE rejections are wrong API usage / hallucinated signatures. Ref lets the dev agent verify the real API *before* writing code, so the diff is right the first time → fewer (expensive, Opus) rework loops. This attacks the same cost tail as Lever 1, from the front.
+2. **Smaller context.** Without Ref, agents either guess or paste entire doc pages into context. Ref returns **only the relevant snippet**, so you pay for the 500 tokens you need, not the 40K-token page. CRITIC can use Ref to confirm "is this really the right call signature?" instead of being handed the whole SDK.
+
+**Where:** add a "verify external APIs via Ref before implementing" step to each dev `read-inputs`/`implement` step file, and a "confirm uncertain API usage via Ref" note to `critic/edge-case-hunt.md`.
+
+### Lever 7 — Cache hygiene, distilled handoffs, batch API
+
+- **Prompt-cache hygiene.** Caching is already in use, but cache hits require the static prefix to be **byte-identical** across spawns. Audit `buildPrompt` (`sprint.workflow.js:273-298`) so the **static** content (role prompt path, pipeline-context, handoff contract) comes first and the **dynamic** content (storyId, task subject, trigger) comes last. Verify realized cache-hit rate with the existing `audit` command (`src/commands/audit.js`) / `valent-review-cost` skill. Cached input is ~90% cheaper — a few percent of hit-rate is real money on a 4M-token sprint.
+- **Distilled handoffs.** `distilled-handoff-format.md` already exists; make sure CRITIC/JUDGE read **distilled** artifacts, not raw full files, wherever the decision doesn't need the raw text.
+- **Batch API (−50%)** for the latency-insensitive, non-interactive work: estimation/sizing in `plan`, retrospective synthesis, KB embeddings. These don't block a human, so the 50% batch discount is free money.
+
+---
+
+## 4. Projected impact
+
+Directional, stacking the levers (no loss of the Opus decision-backstop):
+
+| Lever | Mechanism | Est. cost reduction |
+|-------|-----------|---------------------|
+| 1 — Deterministic pre-gates | Removes ~30–50% of CRITIC rejection cycles | **High** |
+| 2 — Find vs. judge tiering | 2 of 3 CRITIC passes → Sonnet/Haiku; JUDGE evidence → Sonnet | ~40–60% of CRITIC |
+| 3 — Targeted re-review | Re-review ~20% of a full pass instead of 100% | High on rework tail |
+| 4 — External reviewer | Blind-hunt → $0.25/file or free, off the Opus bill | Moderate |
+| 5 — Provider arbitrage | Dev/blind work → subsidized flat-rate subs ($0 marginal) | **High** (can move the entire Sonnet dev line off API) |
+| 6 — Ref MCP | Fewer rework loops + smaller context | Moderate, compounding |
+| 7 — Cache/distill/batch | ~90% off cached input, 50% off batch | Moderate, broad |
+
+**Realistic combined target: 50–70% reduction** in per-sprint API spend, with the irreducible Opus judgment (CRITIC triage, JUDGE ship decision, READINESS) preserved as the quality floor.
+
+---
+
+## 5. Resumability redesign
+
+### Current state and the gap
+
+Resume = relaunch `Workflow({ scriptPath, resumeFromRunId })`; the journal replays the unchanged `agent()` prefix at ~100% cache hit. This is elegant **but**:
+- **Same-session only / in-memory.** Context exhaustion that forces a new session, or a killed host process, loses the journal and the runId.
+- **No durable ledger.** Nothing on disk says "story KANBAN-014 already SHIPPED in this sprint," so a from-scratch restart re-bills shipped stories.
+- **A transient failure is fatal to sequential gates.** In a `for`-loop story (`sprint.workflow.js:312-315`), a network blip inside an awaited gate `throw`s and ends the run (unlike `parallel`, which drops to `null`).
+
+### Fix A — Idempotent, on-disk phase checkpoints (cross-session resume)
+
+Persist a durable run ledger in the existing SQLite DB (extends the `artifacts`/`calibration` tables in `src/lib/db.js`). Add a CLI command:
+
+```
+node .valent-pipeline/bin/cli.js checkpoint --sprint <id> --story <id> --phase <spec|build|critic|qa|judge> --verdict <pass|ship|reject>
+```
+
+An `agent()` at the end of each phase writes the checkpoint (IO inside an agent = journal-safe). Then **make each phase idempotent at the top of `runStory`**: before running a phase, query the ledger; if a terminal verdict already exists for `(sprint, story, phase)`, **skip and reuse the on-disk artifact**. This is exactly the `groomed`-bypass pattern (`sprint.workflow.js` skips Spec+Readiness when `groomed:true`) — generalized to every phase. Result: a fresh run **after total session loss** naturally fast-forwards to the first incomplete phase, with no journal required.
+
+### Fix B — Retry-with-backoff wrapper for transient failures
+
+Wrap every gate/agent call in a bounded retry so a network glitch doesn't kill a 4M-token run:
+
+```js
+async function withRetry(fn, { tries = 3, label } = {}) {
+  let lastErr
+  for (let i = 0; i < tries; i++) {
+    try { return await fn() }
+    catch (e) { lastErr = e; log(`retry ${label} (${i + 1}/${tries}): ${e.message}`) }
+  }
+  // exhausted: checkpoint progress and surface the runId so the user can resume cross-session
+  log(`PAUSED at ${label}. Resume with resumeFromRunId, or restart — completed phases will be skipped via the ledger.`)
+  throw lastErr
+}
+```
+
+(Keep it deterministic — no `Date.now`/`Math.random` in the script body; the resume-safety linter at `scripts/test-workflow.js` enforces this.)
+
+### Fix C — Make the runId loud and durable
+
+On every story boundary, `log()` the `runId` and write it into the SQLite ledger so it survives the session. The resume instruction becomes a one-liner the user can always recover, and even if the runId is lost, **Fix A** makes a cold restart safe.
+
+**Net:** three independent safety nets — journal replay (fast path, same session), the idempotent ledger (cross-session/cold-start), and bounded retry (transient blips) — so no single failure mode forces a 2–4M-token redo.
+
+---
+
+## 6. Proposed `pipeline-config.yaml` surface (consolidated)
+
+```yaml
+runtime:
+  provider: claude-code
+
+# Lever 2 — find vs. judge tiering (CRITIC/JUDGE split into sub-roles)
+models:
+  haiku:  [RESOLVE, CRITIC_BLIND]
+  sonnet: [REQS, UXA, QA-A, QA-B, BEND, FEND, DATA, IAC, MCP-DEV, LIBDEV, DOCGEN, MOBILE,
+           CRITIC_EDGE, CRITIC_ACCEPT, JUDGE_EVIDENCE]
+  opus:   [READINESS, CRITIC_TRIAGE, JUDGE_DECIDE, INTEGRATION]
+
+# Lever 5 — multi-provider runners (subsidized arbitrage)
+runners:
+  codex:  { cmd: "codex exec",   auth: subscription }
+  cursor: { cmd: "cursor-agent", auth: subscription }
+  grok:   { cmd: "grok",         auth: subscription }
+roles:
+  BEND:          { runner: codex,  fallback: claude:sonnet }
+  CRITIC_BLIND:  { runner: cursor, fallback: claude:haiku }
+  CRITIC_TRIAGE: { runner: claude, model: opus }
+  JUDGE_DECIDE:  { runner: claude, model: opus }
+
+# Lever 1 — deterministic pre-gate (blocks CRITIC until green)
+pre_critic_gate:
+  blocking: true
+  commands: ["npm run lint", "npm run typecheck", "semgrep --config auto --error"]
+
+# Lever 4 — external reviewer as blind-hunt
+external_review:
+  blind_hunt: coderabbit          # coderabbit | pr-agent | native | claude
+
+# Lever 3 — bounded, targeted rework
+rejection:
+  max_cycles: 2                   # was 5
+  targeted_reverify: true         # re-check only previously-failed findings
+
+# Lever 6 — Ref MCP for dev + critic
+ref_mcp: { enabled: true, roles: [BEND, FEND, DATA, CRITIC_EDGE] }
+
+# Resumability
+resume:
+  ledger: sqlite                  # durable cross-session phase checkpoints
+  retry: { tries: 3 }
+```
+
+All of this is overlay-on-default and journal-replay-safe (static + args only), consistent with `buildModelMap` (`sprint.workflow.js:231-241`).
+
+---
+
+## 7. Phased rollout
+
+| Phase | Change | Effort | Risk | Payoff |
+|-------|--------|--------|------|--------|
+| **0** | Turn on **prompt-cache hygiene** + verify hit-rate via `audit`; add **retry wrapper**; **lower `max_cycles` to 3** | S | Low | Quick cost + stability win |
+| **1** | **Deterministic pre-critic gate** (lint/types/semgrep) | S–M | Low | Biggest single cost cut (kills rework cycles) |
+| **2** | **Idempotent SQLite checkpoint ledger** (cross-session resume) | M | Low | Fixes Problem 1 fully |
+| **3** | **Split CRITIC/JUDGE** into sub-roles + **find-vs-judge tiering** | M | Med (validate quality holds) | ~40–60% CRITIC cut |
+| **4** | **Targeted re-verify** on rejection | M | Med | Collapses the cost tail |
+| **5** | **External reviewer** (CodeRabbit CLI or self-hosted PR-Agent) as blind-hunt | M | Low | Moves a pass off the Opus bill |
+| **6** | **Ref MCP** wired into dev + critic | S | Low | Fewer reworks, smaller context |
+| **7** | **`runnerFor()` provider abstraction** → Codex/Cursor/Grok arbitrage | L | Med–High | Largest structural saving; multi-harness future |
+
+Phases 0–2 are low-risk and address both problems immediately. Phase 7 is the strategic bet that unlocks the "many subsidized providers" future you described — and it's safe to attempt *because the gates already protect quality*, which is the whole premise.
+
+---
+
+## 8. Risks & guardrails
+
+- **Quality regression from cheaper/foreign models.** Mitigated by design: the Opus judgment gates are the floor. Track rejection-rate and rework-cycle counts per tier in the existing `calibrate` data — if a Sonnet/Codex pass drives rework up, the savings evaporate and you escalate that role back up. Make the tiering **measured, not assumed.**
+- **Determinism / journal safety.** All external-CLI and DB calls must stay **inside agents**; the orchestrator script stays pure (no `Date.now`/`Math.random`/IO) so resume replay holds. The linter at `scripts/test-workflow.js` already enforces this — keep it green.
+- **External-tool auth in headless/cron runs.** Codex/Cursor/Grok CLIs and CodeRabbit need their own auth; subscription-based CLIs may not be present in unattended runs. Always define a **`fallback` to a native Claude agent** so a missing CLI degrades instead of failing.
+- **Cost monitoring must lead.** Before/after every phase, run `valent-review-cost` / `audit` on the Workflow journals so each lever's real savings is measured, not guessed.
+
+---
+
+## 9. TL;DR
+
+1. **Stop paying Opus to find mechanical bugs.** Put free linters/Semgrep/Ref in front of CRITIC, and move CRITIC's *hunting* passes to Sonnet/Haiku (or a flat-rate external reviewer / subsidized CLI). Keep Opus only for the *triage* and *ship* decisions.
+2. **Kill the rejection-loop tail** — targeted re-verify + lower cap. It's the #1 cost center.
+3. **Arbitrage subsidized providers** (Codex/Cursor/Grok via headless CLI) for the bulk build/find work; the Opus gate makes the quality variance safe. This is also the on-ramp to the multi-harness future.
+4. **Make resume durable** with an idempotent SQLite phase ledger + retry wrapper, so a glitch or context wipe never re-bills a 2–4M-token sprint.
+
+Combined target: **50–70% lower spend** and **no full restarts**, with the quality backstop untouched.

package/pipeline/orchestrators/claude-code/plan.workflow.js

@@ -392,11 +392,14 @@ if (!validation.valid) {
 // before its dependent) and sprint.workflow.js runs the batch SEQUENTIALLY in array order on a
 // shared branch — so a dependent must not precede its prerequisite. This is what lets a dependency
 // chain ship together in one sprint.
+// `groomed: true` — these stories were fully specced + passed the READINESS gate during grooming
+// above, and their reqs-brief/uxa-spec/qa-test-spec are on disk. sprint.workflow.js reads this flag
+// and SKIPS its Spec + Readiness phases, so execution doesn't redundantly re-spec and re-gate.
 const sizedById = new Map(sizedStories.map((s) => [s.storyId, s]))
 const plannedStories = pack.sprint_stories
   .map((id) => sizedById.get(id))
   .filter(Boolean)
-  .map((s) => ({ storyId: s.storyId, projectType: s.projectType, profiles: s.profiles }))
+  .map((s) => ({ storyId: s.storyId, projectType: s.projectType, profiles: s.profiles, groomed: true }))
 
 return {
   sprintId,