fix(shard-2139Z): replace broken relative markdown links with backtick paths#3269
Merged
AceHack merged 1 commit intoMay 14, 2026
Merged
Conversation
…k paths Copilot caught post-merge on PR #3264: three markdown links in 2139Z.md used relative paths that resolved to docs/hygiene-history/ticks/2026/05/14/.claude/... (404 in any rendered view). The convention in OTHER tick shards is plain backticks without link, e.g., `.claude/rules/foo.md`. Changed 3 occurrences: - Line 12: `holding-without-named-dependency-is-standing-by-failure.md` - Line 31: `never-be-idle.md` - Line 40: `docs/hygiene-history/ticks/2026/05/14/2001Z.md` Plain-backtick form chosen over root-relative (the other Copilot suggestion) because it matches the established shard-authoring convention. Scan of all other today's shards: no other instances of the bug. Post-merge cleanup: #3264 already merged the shard with the bug. This PR fixes forward on main. Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR performs a narrow documentation cleanup in a hygiene-history tick shard by replacing broken relative Markdown links with plain backtick paths.
Changes:
- Replaced two
.claude/rules/...Markdown links with inline path references. - Replaced one same-directory hygiene-history link with an inline path reference.
- Aligns the shard with nearby tick-shard path-reference style.
5 tasks
AceHack
deleted the
fix/shard-2139Z-broken-relative-links-otto-cli-2026-05-14
branch
AceHack
commented
May 14, 2026
Member
Author
AceHack
left a comment
AceHack
left a comment
There was a problem hiding this comment.
Antigravity check: Clean fix. Parity proved.
AceHack
added a commit
that referenced
this pull request
May 14, 2026
… bug (#3271) Tick output: - PR #3269 (fix(shard-2139Z) broken relative links): replaced 3 occurrences of relative markdown links with plain backtick form (matching established shard-authoring convention). Auto-merge armed. - Post-merge thread on #3264 (Copilot caught the bug) resolved with reply pointing to #3269. - This shard. Real substantive catch by Copilot: markdown links like `[text](.claude/rules/foo.md)` from a tick shard at docs/hygiene-history/ticks/2026/05/14/ resolve to docs/hygiene-history/ticks/2026/05/14/.claude/... (404 in render). Convention codified: use plain backticks for path references in tick shards, NOT markdown links. Two acceptable patterns: 1. `.claude/rules/foo.md` (preferred — repo convention) 2. [link](/path/to/foo.md) (root-relative if linking is needed) Scan of all OTHER today's shards: 0 instances. Bug isolated to 2139Z. Filed mentally: audit-shard-broken-links.ts candidate (cousin to audit-md032-plus-linestart.ts). Session tally: 27 merged + 2 wait-ci. Cron sentinel 12fb713e armed; recurring. Co-authored-by: Claude <noreply@anthropic.com>
5 tasks
AceHack
added a commit
that referenced
this pull request
May 14, 2026
…ight) (#3273) Tick output: - Resolved 2 unresolved threads on #3267 (shard 2143Z): both Copilot AND Codex caught the same temporal-provenance issue (2143Z cited 2139Z but #3264 was still wait-ci at review-time; tree at #3267's base didn't have the cited file). Reply explained that by merge-time the cross-reference is navigable; threads resolved. - This shard codifies the temporal-provenance discipline. Three patterns for minimal-continuation shards that cite in-flight prior shards: 1. Stack on prior shard's PR (--base <prior-branch>) 2. Inline the minimal audit-sweep context (self-contained shard) 3. Reply at review-time + resolve (pragmatic for tight cron cadence) Audit-discipline candidate filed: tool that scans tick shards for cross-references to other tick-shards whose PRs are still open. Cousin to audit-shard-broken-links.ts (filed in 2146Z). Two-reviewer convergence continues to be strong signal: - This tick: Copilot + Codex on temporal-provenance - Earlier (#3258): Copilot + Codex on tally arithmetic Prior-tick PRs merged this batch: - #3267 (shard 2143Z) MERGED as a093da2 - #3269 (broken-link fix) MERGED as 29983a5 Session tally: 29 merged + 1 wait-ci. Cron sentinel 12fb713e armed; recurring. Co-authored-by: Claude <noreply@anthropic.com>
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
Post-merge cleanup of #3264. Copilot caught that three markdown links in
2139Z.mdused relative paths that resolve todocs/hygiene-history/ticks/2026/05/14/.claude/...— broken in any rendered view.Changes
Replaced 3 broken relative links with plain backtick paths (matching the established shard-authoring convention):
[link](.claude/rules/holding-without-...md)`.claude/rules/holding-without-...md`[link](.claude/rules/never-be-idle.md)`.claude/rules/never-be-idle.md`[link](docs/hygiene-history/ticks/2026/05/14/2001Z.md)`docs/hygiene-history/ticks/2026/05/14/2001Z.md`Why backticks over root-relative
Copilot suggested either
/.claude/rules/...(root-relative) or plain backticks. The repo's existing tick shards (2001Z, 2010Z, 2026Z, etc.) use plain backticks without link — chose that for consistency.Scan of other shards
grep -nE "\[\?[^]]`?](.claude/|[[^]]](docs/hygiene" docs/hygiene-history/ticks/2026/05/14/2*.md` returns 0 other instances. Bug isolated to 2139Z.Test plan
markdownlint-cli2clean.claude/...ordocs/hygiene-history/...links remain in 2139Zgh pr create --headused🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com