Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›iOS›iOS — Build & release·18 in this wave

Submit iOS build for reviewTo do · blocker Approve: iOS releaseTo do · blocker Rotate the leaked Supabase service_role key + provision the release iOS plistTo do · blocker Remove the simulator auto-login before releaseDone Verify App Store privacy labels match realityTo do Produce iPhone + iPad screenshotsTo do Verify in-app purchase products match Stripe/App Store ConnectTo do Full device test pass on physical iPhoneTo do Full device test pass on physical iPadTo do App Store review pre-flightTo do TacTileConnectTests bundle fails as a whole, and the live Canvas Arrange algorithm has zero coverageDone arrangeLegacy exists only to keep its own test meaningful — decide: delete both, or make it realTo do Write iOS store listing copyTo do CustomDomainViewModelTests has never run — orphaned from the test target by a now-false commentDone project.pbxproj + entitlements hygiene: 4 tests that never run, 8 phantom file refs, an unreferenced Release entitlements fileIn progress Reconcile the destination count: app shows 143, brief says 282Done Agent UI test target needs a mock server nobody starts locallyTo do tile_nfc_profiles RLS exists in production but in no migration — the migrations do not describe prodTo do

Wave

iOS — Build & release

Ship to the App Store. Fastlane already works — a successful TestFlight upload ran 2026-07-25. Store listing, review prep, and the release build are what's left.

TacTile › Launch TacTile › iOS › iOS — Build & release

4/18 done14 open3 open blockers

Selected taskclear

CustomDomainViewModelTests has never run — orphaned from the test target by a now-false comment

DoneOwner · ait_ebd4d11b

9 of 10 iOS unit-test files are wired into TacTileConnectTests; this one is not, so its tests have never executed. The comment explaining why says there is no test target — there is one, so the reason it was skipped is no longer true.

No dependencies in this wave — nothing gates it, and nothing waits on it.

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**CustomDomainViewModelTests has never run — orphaned from the test target by a now-false comment** · done

9 of 10 iOS unit-test files are wired into TacTileConnectTests; this one is not, so its tests have never executed. The comment explaining why says there is no test target — there is one, so the reason it was skipped is no longer true.

Where it sits: TacTile › Launch TacTile › iOS › iOS — Build & release

## The brief on file

IN PROGRESS 2026-08-05 (iOS session) — wired up, and it turned out worse than the task described.

DONE SO FAR (on branch feature/ios, PR #223):
 - Added PBXFileReference CD0091FFFFFFFFFFFFFFFFFF, PBXBuildFile CD0091AAAAAAAAAAAAAAAAAA, a new
   `Tests` PBXGroup (SETT00010001SETT00010002) under the Settings group, and the file to the
   TacTileConnectTests Sources phase (0FB8FC9AFB7F7371D1997682).
 - Rewrote the false header comment.

TWO THINGS THE TASK DID NOT ANTICIPATE:

1. THE COUNT WAS WRONG. I said "9 of 10 test files are wired"; it is 8 of 10. The
   TacTileConnectTests Sources phase contained exactly eight entries — NFCTagClassifierTests,
   NFCChipCatalogTests, NFCEncoderWriterSimulatedTests, NFCGoldenNDEFTests, NFCScanRouterTests,
   GallerySavePlanTests, QRPayloadParseTests, AnalyticsFormattersTests. BOTH orphans were absent.

2. THE FILE DID NOT COMPILE ONCE WIRED. Every call site failed with "call to main actor-isolated
   static method … in a synchronous nonisolated context" — 20 errors, because CustomDomainViewModel
   is @MainActor and so are its statics. Fixed by annotating the test class @MainActor.
   This is the real cost of an unwired test: it does not merely fail to run, it silently rots
   against the code it is supposed to be guarding. Its sibling CanvasArrangeLayoutTests
   (t_05660f7d) had rotted the same way — three methods calling `try XCTUnwrap` without `throws`.

STATUS: `xcodebuild build-for-testing` → ** TEST BUILD SUCCEEDED **. A targeted run of the two
suites is the remaining verification before this closes.

NOT DONE, AND WORTH ITS OWN LOOK: a full `xcodebuild test` run of TacTileConnectTests reports the
bundle FAILED while every individual suite that printed a result passed (NFCTagClassifierTests,
QRPayloadParseTests). Something in the target fails without emitting a Test Case line — most likely
a crash in a suite rather than an assertion. That predates this change and is not caused by it, but
it means the unit-test target has NOT been green for some time and nobody noticed, which is the same
class of problem as this task. Should be tracked separately.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

iOS — Build & release

CustomDomainViewModelTests has never run — orphaned from the test target by a now-false comment