status reports `systemctl is-active` as the service line, and that is the strongest health signal it has — the command reads only on-disk config, by contract. But a poller can go quiet while the process stays up: measured 2026-07-30 while probing for #129, a daemon logged "[poller] launched" and never fetched a job dispatched four minutes later, while a daemon started fresh claimed that same queued task in one second. Both times it read as a label-mapping bug on the forge, which is the wrong place to look. Says so where an operator already looks when nothing is obviously wrong, and names the remedy. log, not warn: an idle-but-healthy runner is silent in exactly the same way a stalled one is, so there is no signal separating them and a warning on every run would be crying wolf. No network call and no token read — the header contract, and test/cli.sh's existing guard, both stand. Refs #133 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 109.md | ||
| 111.md | ||
| 112.md | ||
| 116.md | ||
| 133.md | ||
| 152.md | ||
| 153.md | ||
| 160.md | ||
| 162.md | ||
| README.md | ||
changelog.d/ — the next release's section, one fragment per issue
Machine-assembled by bin/changelog-assemble (#112): every PR that changes
behavior writes one file here — <issue>.md, the exact prose that will be
published, nothing else — and the release PR folds them all into the next
## X.Y.Z — DATE section of CHANGELOG.md, consuming them. Distinct
filenames never conflict, which is this directory's whole reason to exist.
This README is the marker that keeps the directory tracked when it holds no
fragments (#112 D1) — changelog-armed refuses a tree without it; do not
delete it.