shard(tick): 2026-05-16T03:10Z — baseline mechanism resolves immutability question (PR #3699)#3701
Merged
Merged
Conversation
…lity question (PR #3699) Tick 11 substantive landing: --baseline flag added to audit (option D from tick 8's deferred decision). Avoids the tick-shard-immutability tension entirely — don't edit historical shards; track grandfathered findings; new violations still fail --enforce. Same shape as Stryker/ESLint suppressions. Initial baseline ships with 10 findings from the empirical 02:48Z run. PR #3692 (audit script) MERGED 03:08:39Z by auto-merge — raced my baseline- feature push by ~6s; recovered by cherry-pick onto fresh branch. PR #3699 is the recovered fresh-branch PR. PR #3697 also merged this tick (03:04:32Z). Audit-script PR lifecycle now at 7 steps (matching §33 audit's 4-step backbone + 2 quality rounds + baseline). CI-gate wire-up is the next-tick candidate, unblocked by this baseline landing. Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a tick-history shard documenting the 2026-05-16T03:10Z baseline-mechanism work around the tick-shard relative-path audit.
Changes:
- Adds a new 0310Z tick shard.
- Records the intended
--baselineaudit behavior and lifecycle status. - Captures follow-up CI-gate wiring candidates.
Comment on lines
+27
to
+35
| ## Initial baseline ships with 10 findings | ||
|
|
||
| `tools/hygiene/audit-tick-shard-relative-paths.baseline.json` (1.8 KB) freezes the empirical baseline from the 2026-05-16T02:48Z run on origin/main: | ||
|
|
||
| - 1 in 0852Z.md (line 1) — moved `docs/research/...` reference | ||
| - 5 in 1436Z.md (lines 6×2, 30, 36×2) — wrong-depth `..` for backlog rows + a `.claude/rules/` reference | ||
| - 3 in 0329Z.md (lines 6, 7, 20) — same wrong-depth pattern for backlog rows | ||
| - 1 in 2158Z.md (line 29) — borderline `docs/foo.md` placeholder | ||
|
|
AceHack
added a commit
that referenced
this pull request
May 16, 2026
…+ sweep (#3707) * shard(tick): 2026-05-16T03:22Z — PR #3690 markdownlint MD038 unblock + sweep PR #3690 had been "armed, awaiting CI" since tick 6 (~70 min ago) — turned out to be a REQUIRED check FAILURE on lint (markdownlint), not "still running". MD038/no-space-in-code triggered on `git ` (trailing space inside backticks) at 0240Z.md:20. Fixup 81b2f1a: rewrite "prepend `git ` to" → "prepend the `git` prefix to". Same semantic, no trailing space in code span. markdownlint-cli2 local exit 0. Sweep of all 2026-05-16 shards on main: 0 other MD038 violations. Lesson: required-check failures are a distinct merge-block class from unresolved-threads + non-required-check warnings. poll-pr-gate.ts's nextAction field disambiguates. PR #3701 also merged 03:16:50Z (carry-over). Co-Authored-By: Claude <noreply@anthropic.com> * fix(pr-3707): MD038 self-bite — pre-commit check caught what shipped Same MD038 class I described in this very shard. Line 44 used a literal backtick-git-space-backtick to illustrate the bug pattern, which IS the bug. Inside fenced code blocks (lines 41, 51) the pattern is safe. Rewrite line 44 to describe the pattern in prose without using the literal trailing-space-in-backticks form. markdownlint-cli2 → exit 0. Lesson: pre-commit MD038 self-check would have caught this before push. Adding to the discipline list. Co-Authored-By: Claude <noreply@anthropic.com> * fix(shard): typo "main main" → "`origin/main`" in 0322Z (Copilot #3707) The sweep description on L58 duplicated "main" ("on origin/main main"). Tightening to "on \`origin/main\`" preserves the intent (sweep target = the main branch) and clarifies it's a ref-name, not free text. The other two Copilot threads on this PR are addressed in the reply: - L44 MD038 alarm is a false positive (the literal `` `git ` `` instances live inside ` ```text ` fenced blocks; MD038 only fires on inline code spans; markdownlint exits 0 locally). - L33 cross-reference to 0240Z.md is no longer stale — PR #3690 has merged and the file is present on main. 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 11: --baseline flag added to the tick-shard audit. Resolves the immutability question deferred since tick 8 by choosing grandfather mechanism (option D) — don't edit shards; track baseline; new violations still fail --enforce.
PR #3692 merged 03:08:39Z and raced my baseline-feature push by ~6s; recovered via cherry-pick onto fresh branch (PR #3699).
Audit lifecycle now at 7 steps (discovery → narrow-fix → scanner → filter → quality-r1 → quality-r2 → baseline). CI-gate wire-up is the next-tick candidate, unblocked.
Co-Authored-By: Claude noreply@anthropic.com