You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(scripts): tighten the parked digest's route-record docs and tests #5000
Follow-up from #4998, which added the STRANDED verdict to blocked-label-blocker-line.sh --parked-digest. The final local review at 9f982b7 found no P0/P1, but it left four nits. They were deferred so the PR could merge at a reviewed head:
Guide wording (.claude/guides/merge-policy.md, the STRANDED bullet): say that any use of re-check as a word inside a tried: or next: value voids the route record, with or without a date. Today next: re-check upstream is NO-ROUTE too, and the current wording only mentions dates.
Direct unit test for recheckWords (.claude/scripts/blocked-label-blocker-line-go/stranded_test.go): assert recheckWords("re-check re-check") == 2. The "two uses side by side" row would still give NO-ROUTE with a count that swallowed the adjacent match, so it doesn't pin the non-consuming count.
compose --result help (compose.go): add that re-check may appear only in its own segment. compose never runs routeReason, so the help is the only guidance there.
Look-alike spellings (pulldigest.go, recheckWords): re‐check with U+2010 and recheck aren't counted, so a second date written that way is ignored. The digest still only uses the exact segment's date, so at worst this is a decoy. Either refuse those spellings or say so in the comment.
Done means: each box is fixed or explicitly declined with a reason, go -C .claude/scripts/blocked-label-blocker-line-go test ./... passes, and .claude/scripts/rule-sensor-inventory.sh --check passes.
Superseded by #5056, merged at e16ef48d84c5551fc4b81866cf14f998a02c2353. I checked all four deferred items against the adopted source:
The old tried: / next: segment wording is retired; routes now use standalone Tried:, Next: and Re-check YYYY-MM-DD lines.
The adjacent-match unit test is declined because recheckWords and its Go module were deleted.
The compose --result help change is declined because the composer was deleted.
The look-alike spelling change is declined because the old free-text word counter was deleted; the replacement reads a standalone dated line.
The replacement checker's existing behavioral suite passes, and rule-sensor-inventory.sh --check passes. The retired module's Go test command no longer exists. These observations settle this follow-up only: the live checker still reports four closed-blocker PRs and one dependency PR without a current route, which remain separate finishing work.
Closing as not planned because the implementation this follow-up targeted has been removed.
Activity
chore: agent-claim #5000 nonce=4d49fb31213ce29fca82fc4672768b7a
devantler commentedon Nov 14, 2026
Superseded by #5056, merged at
e16ef48d84c5551fc4b81866cf14f998a02c2353. I checked all four deferred items against the adopted source:tried:/next:segment wording is retired; routes now use standaloneTried:,Next:andRe-check YYYY-MM-DDlines.recheckWordsand its Go module were deleted.compose --resulthelp change is declined because the composer was deleted.The replacement checker's existing behavioral suite passes, and
rule-sensor-inventory.sh --checkpasses. The retired module's Go test command no longer exists. These observations settle this follow-up only: the live checker still reports four closed-blocker PRs and one dependency PR without a current route, which remain separate finishing work.Closing as not planned because the implementation this follow-up targeted has been removed.
chore: agent-claim #5000 nonce=4f4982f33eb060ca46e528b970ee7396
chore: agent-claim #5000 nonce=a40778cfb6d6d479a5eaf184bad4fc7d