rdmsm4x-changelog-20260830-2235-xentropy-six-host-additive-reconciliation

Restored XEntropy's feature-rich credential tooling after a destructive source regression and deployed one exact rollback-protected artifact to the six-Mac fleet.

Scope

• Controller and canonical writer: rdmsm4x
• Installed hosts: rdmsm4x, rdmbair15m5, rdmpw3275m, rdmbair13m5, jdmbair13m5, rdmpw3265m
• Release commit: 5e34bb29c2e70edf5af4649b636e1cdc69eb695a
• Documentation checkpoint: 34c0381ffef3a7c3799837e6596a76b09a05106f
• App tree: 593a346ecdf9464837a8215d9150672f9b5d73d1
• ecs0lib commit: 6faf512aa8d341c1be396f52cc68bc8052d1d755

Files and state changed

• Canonical repository /Users/richh/dev/apps/Xentropy fast-forwarded and documented through 34c0381.
• Per-user app installed at ~/Applications/XEntropy.app on all six hosts.
• Per-user CLI installed at ~/.local/bin/xentropyctl on all six hosts.
• Project indexes updated at /Users/richh/dev/PROJECTS.md and the canonical iCloud PROJECTS.md.
• Ticket ISSUE-20260830-43 resolved under EPIC-20260830-08.
• Recovery bundle retained at /Users/richh/dev/_migration/conflicts/rdmsm4x-20260830-xentropy-additive-reconciliation/xentropy-additive-reconciliation-34c0381.bundle with SHA-256 282055fdcbeac9cd818c7162785b820d9524891da5c8d90097bca51baa7d3d39.

Commands and verification

• swift test --package-path app: 247 XCTest cases, zero failures.
• Both XEntropy and xentropyctl product builds passed.
• zsh scripts/install_xentropy_local_instance_v1.0.zsh --all: six installs passed from one canonical signed universal2 artifact.
• zsh scripts/verify_xentropy_fleet_canary_v1.0.zsh --all: six exact-artifact checks passed; unavailable=0 and failed=0.
• Every host passed strict app/CLI signing, x86_64 arm64, exact hashes, mode-0600 rollback manifest, xentropy.catalog.v2 schema 2, tyrell-light, and the expected running executable path.

Rollback

The latest retained rollback directories are:

• rdmsm4x: ~/Library/Application Support/XEntropy/DeploymentRollback/20260830-223115-5e34bb29c2e70edf5af4649b636e1cdc69eb695a
• rdmbair15m5: ~/Library/Application Support/XEntropy/DeploymentRollback/20260830-223119-5e34bb29c2e70edf5af4649b636e1cdc69eb695a
• rdmpw3275m: ~/Library/Application Support/XEntropy/DeploymentRollback/20260830-223123-5e34bb29c2e70edf5af4649b636e1cdc69eb695a
• rdmbair13m5: ~/Library/Application Support/XEntropy/DeploymentRollback/20260830-223127-5e34bb29c2e70edf5af4649b636e1cdc69eb695a
• jdmbair13m5: ~/Library/Application Support/XEntropy/DeploymentRollback/20260830-223133-5e34bb29c2e70edf5af4649b636e1cdc69eb695a
• rdmpw3265m: ~/Library/Application Support/XEntropy/DeploymentRollback/20260830-223137-5e34bb29c2e70edf5af4649b636e1cdc69eb695a

Restore the prior app and CLI only from that host's own rollback directory, then relaunch the per-user app. Do not copy a host-local authority or catalog between Macs.

Boundaries and outstanding actions

• No credential value, source authority, provider API, public listener, import, rotation, or revocation was used.
• Independent peer review remains pending and is not conflated with the proven source/runtime/deployment states.
• Apple Notes publication remains pending because this run's launchd manager is Background; the required file copy is complete.

2026-08-31 publication addendum

• After fresh fetch, origin/main had zero remote-only commits and canonical main was 91 commits ahead.
• main was pushed by fast-forward, never force-pushed.
• Publication-record checkpoint d55c546803013bc23b09ddad8e4bd365ce5152a6 was read back from refs/heads/main and matched the local commit exactly.
• The published checkpoint retains deployed app tree 593a346ecdf9464837a8215d9150672f9b5d73d1; no reinstall was needed.
• The separate backup remote was not changed.