Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›web-mobile — Parity & docs·7 in this wave

Approve: web-mobile parityTo do · blocker Fix the stale m.tactile.to referencesDone Add custom domain settings to web-mobileTo do Add data export settings to web-mobileTo do Add the missing destination builders to web-mobileDone Decide and document the web-mobile desktop storyTo do Fix the stale m.tactile.to references in web-mobile docsTo do

Wave

web-mobile — Parity & docs

Deliberate, live, actively developed PWA — keep it. But it has real gaps and its documentation points at a dead domain.

TacTile › Launch TacTile › Web › web-mobile — Parity & docs

2/7 done5 open1 open blocker

Selected taskclear

Fix the stale m.tactile.to references

DoneOwner · Vivt_53abb409

Unlocks 1Approve: web-mobile parity

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

**Fix the stale m.tactile.to references** · done

Where it sits: TacTile › Launch TacTile › Web › web-mobile — Parity & docs

## Unlocks 1

- Approve: web-mobile parity

## The brief on file

SUPERSEDED 2026-08-13 by t_26939280 — NOT COMPLETED. The m.tactile.to references are still stale.

Closed only to correct its priority. It carried HIGH for five rounds on a docs-only cleanup and `task_update` exposes no `priority` field, so it was escalated to Matthew four times purely because it looked store-blocking. Re-filed at MEDIUM in the same wave as t_26939280 with the scope caveat about near-miss hostnames carried over.

Work the new row.

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

web-mobile — Parity & docs

Fix the stale m.tactile.to references