admin
da20722e76
gates / gates (push) Successful in 27s
INTERIM CHECKPOINT — evidence off the machine at the end of the phase that produced it (R-320), not at the end of the session. Phases 2-5 follow in a later commit. Phase 0, all three mechanisms proven with their controls: - the fleet floor to 0.261.0 with its declared MinAgent — both demo boxes in 13 s, the hub logging `managed floor SERVED ... from declared (golden 0.258.0)`. - a PRIVATE DRILL CATALOG (admin/app-catalog-drill), so that broken, dummy, cross-repo and engine-major edges can be measured without the live catalog ever carrying one. Positive control quoted, and two negative controls: the live catalog's main and both real boxes' caches unchanged. - a throwaway image store on the scratch guest, which is what makes an UNATTENDED HOLD measurable at all: an edge that PASSES the within-a-major test and still fails. CompareImageRefs was proven to order host:port/ references by RUNNING it (4 positive cases + 1 negative control), not by reading it. Phase 1: real within-a-major upstream edges walked on guest 9202 through the product's own guarded Update, each app seeded and read back through its OWN front door (R-156), with a per-edge verdict record in 09's shape. `inconclusive` is never collapsed into `failed`. TWO INSTRUMENT FIXES, both in this repo's own evidence code: - 00-api-recipe.md said the app page is /app/<n>; it is /apps/<n>, and every call it described 404s. Corrected, with the session-expiry note that cost the same time. - unattended-caller.py's follow() read update_phase/updating off the API ENVELOPE, so both were always None and EVERY followed update ran to its 900 s timeout and was then recorded `timeout` and never-press-again. Fixed before B1 relied on it. R-623. No controller, agent or hub code was written. The live catalog carries no broken reference. Gates: repo_gates.py --fast — all 15 OK, exit 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
22 lines
1.2 KiB
Plaintext
22 lines
1.2 KiB
Plaintext
=== 9202 notifier state, 2026-09-21 — why the event/mail half is unmeasurable here
|
|
|
|
controller.yaml hub block on guest 9202:
|
|
hub: { api_key: "", enabled: false, push_interval: 15m, url: "" }
|
|
|
|
the box says so once, at startup, and never again:
|
|
notifier.go:75 [INFO] Notifier disabled (hub not configured)
|
|
main.go:642 [INFO] [mailrelay] app-email shim unavailable (no hub configured or disabled in config)
|
|
selftest.go:68 [INFO] [PASS] Hub connectivity: hub disabled, skipped
|
|
|
|
and every event path returns BEFORE it logs anything:
|
|
notify/notifier.go:269 Publish -> if !n.enabled { return }
|
|
notify/notifier.go:359 NotifyHealthChange -> if !n.enabled { return }
|
|
notify/notifier.go:867 SyncPreferences -> refuses with a message (the one that does speak)
|
|
notify/notifier.go:917, :959, :1058 the remaining entry points, all silent
|
|
|
|
CONSEQUENCE FOR TONIGHT, stated rather than worked around:
|
|
the alarm truth table covers the app page, the dashboard and the controller log ONLY.
|
|
no hub event and no customer mail could be produced or observed on this venue.
|
|
the hub was NOT enabled on 9202 to get around this: that would register an unclaimed
|
|
host at the live hub and could mail a real address, and the brief fences the hub.
|