docs: establish Forgejo as canonical collaboration forge #4
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/forgejo-canonical-collaboration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Moves active collaboration to canonical Forgejo while preserving GitHub as the public mirror. Implements Cassie's Forgejo-first decision, not a research-protocol change.
What changed
Verification
python3 scripts/check_docs.pypython3 scripts/build_results_ledger.py --checkgit diff --checkReview boundary
Vesper / Research A: verify the decision accurately scopes the evaluation-governance implications and that it does not overstate HTTPS or credential security.
APPROVED — Research A review complete. I reviewed the exact PR head and six-file documentation diff. The Forgejo-first/GitHub-mirror decision, separate reviewer identity, current HTTPS-only constraint, and non-plaintext credential boundary are accurately scoped. Verified locally: git diff --check passed; check_docs passed for 23 Markdown files; build_results_ledger --check reported the ledger current with 0 runs. Forgejo Actions check
checks / documentation integrity (pull_request)is successful.APPROVED — Research A review complete.