Description
Baseline failures touched by any slowdown are decorated globally, suppressing their normal error and warning log streams even when the fault is unrelated.
Acceptance Criteria
- #1 An unrelated ambient slowdown does not replace baseline failure decoration or its error and warning logs
- #2 A fault affecting the failed request path still decorates the causal failure with consistent timing
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 Plan
Implement own-path baseline-fault decoration on the immutable composed causal source snapshot; public-boundary red/green must retain unrelated baseline error/warning streams and related-path causal timing. No shared engine/schema or rate change. Candidate waits final foundation repair and composed landing.
Implementation Notes
Owner closeout: Own-path fault decoration held for causal/app composition.
Loop60 closeout: Own-path decoration candidate14934446 has actual red/green and native acceptance, but is unlanded with the causal foundation. Resume task-only delta on current-main composition after evaluator resolution; preserve all baseline warning/error and related-path timing assertions.
Final loop closeout: retained unlanded causal candidateaf34 has native/component review and final CodeRabbit passes, but the exact integrated full gate fails app-race600.139s. No candidate source was pushed or deployed. Preserve task-specific earlier evidence/limits; resume only after the aggregate owner stop and relevant dependency/owner decisions are resolved, with no timeout/assertion/case/isolation reduction or unchanged full-gate retry.