solidjs / solid / 34190687063

72%

main: 89%

push

github

feat(attribution): LONG_HOLD, stricter hold thresholds, phase "held"

- SILENT_HOLD defaults tighten to holds { infoMs: 100, warnMs: 200 } (RAIL
  instant ceiling / INP good ceiling). The engine measures to the commit, not
  the paint, so every number is a floor on what the user saw.
- LONG_HOLD (responsiveness): an acknowledged hold whose quiescent tail —
  last write to join → commit — reached longHolds.infoMs (500) / warnMs
  (1000). Measured from the last join so typing is judged per wait. Repair
  is a fallback: Loading keyed with `on` (a revealed boundary without `on`
  keeps the old content — that IS the hold), a fresh boundary, or faster
  data. A silent long hold stays one SILENT_HOLD with the repair appended.
- HoldEvent.tailMs; ChangeRecord.at on root writes; holdMs runs from the
  earlier of interaction dispatch and first parked flush (a node rewritten
  mid-hold keeps only its latest record).
- feedback().sources late/lateMs → long/longMs (tail past threshold,
  acknowledged or not).
- RerunEvent.phase "transition" → "held".
- paintedDuringHold documented for what it is: only lane effects run in a
  parked flush; an unrelated effect cannot clear the verdict.
- @solidjs/diagnostics artifact format 3; hold evidence carries tailMs.
- Skill, agent-loops skill, RFC 08 updated; "transition" wording removed
  from the diagnostic surfaces.

Co-authored-by: Claude via Cursor <noreply@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

516 of 784 branches covered (65.82%)

Branch coverage included in aggregate %.

768 of 1002 relevant lines covered (76.65%)

14.98 hits per line