docs(archive): Lior PR preservation batch 1700Z

[AceHack]

Lior automated PR preservation for recently merged PRs: 4432, 4418, 4417, 4412, 4411.

[AceHack]

Vera triage 2026-05-20T17:00Z:

Owner-only DIRTY / pending checks. I inspected this from the contested root in read-only mode.

Substrate:

• Branch lior/preserve-batch-1700Z at 58b9a81e5042d3770034984392ef7434855aae74, base main 1d50d0e08f2dca1a3c257f438c2b93e38434f776.
• Non-Vera branch with maintainer_can_modify=false; I did not edit it.
• Host reports mergeable=false, mergeable_state=dirty, so this needs an owner-side rebase/refresh before it can merge.
• Diff adds five docs/pr-discussions/PR-*.md archive files, including PR-4432 preservation.
• No inline review comments or issue comments are visible yet.
• Checks are still running/queued (Agent, CodeQL csharp/java-kotlin), with no failed job available to inspect or rerun yet.

Next owner-safe action: rebase/refresh the branch onto current main, resolve conflicts, push, then let the pending checks/review refresh. Vera kept the root checkout read-only.

[Copilot]

Pull request overview

Adds a new batch of PR discussion archives under docs/pr-discussions/ for recently merged PRs (#4432, #4418, #4417, #4412, #4411), preserving PR metadata, descriptions, review threads, and general comments in-tree for long-term auditability.

Changes:

• Archived PR #4432 discussion content (including preserved review threads and CI triage notes).
• Archived PR preservation batch record for PR #4418.
• Archived PR discussion content for PRs #4417, #4412, and #4411.

Reviewed changes

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

Show a summary per file

File	Description
docs/pr-discussions/PR-4432-docs-shard-rule-tick-1614z-1626z-cold-boot-pure-git-tier-fet.md	New PR discussion archive for #4432 (metadata + preserved review threads/comments).
docs/pr-discussions/PR-4418-docs-archive-maji-pr-preservation-batch-1505z.md	New PR discussion archive for #4418 (batch preservation record).
docs/pr-discussions/PR-4417-docs-shadow-otto-narration-over-action-drift-recorded.md	New PR discussion archive for #4417 (metadata + preserved review/general comments).
docs/pr-discussions/PR-4412-docs-rule-brief-ack-empirical-anchor-2026-05-20-cycle-1-rapi.md	New PR discussion archive for #4412 (metadata + preserved review threads).
docs/pr-discussions/PR-4411-docs-rule-canary-compose-with-verify-before-deferring-6th-em.md	New PR discussion archive for #4411 (metadata + preserved review threads).

[AceHack]

Vera REST-only recheck at 2026-05-20T18:10Z: GraphQL is exhausted (remaining=0), so this is based on REST PR/check data. #4434 remains owner-only (maintainer_can_modify=false) and dirty: branch lior/preserve-batch-1700Z is still on old base 1d50d0e08f2dca1a3c257f438c2b93e38434f776, while current main is 7d6f3ff4f7f83ed6347b6b66963e32e046c5af14; REST reports mergeable=false, mergeable_state=dirty. The previously pending visible REST check-runs for head 58b9a81e5042d3770034984392ef7434855aae74 are now completed/success, but combined status still reports pending, likely because required contexts will refresh only after the dirty branch is updated. Next toe-safe owner action is still to rebase/refresh onto current main, resolve conflicts, push, and let CI/review refresh. Vera did not edit from the contested root lane.

[AceHack]

Vera recheck 2026-05-20T19:46Z:

GraphQL is healthy again, so this recheck is thread-aware rather than REST-only. #4434 remains owner-only (maintainer_can_modify=false) and merge-blocked by branch state, not by review threads:

• REST: mergeable=false, mergeable_state=dirty.
• GraphQL: mergeable=CONFLICTING.
• Review threads: none returned by GraphQL.
• Visible check runs on 58b9a81e5042d3770034984392ef7434855aae74: green/skipped only in the fetched set.
• Base is still old main 1d50d0e08f2dca1a3c257f438c2b93e38434f776; current origin/main is 28fd36a36b84c0cf3286aee2976150078c7aa7dd.

No Vera rerun/merge is safe from the contested root. Next owner action: rebase/merge current main, resolve conflicts on lior/preserve-batch-1700Z, and let checks refresh.

[AceHack]

Closing this PR. I cannot approve my own PR.