Part of #337 (Phase 0).
Mobile developer tooling still uses upstream T3 identities, so the J5 test loop fails:
scripts/mobile-native-client.ts builds ios/T3CodeDev.xcworkspace / scheme T3CodeDev and checks bundle com.t3tools.t3code.dev. J5 prebuild emits J5CodeDev / codes.jackson.j5code.dev, so ensure ios fails at xcodebuild..agents/skills/test-t3-mobile/scripts/pair-client.sh opens com.t3tools.t3code.dev with t3code-dev://, so pairing targets the wrong app.scripts/mobile-showcase.ts hard-codes com.t3tools.t3code, the t3code scheme and T3Code.app.- The
test-t3-mobile skill describes .t3 state and ~/.t3/userdata.
Fix: read every id from scripts/lib/j5-branding.ts so this cannot drift again, and add these files to BRANDING.md's pin-advance audit sites.
Done when node scripts/mobile-native-client.ts ensure ios <udid> builds and installs J5 Code Dev and the pairing helper opens the J5 app.
Part of #337 (Phase 0).
Mobile developer tooling still uses upstream T3 identities, so the J5 test loop fails:
scripts/mobile-native-client.tsbuildsios/T3CodeDev.xcworkspace/ schemeT3CodeDevand checks bundlecom.t3tools.t3code.dev. J5 prebuild emitsJ5CodeDev/codes.jackson.j5code.dev, soensure iosfails at xcodebuild..agents/skills/test-t3-mobile/scripts/pair-client.shopenscom.t3tools.t3code.devwitht3code-dev://, so pairing targets the wrong app.scripts/mobile-showcase.tshard-codescom.t3tools.t3code, thet3codescheme andT3Code.app.test-t3-mobileskill describes.t3state and~/.t3/userdata.Fix: read every id from
scripts/lib/j5-branding.tsso this cannot drift again, and add these files to BRANDING.md's pin-advance audit sites.Done when
node scripts/mobile-native-client.ts ensure ios <udid>builds and installs J5 Code Dev and the pairing helper opens the J5 app.