rdmbair15m5-changelog-20260902-2106-replicantdb-1-19-0-build34-fleet-test-rollout
ReplicantDB 1.19.0 build 34 replaced the older active installation on rdmbair15m5, launched successfully, preserved the prior unloaded-daemon state and old artifacts for rollback, and passed independent acceptance.
Scope and provenance
- Host:
rdmbair15m5(macOS 27.0, arm64); designated first canary; operatorcodex@rdmsm4x; ticketTASK-20260902-11. - Candidate: isolated source commit
bf4d455a3009a66d93116dff266d7d47b6d2e098; archive SHA-256450420cb8632164e68b3b547e3f81a5c28756ec967529622944f8a868621b977. - Active paths changed:
/Applications/ReplicantDB.app,/Users/richh/bin/replicantdb-cli, and/Users/richh/bin/replicantdb-mcp. - The existing daemon remained unloaded; no daemon was newly registered or started. Final GUI PID was 88383 at the 21:00 EDT acceptance capture.
- Prior artifacts and state:
/Users/richh/Library/Application Support/ReplicantDB Rollbacks/replicantdb-1.19.0-build34-20260902-204931. - Transaction/rollback script:
/Users/richh/Library/Caches/com.eastcoastscience.ReplicantDBDeployment/replicantdb-1.19.0-build34-20260902-204931/replicantdb-host-rollout.zsh.
Verification and recovery evidence
- Exact accepted hashes: app
637c70818381488348d1a78d4ad4bed04386ee3ed1e6957bafed120f568e62a1; CLI05875904208fed74bc8c06339a2c85b583ae8425231693e1b182df74bacfbf4c; MCP7c52b3d36e950d7a94ce2cf43f9b3754e33413e68279ce7f76bfe5b4e8e8d509. - Strict signing, Team
ZU2882L4HT, unchanged designated-requirement SHA-25629f8e26d69cd51f7bd136c16321acefc18b1bf5c62d3a1817c59691a516d84e7, and both architecture slices passed. - Executed CLI version, parsed MCP initialize version 1.19.0, and required a live process from the new app executable.
- Read-only database count with
PRAGMA query_only=ON: 3,875,125 rows; no content or indexed paths were recorded. - The first canary attempt could not enter the Aqua audit session
through
launchctl asuser; automatic rollback restored 1.16.1 and the unloaded-daemon state. A fresh transaction using LaunchServices succeeded. That failed attempt made no unrecoverable change.
Undo
"$HOME/Library/Caches/com.eastcoastscience.ReplicantDBDeployment/replicantdb-1.19.0-build34-20260902-204931/replicantdb-host-rollout.zsh" rollback replicantdb-1.19.0-build34-20260902-204931Outstanding gates
- This canary was selected because of a prior 32-hour memory-growth report; deployment and a point RSS reading do not close that issue.
- No scan, OCR, classification, tagging, deduplication, file move, live-database mutation, TCC change, or CloudKit operation ran.
cloudKitProvisionedremains false; the Apple Development-signed build is for private fleet testing only.