Skip to content

chore(scripts): tighten the parked digest's route-record docs and tests #5000

Closed as not planned

Description

@devantler

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.

🤖 Generated with Claude Code

Activity

  1. added theissue type on Nov 13, 2026
  2. moved this to 📥 Backlog in 🌊 Project Boardon Nov 13, 2026
  3. added a commit that references this issue on Nov 14, 2026
  4. devantler commented on Nov 14, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    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.

  5. added a commit that references this issue on Nov 14, 2026
  6. moved this from 📥 Backlog to ✅ Done in 🌊 Project Boardon Nov 14, 2026
  7. added a commit that references this issue on Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions