backlog(P2): B-0529 — tick-shard schema validator vs current practice drift#3362
Merged
Merged
Conversation
… drift Codex P1 review on PR #3359 surfaced that tools/hygiene/check-tick-history-shard-schema.ts expects a 6-column pipe-row first line per docs/hygiene-history/ticks/README.md, but the May 2026 shard cohort universally starts with H1 (substrate-wide drift). Validator is NOT wired to CI, so violations have been invisible. This row proposes Option 3 (hybrid): pipe-row first line + H1-rich body. Three sub-tasks sequenced: backfill May 2026 shards, update README, wire validator to CI gate. Refs: - PR #3359 (Codex P1 surface) - PR #3361 (this tick's shard following hybrid pattern) Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a new P2 backlog row (B-0529) to document and track the drift between the tick-shard schema validator’s “pipe-row first line” expectation and the May 2026 practice of H1-rich shard bodies, including options and a recommended hybrid approach.
Changes:
- Introduces backlog item B-0529 describing the validator/practice mismatch and its operational implications.
- Captures concrete reproduction output and proposes a sequenced remediation plan (backfill → docs update → CI wiring).
Comment on lines
+23
to
+27
| `tools/hygiene/check-tick-history-shard-schema.ts` validates that every tick shard's first non-empty line is a 6-column pipe-row with an ISO 8601 UTC timestamp matching the path's date + the filename's `HHMMZ`. The schema is documented in [docs/hygiene-history/ticks/README.md](../../hygiene-history/ticks/README.md): | ||
|
|
||
| ```text | ||
| | <ISO 8601 UTC timestamp> | <model id> | <cron sentinel> | <body> | <PR ref> | <observation> | | ||
| ``` |
|
|
||
| ## What | ||
|
|
||
| `tools/hygiene/check-tick-history-shard-schema.ts` validates that every tick shard's first non-empty line is a 6-column pipe-row with an ISO 8601 UTC timestamp matching the path's date + the filename's `HHMMZ`. The schema is documented in [docs/hygiene-history/ticks/README.md](../../hygiene-history/ticks/README.md): |
6 tasks
AceHack
added a commit
that referenced
this pull request
May 15, 2026
…estigation cleared 4 standard agent loops (#3365) Negative-finding substrate: cleared Lior, Riven, Codex/Vera, Copilot loops + lane-allocator + git worktree prune + git gc.pruneexpire as suspects for the worktree-pruning race observed in tick 0414Z. Source remains untraced; remaining candidates (claude-loop, otto-forward, peer-Otto, .git/hooks/, macOS system services) listed for next-tick investigation. Investigation-budget discipline: 12 tool calls; diminishing returns; next-tick continuation. Co-authored-by: Claude <noreply@anthropic.com>
This was referenced May 15, 2026
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
Files B-0529 P2 row documenting the substrate-wide drift between the documented 6-col pipe-row tick-shard schema and the H1-rich-body practice that the May 2026 cohort adopted. Surfaced via Codex P1 review on PR #3359.
Recommendation: hybrid (Option 3) — keep machine-parseable pipe-row first line + H1-rich body. Three sub-tasks sequenced:
docs/hygiene-history/ticks/README.md"Shard file schema" sectionP2 priority because the validator is NOT wired to CI — drift is invisible at gate-time today.
Test plan
bun x markdownlint-cli2 docs/backlog/P2/B-0529-*.md→ 0 violations🤖 Generated with Claude Code