Prepared a verified, signed ReplicantDB next-build candidate in an isolated worktree so the lead can integrate substantial UI, daemon, networking, dependency, naming, and build-system progress without touching the live corpus.

ReplicantDB next-build candidate

Scope

• Host: rdmsm4x
• Isolated worktree: /Users/richh/dev/_handoff/codex-out/replicantdb-next-build-integration-20260902
• Branch: codex/replicantdb-next-build-integration-20260902
• Final commit: bf4d455
• Canonical checkout: not modified
• Installed app and live database: not replaced or mutated
• Live daemon: not restarted; installed daemon process remained running at final verification

Changes

• Integrated four persisted, functional ReplicantDB workbench layouts: Corpus Atlas, Live Operations, Placement Planner, and Evidence Desk.
• Renamed visible app/product/module/artifact branding to ReplicantDB; preserved lowercase compatibility identifiers that back existing state and OS registrations.
• Renamed the checked-in transport archive to dist/ReplicantDB-app.tgz; it contains ReplicantDB.app/.
• Linked and execution-verified all 12 public products currently exported by canonical ecs0lib at commit 90c3c6ddd6377be6012617d1934a5fbce5c028aa.
• Fixed event-batch work amplification that caused the indexing daemon to appear crashed on large FSEvents backlogs.
• Fixed concurrent LAN connection creation corrupting shared connection/framing state.
• Hardened CLI and MCP mutation boundaries; MCP mutations require exact opt-in.
• Added alternate-database runtime and lock isolation for safe candidate testing beside the installed app.
• Corrected Local Network permission state and settings guidance; the app no longer equates an unknowable state with denial or claims an accepted URL proves the subpane opened.
• Hardened build.sh around exact certificate identity, universal2 output, Cascade Lake compiler evidence, App Intents metadata, current icon, optional provisioned CloudKit signing, and a machine-readable build manifest.

Files touched

• .gitignore, Package.swift, build.sh, scripts/verify_build_contract.zsh
• SESSION-STATE.md, ISSUES.md
• Sources/ReplicantDBCLI/ReplicantDBCLI.swift
• Sources/ReplicantDBCore/{Database,LANPeerDiscoveryService,PermissionsProbe,SingleInstanceGuard,StatusReport}.swift
• Sources/ReplicantDBDaemon/{DaemonService,ThermalGovernor}.swift
• Sources/ReplicantDBMCP/main.swift
• Sources/ReplicantDBMobile/MobileCloudStatus.swift
• Sources/replicantDB/{DaemonMode,ReplicantDBApp}.swift
• Eight focused test files under Tests/ReplicantDBTests/
• dist/ReplicantDB-app.tgz, dist/ReplicantDB.build.json, dist/replicantdb-cli, dist/replicantdb-mcp
• Earlier commits on the same branch add the workbench, daemon regression test, shared-foundation witness, and command mutation-safety tests.

Commands and verification

• swift test --scratch-path .build/final-test --skip-build
  • Result: 1,091 tests, 0 failures in 79.028 seconds.
  • Log: dist/build-logs/final-swift-test.log
  • Log SHA-256: e01fd4365d50d2e31bd32307a158d928ec6f754d7d3dc51e414cec0f6a611f4f
• ./build.sh
  • Result: signed universal2 app, CLI, and MCP; build contract passed.
• scripts/verify_build_contract.zsh
  • Result: all 12 ecs0lib products adopted, linkage witness executed, app/CLI/MCP universal2, Cascade Lake build request present, branding/icon/Info.plist correct, MCP default read-only behavior exercised, signing identity exact, archive root correct.
• codesign --verify --deep --strict --verbose=2 dist/ReplicantDB.app
  • Result: valid on disk and satisfies designated requirement.
• lipo -archs on app, CLI, and MCP
  • Result: x86_64 arm64 for all three.
• Signing certificate observed:
  • SHA-1 560BC359BA396F1B2A9F2CC1B2012AB2A14CEC96
  • Team ZU2882L4HT
  • Organization east coast science, llc
• GUI acceptance:
  • Launched the signed bundle against .build/ui-acceptance-20260902/replicantdb-ui.sqlite.
  • Verified 109 indexed/hashed/classified fixture files and all four workbench modes through accessibility inspection.
  • Exercised Local Network routing and confirmed the explicit manual navigation guidance.
  • Screenshots: .build/ui-acceptance-20260902/screenshots/01-corpus-atlas-light.png through 05-permissions-local-network-guidance-light.png.
• macOS 26.7 read-only compatibility check:
  • Queried the Privacy & Security extension on rdmpw3265m and rdmpw3275m; both export com.apple.settings.PrivacySecurity.extension.privacy-localnetwork, matching macOS 27.

Backups and undo

• No live files were overwritten, so no live rollback was required.
• Discard the isolated branch/worktree to undo the candidate before integration.
• After integration, revert commit bf4d455 plus the seven preceding candidate commits as a group if rollback is required; do not copy individual generated binaries back over a running process.
• Existing remote backup/main and the canonical checkout remain the pre-candidate baseline.

Outstanding owner/lead actions

• Review and integrate the complete eight-commit branch; do not copy loose files from the worktree.
• Create/download a matching macOS development provisioning profile at provisioning/ReplicantDB-dev.provisionprofile before enabling the existing restricted CloudKit entitlements. The current manifest honestly records cloudKitProvisioned: false.
• Resolve the observed macOS 27 NSTableView reentrant-delegate warning before production rollout.
• Treat merge, installed-app replacement, live-daemon restart, live-corpus migration, and fleet deployment as separate gated steps with independent verification.
• Handoff message: fleet bus ID 20260902-182824-EC0DED9B, addressed to claude@rdmsm4x and codex@rdmsm4x.