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

TacTileConnectTests bundle fails as a whole, and the live Canvas Arrange algorithm has zero coverage

DoneOwner · ait_efc87ba8

Two gaps surfaced by wiring the orphaned test files. The unit-test target reports FAILED while every suite that prints a result passes, and the Arrange button's actual algorithm is untested.

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

**TacTileConnectTests bundle fails as a whole, and the live Canvas Arrange algorithm has zero coverage** · done

Two gaps surfaced by wiring the orphaned test files. The unit-test target reports FAILED while every suite that prints a result passes, and the Arrange button's actual algorithm is untested.

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

## The brief on file

CLOSED 2026-08-08 (round 11). Item 1 was retracted by its own author as a misdiagnosis; item 2 shipped. Both carry-forwards are filed so nothing is lost with this task:

1. The `arrangeLegacy` question → t_34c8f381 (production does not call it; it survives only to keep CanvasArrangeLayoutTests meaningful, which is coverage-shaped but not coverage).
2. The CI-wiring decision → carried into round 11's report as a recommendation WITH the measured numbers, which is what it was missing. `scripts/verify/ios-unit-tests.sh` and `pnpm verify:ios-unit` now exist and are proven working; they are deliberately NOT in `run-all.sh`'s CHECKS array, because that decision lands on three other sessions' merges and is Matthew's to make. Numbers for it: 219/219 green, ~164s cold on a quiet machine. See t_b710ffd4 for the agent-UI half.

VERIFIED THIS ROUND, so nobody re-investigates: the title's claim that `TacTileConnectTests` fails as a bundle is false, exactly as this task's own body already retracted. Ran unfiltered against iPhone 17 Pro / iOS 26.5: 219 tests, 0 failures, exit 0.

## 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

TacTileConnectTests bundle fails as a whole, and the live Canvas Arrange algorithm has zero coverage