fix(lint): grandfather pre-existing 0007Z-c B-0668 broken link in tick-shard baseline#4396
Merged
AceHack merged 1 commit intoMay 19, 2026
Conversation
…k-shard relative-paths baseline Re-shipping the baseline fix that was on PR #4393 branch but did NOT land via the squash-merge (auto-merge fired on first SHA before second commit pushed; merge sha d3a8159 only included substrate landing, not the lint fix). Without this fix, the tick-shard relative-paths lint fails for ALL future PRs that trigger full-tree scan. Pre-existing finding: docs/hygiene-history/ticks/2026/05/19/0007Z-c.md references B-0668-compositional-dbsp-* via a 6-level relative path, but no B-0668-* file landed on origin/main (PRs #4281 + #4386 both CLOSED-without-merge per gh pr view --json state). Per tick-shard immutability discipline (.claude/rules/tick-must-never-stop.md: shards write-once at docs/hygiene-history/ticks/YYYY/MM/DD/HHMMZ.md), the link cannot be edited in-place. Baseline-grandfathering is the substrate-honest fix: detect-only signal preserved, CI gate passes. Verified locally: bun tools/hygiene/audit-tick-shard-relative-paths.ts --enforce --baseline ... exit=0; "13 broken relative-path links (13 grandfathered by baseline, 0 new)". Composes with #4180 (baseline mechanism shipped) and other prior baseline-extension PRs (e.g., #4358 peer Otto's PR-fix batch). Co-Authored-By: Claude <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Pull request overview
Updates the tick-shard relative-path lint baseline to grandfather a newly-discovered (already-merged) broken link in the 2026-05-19 0007Z-c tick shard, keeping the audit-tick-shard-relative-paths CI gate from failing future PRs.
Changes:
- Add a baseline entry for
docs/hygiene-history/ticks/2026/05/19/0007Z-c.md:7pointing at the missingB-0668backlog-row path so it’s treated as “known historical residue” under--enforce --baseline.
AceHack
deleted the
otto/fix-shard-lint-baseline-0007z-c-grandfather-2026-05-19
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Re-shipping the baseline fix that was on #4393 branch but did NOT land via the squash-merge (auto-merge fired on first SHA before the second commit pushed; merge sha d3a8159 only included substrate landing, not the lint fix).
Without this fix, tick-shard relative-paths lint FAILS for ALL future PRs that trigger full-tree scan — confirmed locally.
Root cause
docs/hygiene-history/ticks/2026/05/19/0007Z-c.md(already on main) references../../../../../../docs/backlog/P1/B-0668-compositional-dbsp-...mdvia 6-level relative path, but noB-0668-*file landed onorigin/main— PRs #4281 + #4386 both CLOSED-without-merge pergh pr view --json state.Per tick-shard immutability discipline (
.claude/rules/tick-must-never-stop.md), shards are write-once atdocs/hygiene-history/ticks/YYYY/MM/DD/HHMMZ.md. The link cannot be edited in-place. Baseline-grandfathering is the substrate-honest fix.Verification
Composes with
Follow-up (separate PR if pursued)
Tasks #34 + #35 corrected — B-0668 + B-0669 substrate is NOT on main. Re-shipping those backlog rows is a separate substantive work item. Until then, baseline-grandfathering keeps CI unblocked.
🤖 Generated with Claude Code