dan-claude-bot cbc8f4f7a8 test(labels): pin the reverse direction — a run that finished after an in-flight entry settles the context ... The supersede fixtures pinned "an in-flight re-run is the newer word". Nothing pinned the converse: a run that FINISHED after an earlier in-flight entry is also the newer word, so the context is settled and reads SUCCESS rather than staying PENDING. That is the assertion that catches an over-correction — widening "an undateable entry sorts last" into "an in-flight entry always wins". Verified it fails under exactly that mutation and that nothing else in the suite does. Also corrects the comment above the undateable fixture: that case is guarded by the sort tiebreak, not by the dating expression, so the two changes are now separately pinned. Reverting only the dating expression fails 2 fixtures (the two zero-sentinel ones), not 3. 48 -> 49. Reconciler unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-07-20 16:29:59 +00:00
..
cli.sh	fix: run setup-host over a migrated flat tree, and name what the migration left	2026-07-20 14:18:21 +00:00
labels-reconcile.sh	test(labels): pin the reverse direction — a run that finished after an in-flight entry settles the context	2026-07-20 16:29:59 +00:00
release.sh	fix: the guard also refuses a DUPLICATED release heading, not just a deleted one	2026-07-20 14:08:56 +00:00