Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›Web — Destination editing·18 in this wave

Wave

Web — Destination editing

No destination editing exists on either web app today. apps/web has zero editing (creation is also being built from scratch in a separate wave); apps/web-mobile has creation for 7 of 14 types but no re-edit path for any of them. Neither web app has an authenticated in-app destination detail/preview page distinct from the public /t/[hash] scan page either — apps/web has no /destinations route of any kind (confirmed: zero list, detail, or edit surface in app/(app)/), and apps/web-mobile's DestinationDetailPage only shows a type badge, date, and trigger-link management, not the destination's actual rendered content. Folding the detail/preview gap in here since one screen (mirroring iOS's DestinationLaunchpad: preview + connected triggers + edit entry + delete) naturally serves both.

TacTile › Launch TacTile › Web › Web — Destination editing

12/18 done6 open1 open blocker

Selected taskclear

SPEC → backend: move update + content wrappers into destinations-core

DoneOwner · ait_3042a424

apps/web has a working update/content client for all 14 kinds written locally because packages/** is the backend worktree's surface. It should live in destinations-core so web-mobile gets it too. Reference implementation exists and is route-tested.

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

**SPEC → backend: move update + content wrappers into destinations-core** · done

apps/web has a working update/content client for all 14 kinds written locally because packages/** is the backend worktree's surface. It should live in destinations-core so web-mobile gets it too. Reference implementation exists and is route-tested.

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

## The brief on file

DONE — web half (commit f8123af0). apps/web no longer bypasses the package.

apps/web/features/destinations/lib/editApi.ts is deleted. It only ever existed because packages/** was read-only when desktop editing shipped, and its own header said to remove it once the package caught up. #230 landed the typed update + content wrappers for all 14 kinds, so all 7 importers now go through createDestinationApi via the app's existing host binding (features/destinations/lib/host.ts): EditDestinationPage, DestinationPreview, and the Payment/LinkHub/Link/Network/Action builders.

tests/unit/destination-edit-routes.test.ts retired — destination-route-contract.test.ts supersedes it and is strictly stronger (14 cases, including a CONTROL asserting a wrong family actually 404s and a check that the verb is specific rather than merely present in the handler file).

The package API is per-kind where the interim one was generic, so the two inherently-generic callers — the launchpad preview and the edit page, which both hold a `type` string off a destination row — go through one exhaustive Record in host.ts. Deliberately a lookup over the package API rather than a URL builder: the route table stays owned by the package and this app never learns a path again. Adding a kind fails the build there.

TWO THINGS THE TYPED WRAPPERS SURFACED:

1. A real defect in the interim client — it sent `owner_account_id` on every update, copied from the create shapes. No Update*Input accepts it; #230's audit found the update handlers never read it. Six builders had been sharing one payload across create and update, and now build the shared fields and spread owner_account_id only on the create call.

2. A package gap, specced as t_4d58a1bd: UpdateLinkHubInput omits `links` and UpdateContactInput omits `fields`, but both are genuinely accepted — updateLinkHubAction reads links as a FULL REPLACE (link_hub.ts:163-170, :236, :279-289), and updateContactAction parses fields and even guards the parse-failure-becomes-empty-wipe case with a 400 (contact.ts:225-245). They work today only because the wrappers JSON.stringify their input verbatim (api.ts:543-559) and passing a VARIABLE skips TypeScript's excess-property check. Switch either call to an object literal and the compiler rejects the field — at which point deleting it looks like the fix, and the request still 200s while the links or contact fields never change. Both now route through one named apps/web/features/destinations/lib/updateGaps.ts, so the thing to delete when the package catches up is a single file.

Verified against a session-start baseline: depcruise/knip/sherif/syncpack 0 new; lint:web, build:web, tsc clean.

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

SPEC → backend: move update + content wrappers into destinations-core