pastilhasandClaude Opus 5
7fc25ae53f
Carries the SQL, because bun db:push cannot apply this one and will not say so: dropping provisioning_script while adding two columns makes drizzle-kit ask whether it is a rename, and with no terminal it bails while the wrapper exits 0. Tested against a scratch database — applies, re-applies cleanly once the column is already gone, and refuses to drop a provisioning_script anything actually wrote. Also carries a one-off cleanup that no plan format covers. alpha, fofos and production-pertento-bridge each hold capabilities/affordances/officerdev/gitea/, a copy from the mechanism this release removes. The gitea plugin still ships that affordance in its own directory and affordances are deliberately not de-duplicated, so without the removal the agent reads the same guidance twice. The verification step is a chat rather than a query, because the failure mode of the capability refactor is an agent that quietly knows less rather than an error. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043
deploy/
One file per release, and one report per release.
deploy/
├── 2026.08.21.01.md the plan — what to run, in order, on which hosts
└── 2026.08.21.01.report.md what actually happened, written by the commander
The plan is written by hand before the release commit. The report is written by the deploy commander afterwards and pushed back here.
A release is a tag, deploy/<version>, and nothing else triggers a deploy — not a commit message,
not a branch. A tag cannot be written into prose by accident, which a code word can and which every
document about deploying does.
What marks a release deployed is LOCAL: $OFFICER_ROOT/data/deploys/<version>.done. Not the report.
If the lock were the pushed report, a failed push would mean the release looked undeployed and the next
tick would roll it out again — and pushes here fail for unrelated reasons. So the report is an artefact,
valuable and not load-bearing.
See prompts/deploy-commander.md.