31 lines
1.5 KiB
Markdown
31 lines
1.5 KiB
Markdown
|
# Request: Remove ops repo branch protection blocking agent writes
|
||
|
|
|
||
|
|
## What
|
||
|
|
The ops repo (disinto-ops) has branch protection rules on `main` that block all agent git pushes AND Forgejo API file commits. Agents need to write prerequisites.md, evidence files, vault items, and planner memory.
|
||
|
|
|
||
|
|
## Why
|
||
|
|
Blocks #758 and #820, which block the entire Adoption milestone:
|
||
|
|
- Evidence collection (predictor, planner, engagement)
|
||
|
|
- Vault lifecycle workflow (pending/approved/fired directories)
|
||
|
|
- Prerequisites.md updates (planner stuck at run 2 data since 2026-04-08)
|
||
|
|
- RESOURCES.md creation
|
||
|
|
- Engagement data persistence (#982)
|
||
|
|
Waiting since 2026-04-08 (first identified in planner run 2).
|
||
|
|
|
||
|
|
## Human action
|
||
|
|
1. Go to Forgejo admin: disinto-ops repo → Settings → Branches → Branch protection
|
||
|
|
2. Either remove branch protection on main, OR add planner-bot/gardener-bot/predictor-bot to the whitelist
|
||
|
|
3. Verify by running: `git push` from the planner container (or confirm agents can write via API)
|
||
|
|
|
||
|
|
## Factory will then
|
||
|
|
- #820: re-seed ops repo directories (evidence/, vault/pending/, vault/approved/, vault/fired/, vault/rejected/, portfolio.md, RESOURCES.md)
|
||
|
|
- Planner will resume updating prerequisites.md each run
|
||
|
|
- Engagement evidence will persist (#982)
|
||
|
|
- Vault PR workflow will become operational
|
||
|
|
|
||
|
|
## Unblocks
|
||
|
|
- #758 — ops repo branch protection blocks all agent writes
|
||
|
|
- #820 — re-seed ops repo directories
|
||
|
|
- #982 — collect-engagement.sh data loss
|
||
|
|
- #426 — website observability (downstream)
|