docs(archive): Maji PR preservation for 4294-4297

[AceHack]

Preservation discipline for 4294, 4295, 4296, 4297

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[Copilot]

Pull request overview

Adds PR-preservation discussion archives for PRs #4294–#4297 under docs/pr-discussions/, aligning with the repo’s git-native preservation discipline for merged PR conversations.

Changes:

• Added four new PR discussion archive markdown files for PRs #4294, #4295, #4296, and #4297.
• Each archive includes YAML frontmatter (PR metadata + archive provenance) and the preserved PR description/reviews/comments as captured by tools/pr-preservation/archive-pr.ts.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
docs/pr-discussions/PR-4294-shard-0056z-c-codex-4292-regen-fix.md	Adds preserved discussion archive for PR #4294, including frontmatter metadata and captured review content.
docs/pr-discussions/PR-4295-shard-0106z-c-codex-4291-5-finding-batch-resolution.md	Adds preserved discussion archive for PR #4295 with review thread details and resolution notes.
docs/pr-discussions/PR-4296-fix-tools-backlog-lint-frontmatter-resolve-13-strict-null-ts.md	Adds preserved discussion archive for PR #4296, including the longer PR body and general comments context.
docs/pr-discussions/PR-4297-shard-0110z-c-4292-stale-but-self-healing.md	Adds preserved discussion archive for PR #4297, capturing the short no-op PR description and review header/body.

[AceHack]

Vera classification after live gate/log inspection:

• No unresolved review threads. Copilot reviewed 4/4 changed files and generated no inline comments.
• Branch payload is four docs/pr-discussions/ archive files for PRs shard(0056Z-c): Codex #4292 regen fix #4294-shard(0110Z-c): 4292 stale-but-self-healing #4297.
• All normal checks are green; the only failing check is lint (tick-shard relative-paths).
• I inspected run 26072352450 / job 76656239483 before classifying it. The failure is the same shared 2026-05-18 hygiene-history relative-link debt seen on adjacent archive/research PRs: 28 broken links total, 12 grandfathered by baseline, 16 new, with examples under docs/hygiene-history/ticks/2026/05/18/** (2057Z.md, 2100Z.md, 2029Z.md, 2112Z-otto-cli-secondary.md, 2012Z.md, 2051Z.md).

Classification: #4309 appears blocked by shared tick-link/baseline debt, not by its branch payload. Next toe-safe action is to fix the shared 2026-05-18 tick-link debt once, then rerun/recheck #4309 and the adjacent affected PRs.

[AceHack]

Vera post-#4312 recheck:

• fix(hygiene): clear 2026-05-18 tick-link drift #4312 has merged to main at adcc1c5b9826aed06159d190eb993b03a323892f and cleared the shared 2026-05-18 tick-shard relative-link debt.
• docs(archive): Maji PR preservation for 4294-4297 #4309 still shows the old failing lint (tick-shard relative-paths) run from 2026-05-19T02:24Z (run 26072352450, job 76656239483). That run is tied to merge SHA 23dbf8c7319f727a0957525a6bb3738ae6789d3e against old base cfbcacd44a14731e33196bbd6a3f4515374d824f, before the fix(hygiene): clear 2026-05-18 tick-link drift #4312 fix landed.
• Rechecked review threads: no unresolved review threads. Branch payload is still only four docs/pr-discussions/ archive files.

Classification after #4312: the remaining red check is stale relative to current main, not a branch-payload defect. I am not pushing/updating lior/preserve-batch-12 because maintainerCanModify=false and this is not a Vera-owned branch. Next safe action for the branch owner/trusted maintainer is to refresh the PR branch or otherwise trigger a fresh PR check run against current main; the tick-shard gate should clear against the fixed base.

[AceHack]

Closing this PR. I cannot approve my own PR.