officerdev/platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

correct the 2026.09.09.01 report: no cron moved those hosts

Browse Source 
The agent inferred auto-pull.sh had pulled alpha and fofos ahead of the rollout. It had not. alpha was
rolled by hand by the session that cut the release, before being stopped; fofos was current because it
had been deployed to all day for plugin work.

The wrong reading is kept in the text rather than deleted — a real cron, on the right machine, with the
right effect, and nothing to do with this. That is what a plausible wrong answer looks like.
This commit is contained in:
pastilhas
2026-09-09 23:32:37 +01:00
parent 9217d1faaa
commit 78896793aa
1 changed files with 17 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/2026.09.09.01.report.md
+17 -5
View File
@@ -6,11 +6,23 @@
Every target ended at `be3139f9` — the commit `deploy/2026.09.09.01` points at. `plugin_ports` was
verified **by query on each host's own database**, not inferred from `db:push` exit codes.
**Two hosts were already at the tag before the rollout touched them.** `alpha` was at `be3139f9`, not
the `19bbbab9` the plan recorded, and `fofos` was at `be3139f9` as expected. Something pulls these
checkouts between a tag being cut and the rollout reaching them — `auto-pull.sh` on a minute crontab is
the obvious candidate. Their merges were no-ops. Only `macbookpro` and `deadpool-rezio-bridge` were
genuine fast-forwards, and they are also the only two where `bun install` had work to do.
**Two hosts were already at the tag before the rollout touched them, and the cause was a person, not a
process.** `alpha` was at `be3139f9` rather than the `19bbbab9` the plan recorded, and `fofos` was at
`be3139f9`. The deploy agent inferred `auto-pull.sh` on its minute crontab; **that inference is wrong
and is corrected here** so nobody spends time hunting a mechanism that was not involved.
What actually happened: the session that cut this release also rolled `alpha` by hand before being
stopped — the release is the releaser's job and the rollout is this commander's, and that line was
crossed. `fofos` was at `master` for an unrelated reason: it had been deployed to repeatedly through
the day during work on the `fofos-website` plugin.
So their merges were no-ops. Only `macbookpro` and `deadpool-rezio-bridge` were genuine fast-forwards,
and they are also the only two where `bun install` had work to do.
The `auto-pull` reading is worth keeping visible rather than deleting, because it is exactly the shape
of a plausible wrong answer: a real cron, on the right machine, with the right effect, that had nothing
to do with this. A host being unexpectedly current is evidence of *something*, and "the obvious
candidate" is not the same as the cause.
## Per host