Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›iOS›iOS — Destination editing·17 in this wave

Wave

iOS — Destination editing

Only THREE of 14 destination types actually persist an edit today — website, notes, document. Menu opens a real editor whose save is a no-op stub, so it dismisses as though it worked and silently discards the change. The remaining 10 show "Editing coming soon." Cost split matters here: gallery, video, audio and contact editors ALREADY EXIST and only need a router case wired, while payment, link hub, form, wifi, bluetooth and action must be built from scratch. Six of them also need a backend update endpoint that does not exist yet.

TacTile › Launch TacTile › iOS › iOS — Destination editing

13/17 done4 open1 open blocker

Selected taskclear

Menu editor: item photos are editable but never sent, and the variation/modifier editors have no presentation site

To doOwner · ait_2b7d139a

Two remaining menu-editor gaps found alongside the banner-reset bug (fixed in PR #223). Both are silent — the UI offers an edit the wire cannot carry.

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

**Menu editor: item photos are editable but never sent, and the variation/modifier editors have no presentation site** · to do

Two remaining menu-editor gaps found alongside the banner-reset bug (fixed in PR #223). Both are silent — the UI offers an edit the wire cannot carry.

Where it sits: TacTile › Launch TacTile › iOS › iOS — Destination editing

## The brief on file

PARTIALLY DONE 2026-08-05 (iOS session) — commit 76e4b767, PR #223. Item 2's doc half is fixed; items 1
and 2's build/delete decision still need Matthew.

ITEM 2 — CORRECTED, AND MY ORIGINAL FRAMING WAS WRONG.
This task said "finish it or delete the three unreachable sheets". Deleting would have been a mistake and
I nearly made it. Verified against all three layers instead:
  - DB: a `menu_variations` table exists with an `ordinal` column, which makes the feature look nearly done.
  - API: it is NOT. `POST /api/menu` inserts exactly ONE unnamed variation per item purely to carry that
    item's price — menu.ts:309-320, whose own comment says "Every item gets exactly one variation carrying
    its price (single-price model)". The route never reads a variations array from the payload.
  - iOS: MenuItemPayload has no variations field, and toDraft() hardcodes `pricingMode = .single`, so
    priceCardDisplay's `.variations` branch is unreachable from real data.
So the table is a price carrier, not an implemented feature, and the iOS sheets are the MOST complete part
of a three-layer feature that was never finished. Deleting them would throw away the only built piece.
They are kept, and the file header now states all of this instead of claiming MenuItemEditorSheet offers
"variations + modifier groups" (it renders itemFieldsCard / pricingCard / dietaryTagsCard only).
DECISION STILL NEEDED: build the feature across all three layers, or cut it and delete the iOS sheets.
Do not wire the sheets up without the API half.

ITEM 1 — MENU ITEM PHOTOS, UNCHANGED AND STILL NEEDS A DECISION.
A user crops a photo for a menu item, saves, sees it in the local preview, and it is gone on next load.
MenuItemPayload carries name/description/priceCents/available/dietaryTags only; imageData and imageURL are
dropped. No multipart upload path for menu images exists. Options remain (a) build the upload path — a
backend handoff, needs an endpoint and a column — or (b) remove the photo UI from the item sheet until the
backend exists. An edit control that silently discards its input is worse than an absent one, so "leave it"
is not on the list.

ITEM 3 — DONE. ActionEditorRouter.submitDocument was dead and was removed in commit 8b2c736b.

## 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 — Destination editing

Menu editor: item photos are editable but never sent, and the variation/modifier editors have no presentation site