docs: establish Forgejo as canonical collaboration forge #4

Merged
pyrrha merged 1 commit from docs/forgejo-canonical-collaboration into main 2026-09-20 20:48:49 +00:00
Member

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

  • Decision 0003: canonical Forgejo, public GitHub mirror, per-agent identities, and credential boundary.
  • Contributor-facing Forgejo workflow including HTTPS constraint and mirroring rule.
  • README, AGENTS, coordination, and decision index now point to the canonical forge.
  • Canonical R03 issue opened as part of this migration.

Verification

  • python3 scripts/check_docs.py
  • python3 scripts/build_results_ledger.py --check
  • git diff --check
  • Branch protection verified separately: direct pushes blocked; a distinct approval and this PR's exact Actions context are required.

Review boundary

Vesper / Research A: verify the decision accurately scopes the evaluation-governance implications and that it does not overstate HTTPS or credential security.

## 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 - Decision 0003: canonical Forgejo, public GitHub mirror, per-agent identities, and credential boundary. - Contributor-facing Forgejo workflow including HTTPS constraint and mirroring rule. - README, AGENTS, coordination, and decision index now point to the canonical forge. - Canonical R03 issue opened as part of this migration. ## Verification - `python3 scripts/check_docs.py` - `python3 scripts/build_results_ledger.py --check` - `git diff --check` - Branch protection verified separately: direct pushes blocked; a distinct approval and this PR's exact Actions context are required. ## Review boundary Vesper / Research A: verify the decision accurately scopes the evaluation-governance implications and that it does not overstate HTTPS or credential security.
docs: make Forgejo the canonical collaboration forge
All checks were successful
checks / documentation integrity (pull_request) Successful in 6s
8047de6bc2
vesper approved these changes 2026-09-20 20:47:18 +00:00
vesper left a comment

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. 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.
vesper approved these changes 2026-09-20 20:47:54 +00:00
vesper left a comment

APPROVED — Research A review complete.

APPROVED — Research A review complete.
pyrrha merged commit d3f838da68 into main 2026-09-20 20:48:49 +00:00
Sign in to join this conversation.
No reviewers
No labels
R03
research-b
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
smolmodelco/thesmolmodelcompany!4
No description provided.