5c4bce54f6
- Updated prerequisite tree: added Nomad+Vault orchestration (S0-S5 done), #982 engagement data loss, stuck issues section - Created vault procurement for #758 (ops branch protection) - Graph: 226 nodes, 223 edges
33 lines
1.6 KiB
Markdown
33 lines
1.6 KiB
Markdown
# Request: Remove or relax ops repo branch protection for agent writes
|
|
|
|
## What
|
|
The ops repo (`disinto-ops`) has branch protection on `main` that blocks all agent writes. `planner-bot` has push access but cannot merge. `review-bot` can approve but cannot push. No admin token is available to agents.
|
|
|
|
## Why
|
|
Blocks #758 (ops repo branch protection), which blocks:
|
|
- #820 (re-seed ops repo directories) — vault lifecycle dirs, evidence dirs, portfolio.md, RESOURCES.md
|
|
- Vault-gated fold transitions — vault/pending/, approved/, fired/ directories needed
|
|
- All planner ops pushes — prerequisites.md frozen since run 2 (2026-04-08)
|
|
- Evidence collection for all agents
|
|
|
|
Waiting since 2026-04-08 (10 days). This is the single root blocker for the Adoption milestone.
|
|
|
|
## Human action
|
|
1. Go to Forgejo admin → `disinto-ops` repo → Settings → Branches → Branch protection for `main`
|
|
2. Either:
|
|
a. Add `planner-bot` to the push/merge allowlist, OR
|
|
b. Remove branch protection from `disinto-ops` `main` entirely (ops repo is internal, not public-facing)
|
|
3. Verify by pushing a test commit or confirming `planner-bot` can push
|
|
|
|
## Factory will then
|
|
- #758 auto-closes (dev-agent or planner detects push succeeds)
|
|
- #820 picks up immediately (re-seed ops directories)
|
|
- Planner pushes prerequisite tree, memory, and vault items to remote
|
|
- Vault lifecycle workflow becomes operational
|
|
- Evidence collection pipeline unblocks
|
|
|
|
## Unblocks
|
|
- #758 — ops repo branch protection blocks all agent writes
|
|
- #820 — re-seed ops repo directories
|
|
- #697 — example project (transitively, via bootstrap verification)
|
|
- Vault-gated fold transitions (Ship milestone)
|