ReplicantDB 1.19.0 build 34 replaced the older active installation on jdmbair13m5, launched successfully, preserved the prior unloaded-daemon state, and retained the old installation for rollback.

Scope and provenance

• Host: jdmbair13m5 (observed macOS 27.0, arm64); operator codex@rdmsm4x; ticket TASK-20260902-11.
• Candidate source commit bf4d455a3009a66d93116dff266d7d47b6d2e098; archive SHA-256 450420cb8632164e68b3b547e3f81a5c28756ec967529622944f8a868621b977.
• Active paths changed: /Applications/ReplicantDB.app, /Users/richh/bin/replicantdb-cli, and /Users/richh/bin/replicantdb-mcp.
• Existing daemon remained unloaded; no daemon registration was added. Final GUI PID was 50988 at the 21:00 EDT capture.
• Prior artifacts/state: /Users/richh/Library/Application Support/ReplicantDB Rollbacks/replicantdb-1.19.0-build34-20260902-205443.

Verification

• Exact app/CLI/MCP SHA-256 values: 637c70818381488348d1a78d4ad4bed04386ee3ed1e6957bafed120f568e62a1, 05875904208fed74bc8c06339a2c85b583ae8425231693e1b182df74bacfbf4c, 7c52b3d36e950d7a94ce2cf43f9b3754e33413e68279ce7f76bfe5b4e8e8d509.
• Strict signing, Team ZU2882L4HT, unchanged designated requirement, and universal2 slices passed.
• Executed CLI version and parsed MCP initialize response both reported 1.19.0; the new GUI process was live.
• Read-only database count under PRAGMA query_only=ON: 0 rows; no indexed paths or content were recorded.

Undo

"$HOME/Library/Caches/com.eastcoastscience.ReplicantDBDeployment/replicantdb-1.19.0-build34-20260902-205443/replicantdb-host-rollout.zsh" rollback replicantdb-1.19.0-build34-20260902-205443

Outstanding gates

• No useful-work or corpus-completeness claim follows from a successful launch or a zero-row index.
• No data mutation, scan, OCR, tagging, deduplication, file move, TCC change, or CloudKit action ran.
• The build remains private Apple Development-signed fleet-test software; cloudKitProvisioned is false.