shard(tick): 2151Z — temporal-provenance discipline (citing PRs in flight)#3273
Merged
AceHack merged 1 commit intoMay 14, 2026
Conversation
…ight) 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>
There was a problem hiding this comment.
Pull request overview
Adds a tick-shard document recording the 2151Z hygiene tick, documenting how two reviewers (Copilot + Codex) both flagged a temporal-provenance issue on #3267 and codifying three patterns for handling minimal-continuation shards that reference in-flight prior shards.
Changes:
- New tick shard at
docs/hygiene-history/ticks/2026/05/14/2151Z.mdrecording 2151Z tick. - Codifies three patterns for citing in-flight prior shards (stack PRs, inline context, or reply-at-review).
- Logs session running tally and audit-discipline candidate for future filing.
6 tasks
AceHack
added a commit
that referenced
this pull request
May 14, 2026
…nds (#3275) Tick output: - PR #3274 (fix(shard-2146Z) grep rendering + operands): converted inline grep command to fenced bash code block + added file operand. Two Copilot catches addressed (P1 rendering bug + P2 reproducibility). Verified corrected command exits 1 (no matches) matching claim. Auto-merge armed. - Both threads on #3271 acknowledged with reply pointing to #3274; resolved. - This shard. Pre-push lint also caught an MD038 issue in the shard table (literal triple-backticks inside single-backtick code span); fixed before push. Pre-push lint continues to pay off. Discipline codified: - Inline-code-span: choose single/double/fenced based on content - Reproducibility: every quoted command should be runnable as-is Audit-discipline candidates filing list: - audit-shard-broken-links.ts (filed 2146Z) - temporal-provenance audit (filed 2151Z) - audit-shard-runnable-commands.ts (this tick — new) Prior-tick PRs merged this batch: - #3271 (shard 2146Z) MERGED as 9691495 - #3273 (shard 2151Z) MERGED as 1862096 Session tally: 31 merged + 1 wait-ci (#3274) + this shard's PR. 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
Tick 2026-05-14T21:51Z shard. Substantive work was thread triage on #3267 where both Copilot AND Codex flagged the same temporal-provenance issue: the 2143Z shard cited 2139Z but at review-time #3264 (which authored 2139Z) was still wait-ci.
Two-reviewer convergence (again)
Earlier this session #3258 had Copilot + Codex converge on the same arithmetic catch. This tick #3267 has them converging on the same temporal-provenance catch. Two reviewers converging is not a noise nit — it's a real bug.
Resolution
Replied to both threads explaining that by merge-time #3264 had merged (
5a88735), so 2139Z was on main and the cross-reference is navigable. Threads resolved with the explanation.Pattern codified — three options for minimal-continuation shards
gh pr create --base <prior-branch>so the tree at review-time contains the cited prior shardFiled for future tick
Audit-discipline candidate: TS script 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).Prior-tick PRs merged this batch
a093da229983a5Session running tally: 29 merged + 1 wait-ci (#3271) + this shard's PR
Test plan
markdownlint-cli2+audit-md032-plus-linestartcleangh pr create --head🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com