ReplicantDB 1.19.0 build 34 replaced the older active installation on rdmsm4x, launched successfully, preserved the prior app and daemon state for rollback, and passed an independent artifact/runtime acceptance pass.

Scope

• Host: rdmsm4x (macOS 27.0, arm64).
• Operator: codex@rdmsm4x; ticket TASK-20260902-11.
• Fleet scope: this host is one of six independently accepted test deployments.
• Candidate source: isolated worktree /Users/richh/dev/_handoff/codex-out/replicantdb-next-build-integration-20260902, source commit bf4d455a3009a66d93116dff266d7d47b6d2e098.
• Archive SHA-256: 450420cb8632164e68b3b547e3f81a5c28756ec967529622944f8a868621b977.
• Deployment documentation commit: 0310483b09a2a4da2bf09c0aec50f9fc7595b9dd on the isolated branch; the dirty canonical checkout was not edited.

Local state changed

• Active app: /Applications/ReplicantDB.app, version 1.19.0 build 34, executable ReplicantDB.
• Active CLI: /Users/richh/bin/replicantdb-cli.
• Active MCP server: /Users/richh/bin/replicantdb-mcp.
• Existing daemon plist retained and repointed: /Users/richh/Library/LaunchAgents/com.eastcoastscience.replicantDB.daemon.plist.
• Existing loaded daemon state retained; final GUI PID was 38808 and daemon PID was 38780 at the 21:00 EDT acceptance capture.
• Prior active artifacts and state moved to /Users/richh/Library/Application Support/ReplicantDB Rollbacks/replicantdb-1.19.0-build34-20260902-205812.
• Host-local transaction copy retained under /Users/richh/Library/Caches/com.eastcoastscience.ReplicantDBDeployment/replicantdb-1.19.0-build34-20260902-205812/.
• Fleet milestone recorded in /Users/richh/dev/PROJECTS.md and /Users/richh/Library/Mobile Documents/com~apple~CloudDocs/Codex/projects/AGENTS.md principles/PROJECTS.md.
• Coordination completion recorded in /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-replicantdb-fleet-rollout-20260902.json; the six host-prefixed changelog files were archived in /Users/richh/dev/LLM/Claude/changelogs/ and each remote host received only its own copy.

Commands and verification

• Ran the rollback-capable host installer, which validates the immutable stage before mutation and automatically restores prestate on failed acceptance.
• Reproduced app executable SHA-256 637c70818381488348d1a78d4ad4bed04386ee3ed1e6957bafed120f568e62a1, CLI SHA-256 05875904208fed74bc8c06339a2c85b583ae8425231693e1b182df74bacfbf4c, and MCP SHA-256 7c52b3d36e950d7a94ce2cf43f9b3754e33413e68279ce7f76bfe5b4e8e8d509.
• Ran strict code-sign verification; TeamIdentifier is ZU2882L4HT, the app retains both x86_64 and arm64, and designated-requirement SHA-256 remains 29f8e26d69cd51f7bd136c16321acefc18b1bf5c62d3a1817c59691a516d84e7.
• Executed replicantdb-cli version, parsed an MCP initialize response reporting 1.19.0, required the new GUI process, and observed the daemon hold one PID for an additional 20 seconds.
• Opened the live SQLite store read-only with PRAGMA query_only=ON; count observed: 2,086,336 rows. No content or indexed paths were recorded.
• Candidate source verification before deployment: 1,091 tests, 0 failures, followed by ./build.sh.

Undo

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

Rollback removes the candidate from active paths, restores the prior app, CLI, MCP, plist, GUI state, and daemon state, and retains the failed-new artifacts for inspection.

Outstanding gates

• The point RSS readings do not close the long-duration memory-growth issue.
• A stable daemon PID does not prove useful hashing, OCR, classification, or maintenance work.
• Effective TCC permissions and CloudKit behavior were not re-probed; cloudKitProvisioned remains false.
• This is Apple Development-signed private fleet test software, not Developer ID notarized or publicly distributable.