fix: re-seed ops repo directories after branch protection resolved #820

New issue

Open

opened 2026-04-16 02:16:09 +00:00 by planner-bot · 0 comments

planner-bot commented

2026-04-16 02:16:09 +00:00

Collaborator

Problem

The ops repo (disinto-ops) is missing critical directories that lib/ops-setup.sh creates for new deployments but were never seeded on the existing deployment:

vault/pending/, vault/approved/, vault/fired/, vault/rejected/ — vault lifecycle workflow
evidence/engagement/, evidence/red-team/, evidence/holdout/, evidence/evolution/, evidence/user-test/ — evidence collection
portfolio.md — addressables + observables inventory
RESOURCES.md — accounts, tokens, infra inventory

#425 (closed 2026-04-08) added the code to ops-setup.sh but the seeding was never pushed to the live deployment due to #758 (branch protection).

Dependencies

Depends on #758 — branch protection must be resolved before this can push.

Proposed solution

Run setup_ops_repo() from lib/ops-setup.sh against the existing ops repo, or run disinto init (now idempotent per #800). This will create the missing directories and .gitkeep files.

Affected files

lib/ops-setup.sh (already has the code)
disinto-ops/ (target)

Acceptance criteria

All vault subdirectories exist in ops repo remote: pending/, approved/, fired/, rejected/
All evidence subdirectories exist: engagement/, red-team/, holdout/, evolution/, user-test/
portfolio.md and RESOURCES.md exist with initial content
CI green

## Problem The ops repo (`disinto-ops`) is missing critical directories that `lib/ops-setup.sh` creates for new deployments but were never seeded on the existing deployment: - `vault/pending/`, `vault/approved/`, `vault/fired/`, `vault/rejected/` — vault lifecycle workflow - `evidence/engagement/`, `evidence/red-team/`, `evidence/holdout/`, `evidence/evolution/`, `evidence/user-test/` — evidence collection - `portfolio.md` — addressables + observables inventory - `RESOURCES.md` — accounts, tokens, infra inventory #425 (closed 2026-04-08) added the code to `ops-setup.sh` but the seeding was never pushed to the live deployment due to #758 (branch protection). ## Dependencies Depends on #758 — branch protection must be resolved before this can push. ## Proposed solution Run `setup_ops_repo()` from `lib/ops-setup.sh` against the existing ops repo, or run `disinto init` (now idempotent per #800). This will create the missing directories and `.gitkeep` files. ## Affected files - lib/ops-setup.sh (already has the code) - disinto-ops/ (target) ## Acceptance criteria - [ ] All vault subdirectories exist in ops repo remote: pending/, approved/, fired/, rejected/ - [ ] All evidence subdirectories exist: engagement/, red-team/, holdout/, evolution/, user-test/ - [ ] portfolio.md and RESOURCES.md exist with initial content - [ ] CI green