Commit Graph

2 Commits

Author SHA1 Message Date
shitratgit[bot] 08a2f77e1e fix(health): stop Front Projection paging as critical; snapshot the replica source
Carries three gateway-worker changes that were reviewed and left uncommitted:

- Front Projection drops out of CRITICAL_COMPONENTS. A stale inbox projection
  is worth knowing about and is not worth forcing overall health critical and
  paging Joel. Health alerts were the single largest producer in the message
  stream (740 of 1083 machine messages) and the largest fallback source.
- serve.ts runs the function-health registration check at startup, so the
  assertion still runs when the durable function's own registration was lost
  while Inngest was unavailable.
- replicate-critical-db.sh freezes one source generation before hashing it.
  The builder renames critical.db atomically, so reading the live path twice
  could pair the old file's checksum with the new file's built_at.

Also lands the three investigation briefs those findings came from.
2026-07-25 13:29:19 -07:00
Joel Hooks f454962414 feat: stage critical.db replication to both NAS boxes
Generation-guarded SSH sync every 60s to three-body and maturin (local
Btrfs, atomic publish, older-generation and checksum conflicts fail
closed). Hardened read-only FTS5 shim containers staged on both hosts
(token auth, caps dropped). CLI walks flagg -> NAS-A -> NAS-B with
servedBy provenance; synthetic reads every 120s alert on failure and
recovery. 26 tests. Step stays blocked: container start needs Joel's
sudo on each NAS.
2026-07-19 22:56:01 -07:00