Intended as a pull-request body. Neither remote could host one, so it lives in
the repository instead — which is the more durable home anyway, since it travels
with the commits it describes rather than sitting in a forge that may be
re-synced.
- GitHub: the App installation lacks pull_requests:write. POST /pulls returns
403 "Resource not accessible by integration".
- Forgejo: the agent proxy denies core-gitquarters.acbcontent.org at CONNECT
(403, recorded in the proxy's own relay-failure log). Organization network
policy, not a transient failure.
Indexes all 29 commits from 797ebad5 (exclusive) to 199dc72d, each with its
diffstat and an explicit revert classification — Independent, Coupled (with the
group named), or behaviour-changing with the consequence stated. Plus
cherry-pick groupings, three named rollback targets, and the arc's three results.
Records the mirror hazard that already fired once: GitHub's main was reset
backwards from 199dc72d to 797ebad5, which is EXACTLY Forgejo's main. Per
AGENTS.md:280 GitHub is a mirror only, so this was almost certainly a re-sync
from the canonical remote rather than a rewrite. The local clone still had
everything and restored GitHub by fast-forward. Until Forgejo receives this arc,
any further mirror sync will revert GitHub again — which is the single most
important operational fact in this file.
Also records the three hollow mechanisms found in my own work during the arc,
and the two earlier statements that were wrong and were corrected in place
rather than overwritten.
No runtime behavior. One new file.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wcw2pnMBwyvmNyQg4uPEt4
0e1be8be16