Description
The parked landing review identified a stale timing test comment, a root exemption that may cover unrelated parentless spans, and a public blueprint comment containing operational loop identifiers.
Acceptance Criteria
- #1 The span nesting check exempts only intended roots, not arbitrary parentless spans
- #2 Stale causal timing comments and public operational loop identifiers are removed or corrected without weakening checks
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
Apply the accepted engine-only restored baseline; locate the stale timing comment and parentless-span exemption from retained review, tighten intended-root recognition without weakening nesting checks, and remove the public operational comment only as a separate hunk for the held migration.
Implementation Notes
Owner closeout: Accepted strict intended-root test candidate unlanded. Resume causal stack without loosening bounds; archived reference-blueprint comment remains separate.
Loop60 closeout: Accepted task-separated candidate is retained in the repaired fe995479 causal stack, not published. Composed app race still exceeds the unchanged600-second budget, including after exact optimization foundation; plain/component success is not full-gate acceptance. Resume after owner-authorized evaluator resolution, current-main composition, final generation/review/full gate and actual inventory proof. No timeout/assertion/population weakening or unchanged green sampling.
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.