Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›iOS›iOS — Destination viewers·10 in this wave

Approve: iOS destination viewersTo do · blocker Fix form destinations showing the contact viewerDone Build dedicated link hub viewerDone Build dedicated payment viewerDone Build dedicated action viewerDone Sign off: the eight dedicated destination viewersTo do Fix Video destination viewer — DestinationViewerScreen passes no content argumentDone Contact preview loses fax identity, extra addresses, notes and every preserved fieldTo do Build dedicated wifi viewerDone Build dedicated bluetooth viewerDone

Wave

iOS — Destination viewers

6 of 14 types show a wrong or generic viewer. Form shows the contact viewer — a straight bug.

TacTile › Launch TacTile › iOS › iOS — Destination viewers

7/10 done3 open1 open blocker

Selected taskclear

Contact preview loses fax identity, extra addresses, notes and every preserved field

To doOwner · ait_4a822203

Four related data-fidelity gaps in the contact viewer, surfaced once it started rendering real content. A fax renders and dials as a mobile; only the first address survives; notes and all unrecognised field types are dropped with no indication.

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

**Contact preview loses fax identity, extra addresses, notes and every preserved field** · to do

Four related data-fidelity gaps in the contact viewer, surfaced once it started rendering real content. A fax renders and dials as a mobile; only the first address survives; notes and all unrecognised field types are dropped with no indication.

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

## The brief on file

Found 2026-08-06 by an adversarial review of PR #229, AFTER the viewer started rendering real customer
content (commit 5d7fcd53). None of these was reachable before that — the viewer showed a demo fixture,
so nobody could notice their card was incomplete. Wiring real data is what made them live.

1. A FAX IS RENDERED, DIALLED AND EXPORTED AS A PHONE. Verified in code, and note this was
   ADVERSARIALLY DISPUTED AND THE DISPUTE WAS WRONG — worth recording so nobody re-refutes it.
   The reviewer said a fax renders as a mobile. A critic refuted it on the grounds that
   `ContactActionFieldKind` has eleven cases and none is `fax`, so a fax could never reach the phone
   list. That reasoning is sound but the premise is incomplete: the bridge COLLAPSES fax into phone —
   ContactActionContent.swift:182 is literally `case "phone", "fax": return .phone`. So a fax wire
   field becomes a `.phone` item, lands in `multiFields`, and `Contact(content:)`'s `repeated(.phone)`
   puts it in `contact.phones`, where it renders as a phone row, is tappable-to-dial, and exports as
   TEL in the vCard. The finding stands.
   FIX IS NOT TRIVIAL, which is why it is filed rather than patched: the distinction is destroyed at
   load time, so the viewer cannot recover it. Carrying the original wire type through would mean
   touching ContactActionFieldItem — the EDITOR's model, whose save path replaces the whole `fields`
   array and has a documented history of destroying customer data. Do it deliberately, with the
   contact-save regression test in front of you, not as a drive-by.

2. ONLY THE FIRST ADDRESS SURVIVES. `Contact.location` is a single String and the mapping takes
   `repeated(.address).first`. A card with home and work addresses silently shows one. The display
   model needs a list, or the viewer needs to say there are more.

3. NOTES ARE DROPPED. `.notes` is a real ContactActionFieldKind and the loader populates it (the
   `contact_cards.notes` COLUMN arrives as a multiField), but `Contact` has no notes property and the
   mapping has no notes branch, so the text vanishes from the preview.

4. EVERY UNRECOGNISED FIELD TYPE IS DROPPED WITH NO INDICATION. The loader routes anything the bridge
   cannot name into `preservedFields` (ContactActionContent.swift:365-368) — deliberately, so a save
   does not delete it — and the viewer never reads that bucket. The bridge recognises only email,
   phone, fax, address, website, link, social_link and notes, while the card editor writes many more
   types verbatim. TREAT THE EXACT LIST AS UNVERIFIED: the reviewer enumerated messaging / payment /
   pet / medical / emergency / credential / custom-app from ConnectCard's separate 56-entry `FieldType`
   model, and the critic flagged that as probably the documented filename-vs-typename trap. Confirm
   which types the CONTACT path can actually produce before sizing this.
   Whatever the list, the shape of the bug is real: fields the customer saved are absent from the
   preview with no "3 more fields not shown" affordance, so the card reads as complete when it is not
   — a narrowed version of the demo-data bug PR #229 set out to kill.

DONE WHEN: a contact whose card carries a fax, two addresses, notes and at least one preserved field
previews without silently misrepresenting any of them — either rendered, or explicitly counted as not
shown. Plus a mapping test per case.

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

Contact preview loses fax identity, extra addresses, notes and every preserved field