Description
An error_spike can mark a downstream hop Failed while the request outcome stays success (pre-existing; raised by CodeRabbit on SKT-0168.09.09). Make the request outcome reflect hop failures without changing default output for blueprints without incidents, or document why a hop failure may be retried/absorbed.
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/
Implementation Notes
loop57 closeout: parked/open, see codex/closeout-2026-10-24-loop57.md.
loop58: folded into SKT-0168.09.15 lane l4a (design v2 §9): causal workloads propagate or absorb hop failures; legacy unchanged and documented.