rdmsm4x-changelog-20260910-1839-rtty-506-uploaded-to-app-store-connect-codex-fixes-merged

2026-09-10 18:39:40 EDT · rdmsm4x · claude@rdmsm4x (Fable 5.1, oversight) · session 742a212e

RTTy 0.3.831 Build 506 is uploaded to App Store Connect and shows Ready to Submit (macOS, TestFlight); the Codex fixes (full legend, cloud settings preview, per-device CloudKit records) and the export-compliance declaration are merged to main for build 507; a jumbo-frame MTU blackhole that hung the upload is worked around with a scoped route.

Scope

rdmsm4x only (App Store Connect portal work, hub repo merges, one non-persistent route). No other host touched.

What changed

• App Store Connect ([email protected], team ZU2882L4HT):
  • API key "rdmsm4x uploader", role App Manager, Key ID NQ3TQ2BF6J, Issuer ID 4440fead-03c3-41c3-9aeb-76ab616b192d. Private key at ~/.private_keys/AuthKey_NQ3TQ2BF6J.p8 (mode 600). Names ASC_KEY_ID / ASC_ISSUER_ID / ASC_KEY_PATH recorded in ~/.secrets/global.env (values of the .p8 never written anywhere else).
  • App record RTTy, Apple ID 6810851036, platforms iOS + macOS, bundle com.eastcoastscience.rtty, SKU rtty-2026, company name "east coast science, llc" (permanent seller name; DEC-20260910-02). The "user access" save failed harmlessly: every team user can see the app.
  • altool --validate-app: VERIFY SUCCEEDED 18:13:40 EDT. altool --upload-app: UPLOAD SUCCEEDED 18:32:47 EDT (13,844,179 bytes in 4.9 s). Package ~/dev/_handoff/rtty-appstore-506-20260910/RTTy.pkg sha256 1516165a39c942477593af7c0a73e06098644142d1a6ff38731b0d081d0fa01a.
  • Export compliance for build 506 answered "None of the algorithms mentioned above" (RTTy only uses Apple-OS encryption: Network.framework TLS, CloudKit, CryptoKit SHA-256/HMAC). Build status: Ready to Submit, expires in 90 days.
• Route (non-persistent): sudo route add -net 17.156.104.0/24 192.168.1.1 -mtu 1500. Reason: en0 runs MTU 9000 and TLS to Apple's object storage never completed (two uploads hung 12+ min on a 188 KB part, 50 % TCP retransmit; curl reproduced; en1 at MTU 1500 answered in 0.1 s). Filed ISSUE-20260910-09 (fleet ticket + fleet/ISSUES.md). Undo: sudo route delete -net 17.156.104.0/24; it also vanishes on reboot.
• richhdoty/RTTy main:
  • PR #50 (8a44379) — Codex fixes from ~/dev/_handoff/rtty-codex-fixes-20260910: X001 full flow legend, X002 "Preview Saved Settings", ISSUE-20260910-08 one private RTTyFleetProjection record per device. Verified on the hub: RTTyTests 883 / 0 failures (5 skipped), LatencyCoreTests 270, RTTyMobileCoreTests 7 (PerDeviceCloudProjectionTests 4), Standard allowlist closure PASS. ISSUE-20260910-08 resolved in the ticket store.
  • PR #51 (05094fe) — ITSAppUsesNonExemptEncryption=false in script/build_and_run.sh and Apps/RTTyMobile/App/Info.plist; app_store_privacy_contract_test.sh and release_metadata_test.sh PASS.
  • Stray PR #2 opened by mistake on the backup mirror (rdmsm4x-dev-apps-rtty) was closed.
• Icon: Rich's ~/Desktop/download-5.png (18:37) is byte-identical (sha256 fe9c78ce…3ea18) to Design/icons/RTTy_app_icon_091026_stitched.png, already on every icon surface since 8a2ddc3 and installed on all six hosts in build 506 (ICNS 7bd033da…). Nothing to change; killall Dock run on the hub at 18:39 to refresh the icon cache.
• Records: fleet/SESSION-STATE.md (18:3x entry), fleet/ISSUES.md ISSUE-20260910-09, memory jumbo-mtu-blackhole-apple-object-storage.

Verification evidence

• ASC TestFlight → macOS Builds: Version 0.3.831, build 506, "Ready to Submit".
• ~/dev/_handoff/rtty-appstore-506-20260910/upload-506-retry2.log (UPLOAD SUCCEEDED, rc 0); altool logs under ~/Library/Logs/ContentDelivery/com.apple.itunes.altool/.
• gh pr view 50 / 51 --repo richhdoty/RTTy → merged; git -C ~/dev/apps/RTTy log --oneline -1 = 05094fe.

Outstanding owner actions (Rich)

1. App Store listing before "Add for Review": ASC version string is "1.0" but the build is 0.3.831 (must match), plus description, screenshots (macOS + iOS), keywords, support URL, privacy answers, and the EU trader-status notice. Not started — content decisions.
2. Decide the persistent fix for ISSUE-20260910-09 (scoped route at login vs en0 MTU 1500).
3. Build 507 (Codex fixes + compliance key) — release run pending; see fleet/SESSION-STATE.md.