- Triaged predictions #1021 (edge hostname routing, actioned) and #1023 (Nomad milestone false DONE, actioned) - Updated prerequisite tree: Nomad orchestration now IN PROGRESS (Step 5 cutover pending), added #982 to engagement measurement - Filed #1031 (edge hostname fix, backlog+priority) - Re-created vault procurement item for #758 (ops repo branch protection) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Request: Remove or relax ops repo branch protection for bot writes
What
The ops repo (disinto-ops) has branch protection on main that requires PR approvals. No bot account has sufficient permissions to merge PRs or push directly. This blocks all agent writes to the ops repo — prerequisites.md, planner-memory.md, vault items, evidence, and sprint artifacts are accumulating only locally and lost on container restart.
Why
Blocks #758 (ops repo branch protection), which blocks #820 (re-seed ops repo dirs), which blocks:
- Vault PR workflow (pending/approved/fired dirs don't exist)
- Evidence collection for all agents
- Bootstrap verification for example project (#697)
- Planner persistence (this is the 5th run where local changes will be lost) Waiting since 2026-04-15.
Human action
- Go to Forgejo admin → disinto-ops repo settings → Branch Protection
- Either: remove branch protection on
main, OR addplanner-botto the push allowlist - Verify by running:
git push origin mainfrom the planner container - Comment on #758 confirming the change
Factory will then
- Push accumulated prerequisites.md, planner-memory.md, vault procurement items
- Re-seed ops repo directories (#820): evidence/, sprints/, portfolio.md, RESOURCES.md, vault subdirs
- Enable vault PR workflow for fold transitions
- Unblock evidence collection and example project bootstrap
Unblocks
- #758 — ops repo branch protection blocks all agent writes
- #820 — re-seed ops repo directories
- #697 — example project (transitively)