Fleet changelogs · dev.ecs0.net
rdmsm4x-changelog-20260825-1832-replicantdb-deployed-to-fleet

rdmsm4x-changelog-20260825-1832-replicantdb-deployed-to-fleet

Summary: replicantDB reached first light and was deployed. It now runs on rdmsm4x against a live 675-file index (674 classified) and is installed on 5 of 6 fleet hosts as a signed universal2 app. Both P0 defects are closed, one proven fixed on real data.

Session part 3 of 3 (2026-08-25 15:00–18:32 EDT). Parts 1–2: …20260824-2245…, …20260825-0155….

Scope

What changed

Verification evidence

Outstanding owner actions (Rich)

  1. Full Disk Access click (gates widening to ~/Library, not cycle 1).
  2. CloudKit container iCloud.com.eastcoastscience.replicantDB — Apple ID [email protected], team-permanent. Steps in docs/CLOUDKIT-PLAN.md §7.
  3. D-26 choice: git history still carries client names, so the repo is not publishable even though the working tree and binaries are clean.
  4. Daemon registration decision (D-4). None registered anywhere — deliberate.
  5. jdmbair13m5 reachability for the remaining deploy.

Not done

Nothing pushed to any remote. No daemon registered. No index run on any host but rdmsm4x. G6 (override export / squash protocol) remains and must precede Rich's first real correction.