Maniacs_Mansion/MealQuest
11
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move the deployment runbook out of the repository into CTXD #137

Merged
approver_agent merged 3 commits from task/runbook-to-ctxd_e81ed994-a510-48e6-9cf6-e76d5d81f56c into feature/3a88c1fd-6c9a-4e70-b6b1-a8880dd4ac82-shopping-list-and-supply-archive 2026-10-08 10:02:41 -04:00
Conversation 2 Commits 3 Files Changed 8
+50 -1520
orchestrator-agent commented 2026-10-08 09:11:24 -04:00
Member
Copy Link
Copy Source

Task

Maestro task e81ed994-a510-48e6-9cf6-e76d5d81f56c — "Move all runbook information out of the repository and into CTXD".

Owner directive (binding, 2026-10-08)

All RUNBOOK information MUST be written in CTXD, NEVER to be placed in the repo.

The repository violated it: deploy/RUNBOOK.md (1417 lines) held the deploy, rollback, restore-the-database, restore-media, count-check, secret-rotation, Google Calendar OAuth client and troubleshooting procedures — and CTXD's own RUNBOOKS.MD pointed at that file as authoritative.

What this PR does

  • Deletes deploy/RUNBOOK.md (1417 lines) from the repository.
  • Re-points every reference: deploy/.env.example, deploy/compose.yaml and deploy/systemd/mealquest-media-backup.sh now name CTXD project mealquest, file RUNBOOKS.MD instead. AGENTS.md already listed CTXD's RUNBOOKS.MD as the runbook home and is unchanged. A case-insensitive search for "runbook" across the repo finds no reference to the deleted file and no description of the runbook as living in the repo.
  • The runbook itself is already published to CTXD by the orchestrator: CTXD project mealquest, file RUNBOOKS.MD, version 5, 715 lines, merged from the repository's procedures and CTXD's existing durable content (the Maestro per-task loop, local development, the Authentik setup with its confirmed live values, the deploy values as confirmed live, backups, and troubleshooting). The published document states that CTXD is the authoritative runbook and no longer points at the repository. Where the old CTXD text contradicted the newer repository procedure, the repository procedure stands — notably that the stack starts and stops only through the mealquest systemd unit, not docker compose up/down.

Notes

  • This is a documentation/context change: no Go, migration, dependency or web change.
  • It deliberately rides Feature 17's branch so the removal reaches dev with that feature's promotion. main still carries the old file until the next promotion; the open release PR #131 has been annotated with that.
  • The full 1482-line merged runbook remains archived as evidence at /home/overseer/.local/state/mealquest-orchestrator/evidence/ctxd-RUNBOOKS.MD; the published CTXD version is the tightened 715-line form, and the developer's notes list exactly what padding was cut (no operational fact or command).

Evidence (orchestrator-run checks at 89574333e8)

  • deploy/RUNBOOK.md is absent from the tree; the diff is 4 files, +11/−1426
  • A case-insensitive "runbook" search finds only the CTXD pointers and AGENTS.md's CTXD file list
  • Developer-reported quality floor: gofmt -l . empty, go vet ./..., go test -race -count=1 ./..., CGO_ENABLED=0 go build ./..., and cd web && npm run typecheck && npm test && npm run build all green

Implementation commit: 89574333e81ad65f03e0d4af43844d3f320049ae

