A box could send 300 new invented app names in every report and the
household's presence rows grew with no end.
- At most 400 names per household. A new name above that takes the place of
the oldest ABSENT name the same report does not claim; when there is none it
is not stored. Said once in the hub's log, not per report.
- A name is stored only when it is shaped like an app name (64 characters,
letters, digits, . _ -) and is not reserved (_shares, the marker, the box's
infrastructure stacks) — from the app list and from an end record alike.
The same check decides what a window may agree to.
- No age limit on a row, on purpose: an aged-out row would start a real ended
app's 30 days again. Making room never makes an app eligible earlier.
Tests TestD72_AppRecord_* (a box that sends new names in 40 reports);
10 mutations seen red, 2 after a redo.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
Built, not deployed. `07-backup-architecture.md` §8.2f parts 3-4 and decision 309.
- store: the hub's own record of which apps a box runs, by the hub's clock
(offsite_app_presence, fed by every controller report); it goes with the household.
- offsitekeys: window-open takes the box's due end records and answers
ended_allowed / ended_refused. An app is agreed only after 30 days of absence
in the hub's record; an id only when the hub's own listing holds it, uploaded
before that absence. The cap (max_remove) is unchanged; the close keeps only
agreed ids from removed_for_ended_apps and allows them beside the cap.
- The 07:10 audit explains the ended apps' vanished files by name and still
raises for every other vanished file.
- notify: offsite_end_scheduled is a household receipt — one mail per press to
the household's own address, whatever its switches; the operator is not mailed.
- Two operator-only hub records: offsite_ended_app_removed (info),
offsite_ended_app_refused (warning).
Tests TestD72_*, TestD84_*; 44 mutations seen red, 5 after a redo
(documentation/audits/build-release-4-2026-11-15/A/redproof-hub-*.txt).
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
A hub daily check skipped while the hub was down; an operator mail that was never sent; a signed job a box did not
take; a signed job a box refused, and the guest-power watchdog's give-up (both from the agent). Operator-only.
No new table. Not deployed.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
The host report's new sent_at (the box clock at the moment of sending) is compared with the hub's clock at arrival.
Both directions; told once; clears within 30 s. A report that waited on the box raises nothing (reported_at is not
read). A second box off in the same direction points at the hub's own clock. Operator-only. Not deployed.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
host_disk_warning and host_disk_critical join the operator-only register, so a
household that already has the type saved gets no mail. The type leaves the
claim seed list. storage_fill_* is split by storage kind: a drive the household
can free (usb, local-dir, nfs, cifs) still reaches the household; the thin pool,
a PBS store, an unknown kind and a missing kind go to the operator only.
Tests: TestD68_HostDiskIsOperatorOnly_EvenWhenTheHouseholdSavedIt,
TestD68_StorageFillReachesAHouseholdOnlyForADriveItCanFree,
TestD68_RegisterAndGate, TestD68_SeedHoldsNoOperatorOnlyType. Red seen three
times (register lines out; gate reading the register only; type back in the seed).
No hub build, no deploy. Also: dated lines on R-1368 and R-1371 for the agent
(776025c8) and controller (844f19f1) commits, and the filesystem-identity
measurement the controller commit cites.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
The host layer's reboot-needed run is cut at the host's last boot (crash guard
last_boot_at, one minute skew margin): the kernel step's reboot is reported on the
kernel layer, so the flag outlived it until the next night. Feeds the System page
and the 14-day alarm. Test TestRebootNeeded_ClearedByAHostBootAfterTheClaim, red on
two mutants.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
Tests red before the fix: TestR1255_TheCarryTakesTheNewestPackageThatHasAHash,
TestR1255_APurgeNeverDeletesAPackageAReusedPathStillNeeds, TestR1255_TwoSetAsidesOnOneDayGetTwoNames.
Commit only; rides the next hub release.
The Backup card's off-site part shows the window state (weekly switch, the normal cap, a waiting grant, the last
window) and a form: optional limit -> a confirm step that names the customer and the limit -> the SAME route and
rule as the script address (POST /offsite/window-grant/<customer>, wr(grpOffsite), the page's CSRF). A waiting grant
can be cancelled. A raised limit above the store's measured snapshot count is refused (the 500 ceiling stays). Every
grant and cancel: a log line and an operator-only info event offsite_window_grant (who, customer, limit).
Tests TestR1299_* (five), red-proved by five mutations.
SaveHostEscrowWithIdentity refuses (ErrEscrowWouldDropRepoKey); the PUT answers 409. Red-proved (store: superseded=true;
API: 500). Two older tests pinned the old demotion and are updated. Commit only.
app_held / app_hold_cleared allow-listed and operator-only; handleEvent mirrors them in held_apps; HeldAppsChecker
sends ONE app_held_reminder (warning, operator-only, per-app cooldown) after the grace per reason (6 h / 1 d / 3 d),
then weekly; recorded before sending; stale rows not reminded; the hub never clears a hold. Test-only
alerting.held_app_grace_override. TestD53_* in api/monitor/notify/web, red-proved by six mutations. Commit only.
app_unexplained_upload / app_unexplained_cpu (warning) and their _cleared (info), from controller v0.342.0 (08 section 9,
operator ruling 2026-10-23). Red-proved: operator-only, the render line, the allow-list.
The Cloudflare tunnel token, Cloudflare API token and git token inside customer_configs.config_json now hold the
05 §16.2 seal (enc:v1:, OFFSITE_SECRET_KEY). Old rows sealed once at start-up without a config_version bump, then
VACUUM + WAL checkpoint (an UPDATE leaves the old plaintext in a freed block). -unseal-box-secrets opens them too.
Eight tests, each red-proved. Built, not deployed. Audit: documentation/audits/hub-token-seal-2026-10-23/.