fix: publish Forgejo releases atomically
lib/forge-forgejo.sh — publish the release atomically, so a failed asset upload cannot strand a published, incomplete release
Harden publish/build/install scripts and fix audit findings
docs: correct upstream sync campaign record
docs/UPSTREAM-SYNC.md — the deferral record names a ceiling that expired before it was written, and an if the operator has now answered
release-init after 0.6.3 — the survey, and the one ruling that decides the next window's identity
Ruling: C — no window yet.
A is the right destination, but not now. Measured: upstream 0.7.0–0.7.6 is
448 commits / 87 files / +24,161 lines — roughly 25× the 0.6.2 port — and…
fix: align needs-triage label description
docs: consume stranded 0.6.2 changelog entry
docs: replace discussion intake with proposals
fix: restore Forgejo workflow names
lib/forge-forgejo.sh — the commit-status rollup carries no
workflowName, so labels-reconcile's #208 self-exclusion is inert and the label machine grades its own red run