## Task Maestro task `e81ed994-a510-48e6-9cf6-e76d5d81f56c` — "Move all runbook information out of the repository and into CTXD". ## Owner directive (binding, 2026-10-08) > All RUNBOOK information MUST be written in CTXD, NEVER to be placed in the repo. The repository violated it: `deploy/RUNBOOK.md` (1417 lines) held the deploy, rollback, restore-the-database, restore-media, count-check, secret-rotation, Google Calendar OAuth client and troubleshooting procedures — and CTXD's own `RUNBOOKS.MD` pointed at that file as authoritative. ## What this PR does - **Deletes `deploy/RUNBOOK.md`** (1417 lines) from the repository. - **Re-points every reference**: `deploy/.env.example`, `deploy/compose.yaml` and `deploy/systemd/mealquest-media-backup.sh` now name CTXD project `mealquest`, file `RUNBOOKS.MD` instead. `AGENTS.md` already listed CTXD's `RUNBOOKS.MD` as the runbook home and is unchanged. A case-insensitive search for "runbook" across the repo finds no reference to the deleted file and no description of the runbook as living in the repo. - **The runbook itself is already published to CTXD** by the orchestrator: CTXD project `mealquest`, file `RUNBOOKS.MD`, **version 5**, 715 lines, merged from the repository's procedures and CTXD's existing durable content (the Maestro per-task loop, local development, the Authentik setup with its confirmed live values, the deploy values as confirmed live, backups, and troubleshooting). The published document states that CTXD is the authoritative runbook and no longer points at the repository. Where the old CTXD text contradicted the newer repository procedure, the repository procedure stands — notably that the stack starts and stops only through the `mealquest` systemd unit, not `docker compose up/down`. ## Notes - This is a documentation/context change: no Go, migration, dependency or web change. - It deliberately rides Feature 17's branch so the removal reaches `dev` with that feature's promotion. `main` still carries the old file until the next promotion; the open release PR #131 has been annotated with that. - The full 1482-line merged runbook remains archived as evidence at `/home/overseer/.local/state/mealquest-orchestrator/evidence/ctxd-RUNBOOKS.MD`; the published CTXD version is the tightened 715-line form, and the developer's notes list exactly what padding was cut (no operational fact or command). ## Evidence (orchestrator-run checks at 89574333e81ad65f03e0d4af43844d3f320049ae) - `deploy/RUNBOOK.md` is absent from the tree; the diff is 4 files, +11/−1426 - A case-insensitive "runbook" search finds only the CTXD pointers and AGENTS.md's CTXD file list - Developer-reported quality floor: `gofmt -l .` empty, `go vet ./...`, `go test -race -count=1 ./...`, `CGO_ENABLED=0 go build ./...`, and `cd web && npm run typecheck && npm test && npm run build` all green Implementation commit: `89574333e81ad65f03e0d4af43844d3f320049ae`
orchestrator-agent added 1 commit 2026-10-08 09:11:25 -04:00
Move the deployment runbook out of the repository into CTXD
CI / ci (push) Successful in 4m59s
Details
CI / ci (pull_request) Successful in 4m56s
Details
89574333e8 
By owner directive (2026-10-08), all runbook information lives in the
CTXD project mealquest, file RUNBOOKS.MD, never in the repository.
Delete deploy/RUNBOOK.md, whose content is merged into that CTXD file,
and point the comments in deploy/.env.example, deploy/compose.yaml and
deploy/systemd/mealquest-media-backup.sh at RUNBOOKS.MD instead.

Maestro task e81ed994-a510-48e6-9cf6-e76d5d81f56c.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
review_agent requested changes 2026-10-08 09:14:18 -04:00
Dismissed
review_agent left a comment
Member
Copy Link
Copy Source

Independent Codex gpt-6-sol review: CHANGES_REQUIRED for this exact commit.

Independent Codex gpt-6-sol review: CHANGES_REQUIRED for this exact commit.
overseer added 1 commit 2026-10-08 09:20:47 -04:00
Replace the remaining deploy procedures with CTXD runbook pointers
CI / ci (push) Successful in 5m27s
Details
CI / ci (pull_request) Successful in 5m41s
Details
fd05d51ebf 
The repository still carried operating steps from the deleted runbook:
secret creation and permission commands in deploy/.env.example, build,
restart and restore steps in deploy/compose.yaml, a direct
"docker compose up -d" in mealquest-firewall.service, a manual run in
mealquest-media-backup.service and a dev start command in
compose.dev.yaml. Replace each with a pointer to the named section of
CTXD project mealquest, RUNBOOKS.MD, keeping every variable, path,
owner, mode, port and mount description.

Maestro task e81ed994-a510-48e6-9cf6-e76d5d81f56c.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
overseer added 1 commit 2026-10-08 09:36:29 -04:00
Point the README's developer setup at the CTXD runbook
CI / ci (push) Successful in 4m55s
Details
CI / ci (pull_request) Successful in 4m57s
Details
ccb63496de 
The Quick start procedure moves to CTXD (mealquest / RUNBOOKS.MD,
"Local development"), corrected there. It had also gone stale: it omitted
MEALQUEST_GOOGLE_CLIENT_ID and MEALQUEST_GOOGLE_CLIENT_SECRET_FILE, without
which the service refuses to start.

Task e81ed994-a510-48e6-9cf6-e76d5d81f56c.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
review_agent left a comment
Member
Copy Link
Copy Source

Independent Codex gpt-6-sol review: APPROVED for this exact commit.

Independent Codex gpt-6-sol review: APPROVED for this exact commit.
approver_agent merged commit 1a781bfdb8 into feature/3a88c1fd-6c9a-4e70-b6b1-a8880dd4ac82-shopping-list-and-supply-archive 2026-10-08 10:02:41 -04:00
Sign in to join this conversation.
Reviewers
No Reviewers
review_agent
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
approver_agent (The Approver) chatgpt claude-ai Claude-Code codex (Codex) dev_agent grok opencode orchestrator-agent overseer (Joshua) review_agent (The Reviewer)
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Maniacs_Mansion/MealQuest#137