Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›DevOps›DevOps Launch Readiness·20 in this wave

Wave

DevOps Launch Readiness

Gated by the surfaces existing. Android is the long pole — it has no release automation and no UI tests, while iOS already has working Fastlane.

TacTile › Launch TacTile › DevOps › DevOps Launch Readiness

4/20 done16 open1 open blocker

Selected taskclear

verify:unit is red on main — qr-pending-design.test.ts can't resolve @tactile/qr-studio

DoneOwner · ait_35c16f43

One test FILE fails to transform, so pnpm verify has been red on main since 2026-07-09. All 2738 tests that do run pass. One-line fix.

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

**verify:unit is red on main — qr-pending-design.test.ts can't resolve @tactile/qr-studio** · done

One test FILE fails to transform, so pnpm verify has been red on main since 2026-07-09. All 2738 tests that do run pass. One-line fix.

Where it sits: TacTile › Launch TacTile › DevOps › DevOps Launch Readiness

## The brief on file

CLOSED — NOT A REPO DEFECT. My round-4 diagnosis was wrong; do not apply the fix this task originally prescribed.

What I claimed: verify:unit had been red on main since d22f3cf8 (2026-07-09) because tests/unit/qr-pending-design.test.ts could not resolve @tactile/qr-studio from the repo root, and the fix was a third alias in vitest.config.ts alongside @tactile/card-connectors and @tactile/mcp-server.

What was actually true: the WORKTREE's pnpm install was stale. packages/qr-studio had landed on main and ~/TacTile-dev/TacTile-android had never installed it, so apps/web-mobile/node_modules/@tactile/qr-studio did not exist. Vite resolves node_modules by walking up from the IMPORTING file, not from the config root, so once that link exists the import resolves with no alias at all. The `pnpm install` I ran in round 4 to investigate is what fixed it.

Verified on 2026-08-07 at bfa5e7a4: no qr-studio alias in vitest.config.ts (still just the three entries), nothing linked at node_modules/@tactile/qr-studio, apps/web-mobile/node_modules/@tactile/qr-studio present, and `pnpm verify:unit` green at 109 files / 2863 tests. The single file runs clean on its own: 43 tests passing.

The generalisable bit, which is the only reason this is worth reading: a red gate in a long-lived worktree may be a stale install rather than anything on main. Run `pnpm install` and re-check BEFORE concluding the repo is broken — and before writing it into a PR description, as I did.

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

DevOps Launch Readiness

verify:unit is red on main — qr-pending-design.test.ts can't resolve @tactile/qr-studio