Fleet changelogs · dev.ecs0.net
rdmsm4x-changelog-20260903-0659-rtty-build46-finalization

RTTy 0.3.824 Build 46 was finalized, merged, deployed, and runtime-accepted on all six Macs; older runnable copies and stale identity state were archived first and then removed, while current data and launch-at-login behavior were preserved.

RTTy Build 46 finalization

Outcome

The current Direct fleet release is RTTy 0.3.824 Build 46, bundle com.eastcoastscience.rtty.direct, minimum macOS 26.0, universal x86_64 arm64, signed by Apple Development Team ZU2882L4HT. The leading dashboard grid mark and RTTy title no longer receive the system oval/capsule; the exact installed artifact was inspected in both light and dark appearance.

The clean release source is df253735fc35af5343d94493dcdf0857ccfb155e. Normal GitHub pull-request merges landed the final record on main at ca49e7f49c4a8f8dd59637910512db01f4a1d66e. GitHub PRs 1 through 3 are closed as superseded with unique history preserved, PRs 4 through 6 merged normally, and no pull request remains open. origin/main, backup/main, and fleet/main all resolve to the same merge commit. No force push, history rewrite, or remote-branch deletion occurred.

Exact files and durable records

Commands and gates run

Verification evidence

The complete nine-gate release QA passed. Each native and Rosetta lane discovered 794 XCTest cases, ran and passed 789, documented the same five environment skips, and had zero failures. Standard structure, Direct universal build, strict signature/provenance, live latency, 102-point status width, heatmap, real throughput, and repository gates all passed.

The final accepted processes recorded by the fleet audit were:

Host PID at final audit Result
rdmsm4x 29431 accepted
rdmbair13m5 90457 accepted
rdmbair15m5 30650 accepted
rdmpw3265m 76908 accepted
rdmpw3275m 13521 accepted
jdmbair13m5 68412 accepted

Every host proved the exact executable, metadata, minimum OS, strict Team signature, both architectures, exactly one process from /Applications/RTTy.app, live command-backed ping and one-shot nettop, recent advancing SQLite evidence, exactly one current LaunchServices registration and firewall entry, and no stale counterpart or legacy RTTy launchd identity. The current RTTy Open at Login entry was deliberately retained because it is shipping behavior, not legacy authorization state.

Archive-first cleanup and backups

Each host created a checksum-verified legacy-state manifest and ZIP before cleanup. Canonical copies are under release/build46-df25373/legacy-state/<host>/. The two unique Build 1 LatencyBar applications on rdmbair15m5 and rdmpw3275m were separately sealed under release/build46-df25373/legacy-artifacts/ before removal.

Cleanup removed retired preference/TCC identities, caches and test/crash state, expanded Build 45 rollback apps, transferred installer ZIPs, stale LaunchServices/firewall entries, six simulator apps, two sealed Build 1 apps, and approximately 45.0 GB of reproducible .build, DerivedData, dist, QA, and remote scratch output. It preserved the current app, current preferences, current monitoring databases, source and Git history, immutable release and rollback ZIPs, and explicit archive/review/migration/recovery evidence. Any older artifacts still present are inert, unregistered preservation records, not live or runnable installations.

The immutable prior Direct rollback remains at release/build45-af06637/artifacts/RTTy-direct-0.3.823-build45-af06637.zip, SHA-256 cc0dcc0cbf300d200d48d90a6ad4fdede5dec1c2033d1780e998986f6f8b5103.

Undo

If Build 46 must be rolled back, first verify the retained Build 45 ZIP against the hash above, extract it into a new staging directory, stop only the current RTTy process, replace only /Applications/RTTy.app, validate the prior bundle identity, signature, architectures, and executable hash, then launch and prove fresh monitoring evidence before re-registering it. Restore retired preference or database state only from that host's matching checksum-verified legacy-state/<host> archive; do not restore another host's state or an entire archive tree blindly. Build 46 remains recoverable from its immutable Direct ZIP and complete checksum manifest.

Xcode disposition

Xcode 26.6 (17F113) is authentic and intact. Its older SwiftBuild can deadlock while sequentially draining the verbose clang discovery probe on this macOS 27 host. The authenticated exact-signature clang wrapper safely suppresses only that probe's non-semantic verbose trace, and the stable compiler/linker passed a minimal build. No global Xcode selection was changed; Xcode 27 beta 6 remains selected. The workaround is bound into the trusted structural archive lane and is not itself represented as an Apple Distribution credential.

Outstanding owner actions

The Direct fleet revision is complete. The Standard Mac App Store archive is intentionally unsigned structural evidence with releaseEligible=false. Publication still requires an Apple Distribution identity, permanent app and Network Filter App IDs, matching provisioning profiles and capabilities, a distribution-signed archive, real Network Extension enable/disable proof, final App Privacy answers, and explicit authorization to upload. No host currently runs macOS 26.0, so the 26.0 floor is proven by both-architecture builds and Mach-O load commands, not by a physical 26.0 launch.

The AppleScript helper timed out while enumerating the large iCloud Notes store, so the same record was filed through the visible rdmsm4x Notes UI in the llmlog folder. Read-only database verification found the note and all critical identity, manifest, boundary, and owner-action markers in its 40,011-byte decompressed body. Identical host-named file copies are placed on the other five Macs; their Apple Notes entries remain pending until an Aqua GUI session on each host can run the Notes helper, because SSH/background sessions cannot send AppleEvents.