fix(shard-1547z-on-main): correct relative-path depth — unblock PR #3898 lint#3906
Merged
Merged
Conversation
…6× ../; docs/ needs 5× ../) PR #3900 auto-merged the ORIGINAL broken-paths commit 9986e58 BEFORE the fix-push 53bc359 (to the same branch) registered. The broken 1547Z.md is now on main and was blocking PR #3898's lint check. This direct-fix-on-main re-applies the same corrections that lived on the now-orphaned 1547Z branch's fix-commit. Once merged, PR #3898 will pass lint and auto-merge. The path-depth reference table for future tick-authoring is documented in 1610Z.md (landed via PR #3903) so this class of error has wake-time substrate. Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR fixes broken relative-link paths in the 1547Z tick shard on main, correcting directory-depth counts so audit-tick-shard-relative-paths no longer reports new findings and PR #3898’s lint gate can pass.
Changes:
- Correct relative-path depth for links targeting
docs/backlog/**,docs/AUTONOMOUS-LOOP-PER-TICK.md, and.claude/rules/**fromdocs/hygiene-history/ticks/2026/05/16/1547Z.md. - Replace the sibling-shard link to
1535Z.md(not present onmain) with a stable link to PR #3898.
Merged
2 tasks
AceHack
added a commit
that referenced
this pull request
May 16, 2026
…med-dep loop closed (#3908) * fix(rules): document 3 stale-armed-PR resolution patterns in blocked-green-ci rule This session's empirical evidence (5 stale-armed PR investigations between 13:10Z and 16:33Z) clarifies three distinct resolution patterns: close-as-redundant, re-land-via-cherry-pick, and forward-signal-comment. Added a decision tree and links to the empirical instances. Composes with the forced-escalation-finds-hidden-work anchor on holding-without-named-dependency rule (PR #3901). Co-Authored-By: Claude <noreply@anthropic.com> * shard(tick): 2026-05-16T16:34Z — cascade complete; lint-failure-as-named-dep loop closed 1h 03m cascade from 1531Z → 1634Z. PRs #3897 (B-0462), #3898 (1535Z shard), #3900 (1547Z shard), #3903 (1610Z + path-depth table) all merged. PR #3906 (fix-1547z-on-main) auto-merging cleanly (22/25 SUCCESS, 2 pending). Substrate-honest lessons: - Auto-merge race (sub-case 5 of claim-acquire saturation-ceiling) - Lint check classification: broken paths on main propagate as new errors to subsequent PRs via the audit's all-shards scan - Path-depth reference table (1610Z, PR #3903) is the durable substrate fix Persistent contamination: git branch --show-current caught HEAD-shift to 5 different peer-Otto branches across 5 cron fires; no commits landed on peer branches. Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
2 tasks
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
PR #3900 auto-merged the ORIGINAL broken-paths commit `9986e5860f` BEFORE the fix-push `53bc359` (to the same branch) registered. The broken `1547Z.md` is now on `main` and is blocking PR #3898's `lint (tick-shard relative-paths)` check.
This direct-fix-on-main re-applies the same corrections that lived on the now-orphaned 1547Z branch's fix-commit `53bc359`. Once merged, PR #3898 will pass lint and auto-merge.
Path corrections
Test plan
Substrate-honest lessons (already encoded in PR #3903's path-depth reference table)
🤖 Generated with Claude Code