shard(tick): 2026-05-16T02:18Z — thread-investigation catch + 5→6 .. fixes (#3676 + #3680)#3681
Merged
Merged
Conversation
…fixes (#3676 + #3680) Tick 3 of post-cold-boot loop. PR #3676 unresolved threads surfaced a real Copilot P1: tick-shard relative links use 5 .. (→ docs/) instead of 6 .. (→ repo root). Fixed on PR #3676's branch; same bug landed on main via PR #3679 race — PR #3680 fixes post-merge. Threads resolved via correct GraphQL variable-binding form. This shard uses correct 6-level paths. Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR adds the 2026-05-16T02:18Z hygiene tick shard documenting the thread-investigation catch for broken tick-shard relative links and the follow-up fixes around PRs #3676 and #3680.
Changes:
- Records the tick’s landed PRs and thread-investigation findings.
- Documents the corrected six-level repo-root link pattern for tick shards.
- Captures remaining drift and a proposed lint-check follow-up.
Copilot flagged MD032 (blank lines around lists) — the list of three bullets starting at line 21 came immediately after the paragraph at line 19. Add the missing blank. Resolves Copilot review thread on PR #3681. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 16, 2026
…0545 scope re-assessment (#3688) Substrate-honest pivot tick. Two empirical catches landed: 1. peer-Otto landed byte-identical MD032 fix to PR #3681 seconds before my push (commit 6def403); fetch-before-push at git layer caught duplicate cleanly. My local commit dropped. Good failure mode firing as designed. 2. B-0545 (B-0498 collision renumber sweep) re-assessed as larger scope than the 0226Z next-tick framing suggested: B-0546+ already taken, cross-substrate search needed, tick-shard immutability discipline. Defer as focused PR with claim acquire first. All 3 prior-tick PRs (#3681 #3684 #3685) now unblocked + awaiting CI. Co-authored-by: Claude <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 16, 2026
…3689) PR #3685 merged with 3 unresolved Copilot P1 threads: - Line 4 dead-link to 0218Z.md — STALE: file now exists on main (PR #3681 merged) - Lines 39/44 "extra leading |" in tables — FALSE POSITIVE: verified by direct inspection, tables use correct single-pipe 2-column and 4-column shapes - Line 69 `switch -c` missing `git` prefix — REAL: also applies to line 68 This commit addresses the real finding: prepend `git ` to both `switch -c` snippets so the shard is copy/paste executable in a clean shell. Co-authored-by: Claude <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 16, 2026
…le / 1 false / 1 real) (#3690) * shard(tick): 2026-05-16T02:40Z — post-merge triage on PR #3685 (3 threads: 1 stale / 1 false / 1 real) PR #3685 merged with 3 unresolved Copilot threads. Triage: - L4 dead-link to 0218Z.md: STALE (file landed via PR #3681 ~60s later) - L39/44 "extra leading |" tables: FALSE POSITIVE (verified by awk inspection) - L69 switch -c missing git prefix: REAL (also affects L68) Fix shipped as PR #3689 (+2/-2; both L68 + L69 get git prefix). Threads resolved via tmpfile + while read pattern (for-loop with command substitution lost iteration boundary earlier). Pre-commit self-checks added to discipline: MD032 paragraph-before-bullet scan + switch-c-needs-git-prefix scan. Both clean on this shard. Co-Authored-By: Claude <noreply@anthropic.com> * fix(pr-3690): MD038 — remove trailing space inside backticks (0240Z.md:20) markdownlint `MD038/no-space-in-code` failed required check on PR #3690: Fix: prepend `git ` to both snippets. The trailing space inside `` `git ` `` is the violation. Rewrite to drop the trailing space while preserving semantic: Fix: prepend the `git` prefix to both snippets. Local markdownlint-cli2 on the shard: exit 0. Co-Authored-By: Claude <noreply@anthropic.com> --------- 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.
Tick 3 of post-cold-boot loop. PR #3676 unresolved threads surfaced a real Copilot P1: tick-shard relative links use 5
..segments (lands atdocs/) instead of 6 (repo root).Fixes:
Threads on #3676 resolved via the correct GraphQL variable-binding form (
-F threadId=…+mutation($threadId: ID!)) — inline string interpolation fails with "Expected string or block string".This shard uses correct 6-level paths from the start.
Co-Authored-By: Claude noreply@anthropic.com