rdmsm4x-changelog-20260823-1903-roodb-app-canonical-consolidation

Consolidated rooDB.app, formerly rdDB.app, into one canonical production project at /Users/richh/dev/apps/roodb-app so future work resumes from a single source-, history-, documentation-, and build-complete root without placing the live private database in Git.

Scope

• Host: rdmsm4x only.
• Canonical project: /Users/richh/dev/apps/roodb-app.
• Final local main HEAD: 33fb8b36b5a20b0a9394a6f03fed186965dc9ab9.
• Consolidation merge: 7ba2f217df40687da91b7813eee8803ff98a4221.
• Legacy ref: legacy/rddb-main at 8077f0d5708e9ffa810e77755c6b7ba5f1650e39.
• Remote: origin remains configured; no push, release, deployment, daemon registration, or live corpus mutation was performed.

Exact state changed

• Promoted /Users/richh/dev/apps/rooDB to /Users/richh/dev/apps/roodb-app after merging the formerly unrelated local and remote rooDB histories.
• Preserved the complete legacy rdDB Git history as legacy/rddb-main and /Users/richh/dev/apps/roodb-app/provenance/rdDB-legacy-8077f0d.bundle.
• Preserved the pre-consolidation rooDB local and remote refs in /Users/richh/dev/apps/roodb-app/provenance/rooDB-pre-consolidation-bbcd965.bundle.
• Added the project entrypoints /Users/richh/dev/apps/roodb-app/README.md, AGENTS.md, MANIFEST.md, SESSION-STATE.md, ISSUES.md, and RESUME.md.
• Added curated project evidence under /Users/richh/dev/apps/roodb-app/docs/history/, runtime boundaries under /Users/richh/dev/apps/roodb-app/runtime/, build archives under /Users/richh/dev/apps/roodb-app/artifacts/builds/, and legacy archives under /Users/richh/dev/apps/roodb-app/artifacts/legacy/.
• Produced fresh local products at /Users/richh/dev/apps/roodb-app/dist/rooDB.app, /Users/richh/dev/apps/roodb-app/dist/roodb-cli, and /Users/richh/dev/apps/roodb-app/dist/roodb-mcp.
• Replaced the former-name roots with pointer-only records at /Users/richh/dev/apps/rooDB/README-MOVED.md and /Users/richh/dev/apps/rdDB/README-MOVED.md.
• Updated /Users/richh/dev/data/products.json, regenerated /Users/richh/dev/fleet/PROJECTS.md, updated the hard-linked /Users/richh/dev/PROJECTS.md and /Users/richh/dev/projects.md, and updated /Users/richh/Library/Mobile Documents/com~apple~CloudDocs/Codex/projects/AGENTS.md principles/PROJECTS.md.
• Updated coordination state at /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-roodb-app-consolidation-20260823.json.

Preserved recovery material

• Untouched original pre-rename root: /Users/richh/dev/_migration/conflicts/rdmsm4x-roodb-consolidation-20260823/rdDB-original-root.
• Pre-consolidation rooDB untracked files: /Users/richh/dev/_migration/conflicts/rdmsm4x-roodb-consolidation-20260823/rooDB-untracked-before-merge/.
• Pre-consolidation rooDB app: /Users/richh/dev/_migration/conflicts/rdmsm4x-roodb-consolidation-20260823/rooDB-build-before-consolidation/rooDB.app.
• Older legacy bundle retained independently at /Users/richh/dev/_backups/rdDB-full-20260823-011736.bundle.
• Live private database left in place and not copied to Git: /Users/richh/Library/Application Support/rooDB/roodb.sqlite.

Commands and verification

• Inspected Git roots, branches, worktrees, remotes, refs, dirty/untracked files, historical bundles, old builds, and fleet coordination traffic before writing.
• Created an isolated linked worktree and consolidation branch; fetched origin, merged origin/main with unrelated-history retention, imported the legacy rdDB ref, verified bundles, committed the consolidated state, fast-forwarded local main, and removed the temporary worktree.
• Ran swift test before consolidation and again from the final canonical root. Final result: 163 tests executed, 0 failures, 0 unexpected failures.
• Ran ./build.sh; verified all three products are arm64. codesign --verify --deep --strict dist/rooDB.app and plutil -lint dist/rooDB.app/Contents/Info.plist passed. The app is ad-hoc signed and is not a release candidate.
• Verified all four ZIP archives with unzip -t and both provenance bundles with git bundle verify.
• Ran git diff --check and git fsck --full; object connectivity completed, with only unreachable objects from prior local history operations reported by fsck.
• Ran gitleaks dir and gitleaks git with redaction; neither found a leak.
• Re-read the live database with sqlite3 -readonly: PRAGMA integrity_check returned ok; the database remained 1,225,965,568 bytes with SHA-256 dfd5e6283f074428240aa2c942266c6ede1f3a8420e752141208e261ff5a49ed.
• Live counts at the gate: 627,660 files, 627,660 FTS rows, 87,396 hashes, 0 duplicate groups, 54 classification rules, 16,303 populated cat_l1, and 0 populated purpose; badges were 627,657 CANDIDATE, 2 VERIFIED, and 1 INFERRED.
• No exact rooDB executable process was active during the state captures.

Undo

1. Stop before undoing if another task has begun writing /Users/richh/dev/apps/roodb-app; inventory and preserve its new commits and dirty files first.
2. Move the pointer-only /Users/richh/dev/apps/rooDB and /Users/richh/dev/apps/rdDB directories aside to a new recovery location.
3. Move /Users/richh/dev/_migration/conflicts/rdmsm4x-roodb-consolidation-20260823/rdDB-original-root back to /Users/richh/dev/apps/rdDB if the untouched pre-rename root is required.
4. Reconstruct the pre-consolidation rooDB checkout from /Users/richh/dev/apps/roodb-app/provenance/rooDB-pre-consolidation-bbcd965.bundle at bbcd96503a2a017352c0aeca178da238e81b7a29, or retain the canonical project and reset only a new isolated worktree to that ref.
5. Restore the previous registry paths only after the selected checkout is verified. The live Application Support database needs no rollback because it was not mutated.

Outstanding owner actions and gates

• Establish and verify a recoverable backup of the current 1.23 GB roodb.sqlite outside Git before any live database mutation or resumed processing.
• The historical /Users/richh/Library/Application Support/rdDB/rddb.sqlite fallback was not found and must not be claimed as present.
• Resume live hashing, taxonomy, purpose classification, and duplicate-group materialization only in bounded, observable batches after the backup gate.
• Keep APFS deduplication in dry-run mode unless a separate explicit task authorizes real-file mutation.
• Review the unified history, remote destination, and branch protections before pushing the four local-main commits absent from origin/main.
• Perform Developer ID signing/notarization and fleet canary validation before treating dist/rooDB.app as a release candidate.