feat(pipeline): SDLC pipeline primitive — engine, store, registries (dark)

[saucam]

What

First slice of the SDLC pipeline (docs/sdlc-pipeline.md): the generic, methodology-agnostic pipeline primitive. Lands dark — no daemon wiring, no methodology content, no behavior change until a manager is instantiated (PR #2).

New package src/daemon/pipeline/:

File	Role
interface.ts	PhaseDef / PipelineState / PhaseState + the four plugin seams — PhaseKind, GatePlugin (at: entry|exit), SkillPlugin, Pack — plus the §5a fields (tools, reads/writes, entryGate, per-phase provider/model)
registry.ts	MapRegistry (register/unregister/resolve/list/has, last-wins-with-warn) + createRegistries()
builtin.ts	content-free built-ins: a noop phase kind + always / manual gates
engine.ts	pure advance logic — step/run, entry+exit gates, onFail halt/retry/abort, terminal/halted guards
store.ts	durable pipelines table on bun:sqlite, mirroring Store conventions; listActive() drives restart rehydration
manager.ts	PipelineManager — create/get/list/advance/abort + resume() (rehydrate non-terminal pipelines)

Why this shape

Follows the design's three-layer split: a generic pipeline primitive (this PR) → blocker-approval + audit (reuses existing seams) → swappable capability packs. The primitive is pure data + a side-effect-free engine, so the transition rules are unit-testable and the whole thing is off by default.

Verification

• bun test src/daemon/pipeline — 26 pass / 0 fail
• tsc --noEmit — clean
• biome check — clean
• Restart survival is covered end-to-end: a manual-gated pipeline halts, and a brand-new PipelineManager over the same store comes back halted at the same phase (the concrete win over ADLC's pipeline-state.json).

Not in this PR (next slices)

• PR Tui/cockpit support #2 — config PipelineSchema (off by default) + daemon-boot wiring + resumePipelines() on boot + the first backend-driven PhaseKind.
• PR feat: codeoid web UI (Solid + Vite + Tailwind 4) — chat cockpit + file viewer #3 — the §10 thin slice: a gate that halts → ui_request → answer from Web/Telegram → resume, with additive protocol fields.

Also includes the design-doc enrichment (external prior-art §2a, refinements §5a, open Q3/Q4/Q6 resolved, default flipped to off/freestyle).

🤖 Generated with Claude Code

[codecov]

Codecov Report

❌ Patch coverage is 98.50746% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 87.66%. Comparing base (98133d8) to head (ab8bf98).
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/daemon/pipeline/manager.ts	93.33%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #204      +/-   ##
==========================================
+ Coverage   87.52%   87.66%   +0.13%     
==========================================
  Files         118      124       +6     
  Lines       21122    21390     +268     
==========================================
+ Hits        18488    18752     +264     
- Misses       2634     2638       +4     

Flag	Coverage Δ
daemon	87.66% <98.50%> (+0.13%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/daemon/pipeline/builtin.ts	100.00% <100.00%> (ø)
src/daemon/pipeline/engine.ts	100.00% <100.00%> (ø)
src/daemon/pipeline/interface.ts	100.00% <100.00%> (ø)
src/daemon/pipeline/registry.ts	100.00% <100.00%> (ø)
src/daemon/pipeline/store.ts	100.00% <100.00%> (ø)
src/daemon/pipeline/manager.ts	93.33% <93.33%> (ø)

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

🤖 Gemini code review

This PR implements a generic, methodology-agnostic SDLC pipeline primitive including the engine, store, in-memory registries, and a manager. The architecture is solid and clean, but there are reliability issues around unhandled plugin exceptions causing crash loops, and a performance bottleneck in the SQLite store where active pipelines are loaded via a full table scan rather than utilizing the status index.

Findings: 🔴 0 · 🟠 3 · 🟡 0 · 🟢 0

---

_{Tokens spent · ⬆️ Input: 16,955 · ⬇️ Output: 688 · Σ Total: 24,699
Total may be higher due to thinking token counts.}

[saucam]

Addressed all three Gemini findings in ab8bf98:

• store.ts listActive() — now filters in SQL (WHERE status NOT IN (…)) instead of scanning every row into JS; the placeholders are derived from TERMINAL_STATUSES so the terminal set stays single-sourced (no drift with isTerminal()).
• engine.ts — PhaseKind.run() and GatePlugin.evaluate() are now wrapped; a throwing plugin becomes a phase failure (handled by onFail) rather than crashing the run and leaving the pipeline stuck running (the restart crash-loop you flagged). Added tests for both paths.

Fixes propagate up the stack to #205 / #206 via rebase.