Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›iOS›iOS — Dashboard, Canvas & Assets build·41 in this wave

Approve: iOS Dashboard, Canvas & AssetsTo do · blocker Dashboard: item-carrying tab navigationTo do Dashboard: wire Recent Triggers row tapTo do Dashboard: wire Families carousel tapTo do Assets: wire Triggers tab Create to real flowTo do Assets: fix Family Schedule context menuTo do Assets: wire real Most scans / Most assets sortTo do Launchpad: wire Mute DestinationTo do Launchpad: persist Save and Close editsDone Launchpad: real Connected Devices dataDone Launchpad: persist Menu destination editsDone Build out the family system — creation and family viewTo do Canvas: search no-results stateTo do Canvas: investigate hardcoded launchpad placeholdersTo do Assets: fix N+1 fetch in FamilyAssetPickerTo do Assets: update stale AGENTS.mdTo do Launchpad: Connected Devices empty stateTo do Launchpad: add Retry to error viewsTo do Dashboard: distinct error states for Recent listsTo do Canvas: wire + Asset buttonTo do Canvas: wire Create asset family pillTo do Canvas: handle realtime delete eventsTo do Decide: CanvasFilterChips dead codeTo do Assets: distinct error states for Destinations/FamiliesTo do Decide: LegacyURLPill wiringTo do Decide: delete dead GroupDetailView.swiftDone Launchpad: wire real Disconnect actionDone Launchpad: build Gallery destination editorDone Launchpad: build Video/Audio destination editorDone Launchpad: build Contact/Form destination editorDone Launchpad: build Link Hub destination editorDone Launchpad: real Menu destination creationTo do Launchpad: real Link Hub destination creationTo do Sign-off: Dashboard end to endTo do Sign-off: Canvas end to endTo do Sign-off: Assets tab end to endTo do Sign-off: Launchpads end to endTo do iOS ships two different app icons — decide which is canonicalTo do iOS silently drops destinations whose type it cannot mapDone iOS has no destinations write path — name/description and mute are read-only from the clientTo do iOS: video/audio edit mode does not show the media you are editingTo do

Wave

iOS — Dashboard, Canvas & Assets build

Remaining build work on the non-destination core surfaces. Everything marked 'coming soon' in these screens is intended to ship.

TacTile › Launch TacTile › iOS › iOS — Dashboard, Canvas & Assets build

10/41 done31 open1 open blocker

Selected taskclear

Launchpad: persist Save and Close edits

DoneOwner · Vivt_ae7d5750

Unlocks 1Approve: iOS Dashboard, Canvas & Assets

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

**Launchpad: persist Save and Close edits** · done

Where it sits: TacTile › Launch TacTile › iOS › iOS — Dashboard, Canvas & Assets build

## Unlocks 1

- Approve: iOS Dashboard, Canvas & Assets

## The brief on file

CLOSED AS SUPERSEDED 2026-08-09. Do NOT reopen and action this as written — following it would re-add the exact defect it was filed against.

It reads: "Launchpad: persist Save and Close edits — today handleSaveAndClose() just calls dismiss() and silently discards the edit. DestinationLaunchpad.swift:705-709, :424, :432."

At eb29c404 the function name and every line number are wrong, and the premise is inverted. `handleSaveAndClose` does not exist in DestinationLaunchpad.swift. The footer button is now labelled **"Close"** (`:830-837`), with a comment recording why: *"'Close', not 'Save and Close'. There is no destinations write path from this client… the old label promised a save that never happened and discarded the edit."* And `handleClose()` (`:1005-1018`) documents the deliberate decision NOT to add a client-side PATCH: *"a new production write path from a client, against a database with zero backups, that cannot be exercised offline, is not something to ship on a hunch."*

So the silent discard was fixed by REMOVING the false promise, not by adding a save. A session reading this row would restore the affordance and reintroduce it.

The only surviving `handleSaveAndClose` in the tree is `QRLaunchpad.swift:540`, which is fully implemented (commits through reencodeService, surfaces errors) and is not what this row describes.

WHAT THE REAL WORK IS, if someone wants destination editing from the launchpad: add a destinations UPDATE endpoint plus a DestinationsService, then restore the save affordance on top of it. That is backend-first and belongs in a backend wave — file it there rather than resurrecting this 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

iOS — Dashboard, Canvas & Assets build

Launchpad: persist Save and Close edits