rdmsm4x-changelog-20260823-2320-roodb-rddb-ingest-and-fleet-cleanup

rooDB.app — rdDB ingest verified, external copies removed fleet-wide

Host: rdmsm4x · When: 2026-08-23 23:14–23:22 EDT · Mode: Production Project: /Users/richh/dev/apps/rooDB · Commits: f212d49, e49e54f (local main, NOT pushed) Scope: rdmsm4x + rdmbair15m5 changed; rdmbair13m5, rdmpw3265m, rdmpw3275m, jdmbair13m5 verified only.

One-line summary: every external rdDB.app copy was proved redundant against the canonical repository and then deleted, reclaiming ~2.1 GB and stopping an old-named daemon that was still writing to a divergent 1.2 GB database.

What was found

rdmbair15m5 was still running the pre-rename product. com.eastcoastscience.rdDB.daemon was registered in ~/Library/LaunchAgents and had written to ~/Library/Application Support/rdDB/rddb.sqlite at 21:52 that evening — 1,326,260,224 bytes with a live 3.5 MB WAL, 628,819 files rows against the canonical store's 627,660, on the older pre-purpose schema.
This resolves the standing P0 "pre-rename database fallback is absent". It was never lost; it was on another host and still growing.
~/dev/agy/rdDB_autoCE is a different product (Arista field-intelligence portal, own GitHub remote) that merely shares the name prefix. Not ingested, not removed.

Verification before any deletion

External copy	Check	Result
`_migration/…/rdDB-original-root` (397 MB)	git HEAD + per-file `cmp`	HEAD `8077f0d` = preserved `legacy/rddb-main`
`_backups/rdDB-full-20260823-011736.bundle`	`git log legacy/rddb-main..`	empty; `b0b4aec` is an ancestor
`.agents/` (181 files)	set comparison against the archive zip	all 181 present
`rdmbair15m5:~/dev/apps/rdDB` (511 MB)	`git status`, `git log 8077f0d..HEAD`	no untracked, modified, or unpushed
`rdmbair15m5:~/dev/apps/rooDB` (464 MB)	git HEAD	`bbcd965`, already merged by consolidation

Also restored byte-faithful copies of eight legacy documents whose markdown hard line breaks had been stripped during the earlier consolidation, and archived the dual-product rdDB/autoCE handoff.

Removed

rdmsm4x: ~/dev/apps/rdDB, ~/dev/_migration/conflicts/…/rdDB-original-root, ~/dev/_backups/rdDB-full-20260823-011736.bundle, stray ~/dev/apps/rdDB-autoCE-dashboard.html.
rdmbair15m5: ~/dev/apps/rdDB, ~/Applications/rdDB.app, ~/Library/Application Support/rdDB, and the rdDB LaunchAgent plist. The daemon was booted out first — deleting the store while it stayed registered would simply have recreated it.

Evidence after

swift test: 163 tests, 0 failures (23:20 EDT).
All five peer hosts re-checked: no rdDB directory, app bundle, plist, or launchctl job anywhere.
rooDB side intact fleet-wide: /Applications/rooDB.app on all six; per-host databases present (rdmbair15m5 1.2 GB, the other four freshly initialised).

Rollback

Repository changes: git revert e49e54f f212d49, or git checkout 4f16431. Nothing pushed.
The deleted rdDB working trees and the 1.2 GB rddb.sqlite are NOT recoverable from disk. Their content is recoverable only as source history — legacy/rddb-main and provenance/rdDB-legacy-8077f0d.bundle carry the complete git history, and artifacts/legacy/ holds the agent evidence and the pre-rename app build. The database itself was accepted as disposable on Rich's direction that per-host stores are by design and regenerating them is fine.

Outstanding owner actions

rdmbair15m5:~/dev/apps/rooDB is a superseded 464 MB checkout at bbcd965, fully contained in the canonical repo. Left in place because it is rooDB-named, not rdDB. Worth removing.
~/dev/apps/HANDOFF_RDDB_AUTOCE.md remains at the apps root for the autoCE product; a copy is archived under docs/history/legacy-rddb/.
Every other rooDB gate is unchanged: live corpus still 0 purposes and 0 duplicate groups, publication still unreviewed, app artifact still ad-hoc signed, icon still placeholder-grade.