[jayleaton]

These are fixes from the final MacBook pass of #235 (gist 73b48c0d).

Summary

1. iOS widget mark: skipped. Upstream never drew it on this widget.

• PipMark.imageset ships in the widget target, but no widget view draws it.
• Upstream drew T3Mark (<Image assetName="T3Mark" />) only in AgentActivity.tsx: the Agent Activity widget and Live Activity. The fork removed those with T3 Connect (b4424b9).
• The Subscription Usage widget never drew a mark on upstream or here, so there's nowhere to restore it.
• withWidgetLogoAsset and assets/widget/PipMark.svg now ship an asset nothing draws. They can go in a follow-up if push PRs feat(server): phones register Expo push tokens with each server #229–feat(mobile): direct push notifications from each server #231 don't bring a view back.

2. Dev home-screen icon now matches the dev in-app mark.

• Production and preview keep the lavender Pip on navy.
• Development builds now use the blueprint with a white Pip, like the desktop dev icon and the in-app BrandMark (assets/dev/blueprint-ios-1024.png).
• scripts/export-android-icons.ts (vp run icons:export:android) renders both from assets/dev/app-icon.icon's background and annotation layers:
  • apps/mobile/assets/agents/dev-ios-icon-1024.png: full bleed, flattened with no alpha channel, because iOS applies its own mask and the App Store rejects transparency. The Icon Composer render already has its corners cut, so it can't be used.
  • apps/mobile/assets/agents/android-dev-icon-background.png: the adaptive background, under the existing white android-icon-monochrome.png foreground.
• The other generated assets came out byte-identical.

Left to right: the current dev icon (same as prod), the in-app dev mark, the new iOS dev icon (shown masked), and the new Android dev icon (shown with a circle mask).

3. Environment → Check for updates.

• Placement fixed. Every action on the environment screen shared one message slot, drawn above the Ada section, so a failed check looked like part of Routes. Each result now shows in its action's section:
  • the update check and server update results in the Ada section, under the version and next to Check for updates;
  • refresh and provider-update results in Providers.
• Release track: already correct. No code change.
  • The track comes from the server's version.
  • Fork nightlies report versions like 0.1.9-nightly.20261113.485001, which read as nightly.
  • "keeps nightly and preview hosts on their channel…" in environment-maintenance.test.ts already shows a nightly host finding the newer nightly.
  • The MacBook pass was on a dev server reporting plain 0.1.9, which reads as stable. With no stable fork release, "No stable release was found." is the correct answer there.

Checks

• vp run check:changed → pass: format, lint, knip, typecheck (2 packages), test, react compiler.
• vp run icons:export:android reproduces every committed mobile asset.

MacBook captures needed

1. Home-screen icon on a dev build: the blueprint with a white Pip, in light and dark. A production or preview build should still show navy with a lavender Pip.
2. The dev build's loading screen BrandMark beside that icon, if it stays up long enough.
3. Environment → Check for updates on a dev server (plain 0.1.9): "No stable release was found." in red inside the Ada section, under the version, not above it.
4. The same on a nightly server (0.1.9-nightly.…): "Version … is available." or "You are up to date." in the Ada section.
5. Providers → Refresh providers: "Provider status refreshed." now inside the Providers section.
6. Android, if checked: the dev adaptive icon (blueprint inside the mask) and the themed monochrome icon.

Merge Danger

Door: two-way. Assets, one exporter step and one screen's message placement.

Blast Radius: mobile

• Dev builds' native icon changes. The fingerprint changes for the development variant, so dev clients need a rebuild (vp run mobile:install).
• Environment screen: action messages move into their sections. There's no behavior change.

Model and harness: Claude Opus 5.5 in Claude Code (T3 Code).

🤖 Generated with Claude Code

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	21.5 KiB	21.5 KiB	0 B (0.0%)	24.4 KiB	✅
Codex	Live turn messages	1	1	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.9 KiB	21.9 KiB	0 B (0.0%)	24.4 KiB	✅
Claude	Live turn messages	1	1	0 (0.0%)	8	✅

Baseline: 22240d2 · PR result: d0dca11 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.