32 lines
1.6 KiB
Markdown
32 lines
1.6 KiB
Markdown
# Request: Ops repo branch protection — add planner-bot to merge whitelist
|
|
|
|
## What
|
|
Forgejo branch protection on `disinto-ops` repo blocks all agent writes (git push AND API file commits). The `planner-bot` user needs to be added to the merge whitelist so the planner can push prerequisite tree updates, memory, and vault items.
|
|
|
|
## Why
|
|
Blocks #758 (ops repo branch protection), which blocks:
|
|
- #820 (re-seed ops repo directories)
|
|
- #982 (collect-engagement evidence commit)
|
|
- All planner tree persistence (prerequisites.md stuck since run 2, 2026-04-08)
|
|
- Vault lifecycle directories (pending/approved/fired/rejected)
|
|
- Evidence collection for all agents
|
|
|
|
Waiting since 2026-04-08 (first identified in planner run 2).
|
|
|
|
## Human action
|
|
1. Open Forgejo admin → `disinto-ops` repo → Settings → Branches → Branch Protection for `main`
|
|
2. Add `planner-bot` to the "Merge Whitelist" (and optionally `gardener-bot`, `dev-qwen`, `dev-qwen2` for future ops writes)
|
|
3. Test: `cd disinto-ops && git push` from the agents container (or planner container)
|
|
4. Comment on #758 confirming resolution
|
|
|
|
## Factory will then
|
|
- Planner pushes updated prerequisites.md, knowledge/planner-memory.md, vault items
|
|
- #820 (re-seed ops repo) becomes unblocked and enters dev-agent pipeline
|
|
- #982 (collect-engagement commit) becomes unblocked
|
|
- Vault lifecycle directories are created and populated
|
|
- Evidence collection begins for all agents
|
|
|
|
## Unblocks
|
|
- #758 — ops repo branch protection blocks all agent writes
|
|
- #820 — re-seed ops repo directories
|
|
- #982 — collect-engagement.sh never commits evidence
|