fix: make pipeline runs self-diagnosing

[murdore]

Two fixes for signals that went silent, both surfaced while investigating why recent content appeared to be missing from the corpus. The corpus itself turned out to be healthy — these are the instruments that failed to show it.

totalItemsProcessed was structurally always 0

recordProcessed / recordSkipped / recordErrored existed in src/utils/metrics.ts but had zero call sites anywhere in the codebase. Every run reported the same totalItemsProcessed: 0 whether it collected 62 items or nothing — which is how the 2026-08-13 harvest failure stayed hidden behind 21/21 steps succeeded.

• PipelineStep.run may now return StepCounts; runSingleStep records whatever comes back
• Wired the two steps whose counts the runner already holds (collection, acquisition)
• Counts reported outside a step are dropped rather than attributed to the next one
• save() split into a pure build() plus the write, so tests can read a run's totals without clobbering the videos/pipeline-metrics.json the scheduled run owns

Verified end-to-end with START_STEP=0 END_STEP=1 (no network, no model calls): 0 → 62.

The other 19 agents still return Promise<void> and report nothing. Collection and acquisition are the two that decide whether new content actually arrived, so they carry the signal that matters.

Piggyback lost a day's harvest to a 15s wait with no diagnostics

On 2026-08-13 all three retries failed identically on Chrome DevTools port 9455 did not open within 15000ms. Three identical failures point at Chrome never starting rather than starting slowly — and stdio: "ignore" meant there was no evidence either way.

• Wait raised 15s → 45s, exposed as IG_PIGGYBACK_PORT_TIMEOUT_MS, matching how every other piggyback knob is tuned, documented in .env.example
• Chrome's stderr is piped and its tail attached to the failure, so a locked profile names itself
• The wait aborts as soon as Chrome exits or is signalled, instead of blaming the port after the full timeout

Notes

Both void-in-union lint suppressions are load-bearing and carry their reason inline: the 19 wired agents are all Promise<void>, and void is not assignable to undefined — verified by compiling the alternative.

Testing

• npm test — 488 tests across 57 files pass
• npx tsc --noEmit clean; no new lint findings vs main
• 12 new tests: 7 covering count aggregation and attribution, 5 covering the port wait including fail-fast on exit and on signal

[github-actions]

Single Commit Policy — COMPLIANT

Status: 1 commit | Valid format | No merge commits | Ready for merge

Commit details

• Hash: deea284c5eee293f71a7f5149ec12f3a82150bad
• Message: fix(pipeline): stop runs from reporting success while doing a fraction of the work
• Author: Sachin Sharma

---

Automated validation — dopamine single-commit enforcement