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: UpdateLinkHubInput is missing `links`, which the worker does accept

DoneOwner · ait_4d58a1bd

#230's UpdateLinkHubInput omits `links`. The worker's updateLinkHubAction reads it (full replace). Link-hub editing works only because the wrapper stringifies its input verbatim and TS skips excess-property checks on variables.

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: UpdateLinkHubInput is missing `links`, which the worker does accept** · done

#230's UpdateLinkHubInput omits `links`. The worker's updateLinkHubAction reads it (full replace). Link-hub editing works only because the wrapper stringifies its input verbatim and TS skips excess-property checks on variables.

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

## The brief on file

DONE 2026-08-06. Backend landed both fields: packages/destinations-core/src/api.ts now declares `links?: Array<{label,url,ordinal?}>` on UpdateLinkHubInput and `fields?: ContactFieldInput[]` on UpdateContactInput.

Web half closed in the same pass: apps/web/features/destinations/lib/updateGaps.ts is DELETED (its own header said to delete it when the package added the two fields), and its three call sites — ConnectCardBuilder.tsx, ContactBuilder.tsx, LinkHubBuilder.tsx — now call api.updateContact / api.updateLinkHub directly with the typed input instead of routing through the widening helper.

The reason the helper existed at all is worth keeping in mind for the next gap: both updates worked at runtime the whole time, because the wrappers JSON.stringify their input verbatim and passing a VARIABLE skips TypeScript's excess-property check. Switching a call site to an object literal would have made the compiler reject the field, at which point deleting it looks like the fix — and the request still 200s while the links or contact fields silently never change.

## 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: UpdateLinkHubInput is missing `links`, which the worker does accept