pastilhasandClaude Opus 5
3343b21a17
No code change. The point is to see a tag picked up by a loop nobody is looking at, and to exercise the claim rule that landed after the last deploy. Not literally an empty commit, and it cannot be: the commander stops when the tag and package.json disagree, and stops again when the plan file is missing. So the smallest honest release is a version and a plan, which is what this is. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
2026.08.21.03 — a drill
No code change. This release exists to watch the watcher fire, and to exercise the claim rule that landed after the last one.
There is nothing to bump but the version and this file, and that is deliberate rather than lazy: a tag
whose package.json disagrees with it makes the commander stop, and a tag with no plan beside it makes it
stop too, so the smallest honest release is still a version and a plan.
What is being tested
- The watcher noticing a tag and spawning an agent on its own, with nobody watching the composer.
scripts/deploy-claim.shtaking the claim before anything is deployed, and the deploy recording success through the same script.- A second pass over the same version being refused rather than repeated.
Every host
git pull --ff-onlybun run plugins:updatepm2 restart officer
officer only. No bun install, no db:push — nothing in this range touches a schema, a dependency or
the lockfile, and git diff deploy/2026.08.21.02..HEAD is two files.
Then check
pm2 jlist: officer is online and its restart_time moved. Nothing else restarted.
scripts/deploy-claim.sh state 2026.08.21.03 says done.