# D1 — R-689, agent v0.135.0 → v0.137.0

Instead of waiting 6 h for the scheduled cycle, the scheduler's own read-only verdict (`felhom-agent
-selftest=restore-test-due`, the daemon's construction path) was read on demo-hp after each release.

| release | what the verdict showed on demo-hp | file |
|---|---|---|
| 0.135.0 (`d4be12c`) — only `vzdump-<type>-<vmid>` / PBS `ct/…` or `vm/…` with a vmid | the golden SKIPPED; the local pick fell to `vzdump-lxc-9100-2026_08_21…`, a guest deleted in August | `D1-selftest-due-demo-hp.txt` |
| 0.136.0 (`16dbc83`) — the guest must exist (`GuestConfig`) | PVE answered **403 permission denied** (9100 is outside the agent's pool), read as a failure → local tier UNKNOWN | `D1-selftest-due-after-0136.txt` |
| 0.137.0 (`3ef095f`) — 403 = not a guest this agent manages | both leftovers skipped; off-site tier due on 9201; local tier waits for today's 9201 archive to settle (~04:43 tomorrow) | `D1-selftest-due-0137-pre.txt` (pre-release binary), `D1-selftest-due-after-0137.txt` |

Red-proofs: `RP-r689-golden-picked.txt`, `RP-r689-deleted-guest.txt`, `RP-r689-acl.txt`. Each released by
`scripts/release-agent.sh`, NOT vouched, and signed-delivered to both hosts (`D1-signed-delivery.txt`). Not observed: an
actual scheduled restore-test run (read-only verdicts only).