docs(archive): Maji PR preservation batch 9

[AceHack]

Preserving merged PRs 4122, 4121, 4120, 4119 into docs/pr-discussions/ via archive-pr.ts

[Copilot]

Pull request overview

Archives the GitHub PR conversations for PRs #4119–#4122 into docs/pr-discussions/ using tools/pr-preservation/archive-pr.ts, so merged PR context (description, reviews, threads, and comments) is preserved in-repo for later archaeology.

Changes:

• Adds four new PR discussion archive markdown files under docs/pr-discussions/ for PRs #4119, #4120, #4121, and #4122.
• Captures PR metadata in YAML frontmatter plus the PR description, reviews, review threads, and general comments for each PR.

Reviewed changes

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

File	Description
docs/pr-discussions/PR-4122-backlog-b-0614-4-empirical-instances-candidate-rule-text-ref.md	Archived PR #4122 discussion, including B-0614 evidence/refinement narrative and review threads.
docs/pr-discussions/PR-4121-shard-2026-05-17-2300z-multi-pr-arc-summary-2207z-cold-boot.md	Archived PR #4121 discussion for the 2300Z shard arc summary.
docs/pr-discussions/PR-4120-backlog-b-0614-forced-6-meta-fallback-edge-case-post-cycle-c.md	Archived PR #4120 discussion for creating backlog row B-0614 and related review content.
docs/pr-discussions/PR-4119-docs-shadow-maji-antigravity-check-on-vera-extreme-narration.md	Archived PR #4119 discussion for the shadow/antigravity check write-up.

Comments suppressed due to low confidence (1)

docs/pr-discussions/PR-4120-backlog-b-0614-forced-6-meta-fallback-edge-case-post-cycle-c.md:41

• This tools/backlog/generate-index.ts link is currently relative to docs/pr-discussions/ and therefore broken (docs/pr-discussions/tools/... doesn’t exist). Please change it to a correct relative path (e.g., ../../tools/backlog/generate-index.ts) or a GitHub URL.

[`tools/backlog/generate-index.ts`](tools/backlog/generate-index.ts) walks only P0-P3 tiers (the original P4 directory was silently skipped). Row moved P4 → P3. Not filed as a separate row — small generator-scope finding, in-scope mention here.

[AceHack]

Vera handoff (2026-05-21T11:42Z): inspected as the next open PR without a prior Vera/Codex top-level handoff.

Current state:

• Base is stale: 19db3cc32081725be8471c35acad03dbf07e270d; current main is 555623234eaa5469a9034a5944849edfee131875.
• Head is 30d42d88d2017c69455692eafeadfbea88d62f19 on maji/preserve-batch9.
• maintainerCanModify=false, mergeable=CONFLICTING, mergeStateStatus=DIRTY.
• Checks shown are green (CodeQL + dependency submission); no failed CI job exists to inspect or rerun.
• Two unresolved non-outdated review threads remain.

Actionable blockers:

• In docs/pr-discussions/PR-4120-backlog-b-0614-forced-6-meta-fallback-edge-case-post-cycle-c.md, rewrite repo-root-style archive links that currently resolve under docs/pr-discussions/docs/... or docs/pr-discussions/.claude/.... Use valid relative paths such as ../backlog/..., ../../.claude/..., or canonical GitHub blob/main URLs. Same issue is noted at line 41.
• In docs/pr-discussions/PR-4122-backlog-b-0614-4-empirical-instances-candidate-rule-text-ref.md, rewrite the docs/backlog/... archive link to a valid relative path such as ../backlog/P3/... or a canonical GitHub URL.
• The suppressed Copilot note also points to tools/backlog/generate-index.ts in the PR-4120 archive resolving as docs/pr-discussions/tools/...; if retained, use ../../tools/backlog/generate-index.ts or a canonical GitHub URL.

Owner-side next step: rebase onto current main, fix the archive-local links, and re-run checks. Vera did not write locally because the root checkout is contested and this PR is owner-only.

[AceHack]

Closing this PR. I cannot approve my own PR.