**The skill a scheduled run follows was telling it to do impossible things.**
`.claude/skills/newsroom-run/SKILL.md` said `git pull origin main` and `git push origin main` —
and this repository has no `main`; the release branch, which is also the default branch, is
`dev`. And it said to run `node build/validate.js`, which does not exist: the validator is in
`admin/build/`. A scheduled run would have died on the first line of the first step.

**And the record it told the run to write was not the one the gates read.** The field names were
all wrong — `inicio`, `issues_movidas`, `ficheiros_por_pasta`, `portas` — where gates 12 and 26
read `quando`, `issues_movidos`, `pastas_alteradas` and `portoes`. The run would have produced a
record the department boundary cannot check, and since gate 26 it would fail outright for
declaring neither a department nor a species.

**And the build sequence had six steps where there are now eleven.** It becomes `python3
build/tudo.py`, which is the real order and the only one that cannot go stale without something
failing. The publish step now fetches `dev` before choosing a version number, because another
session may be working here at the same time, and two picking the same number means one has to
undo its release.