Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›iOS›iOS QA — Destinations·20 in this wave

Wave

iOS QA — Destinations

Sign-off on every destination type: creation, viewing, and editing. 14 types. Known gaps mean several of these are expected to FAIL until the editing and viewer waves land.

TacTile › Launch TacTile › iOS › iOS QA — Destinations

1/20 done19 open1 open blocker

Selected taskclear

Decide: gallery at exactly 30 items cannot swap in one save

To doOwner · met_6b278b5a

A user whose gallery is full has to remove an item and save, then add the new one as a second save. That is a deliberate safety trade, but it is a product decision that should be confirmed rather than inherited.

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

**Decide: gallery at exactly 30 items cannot swap in one save** · to do

A user whose gallery is full has to remove an item and save, then add the new one as a second save. That is a deliberate safety trade, but it is a product decision that should be confirmed rather than inherited.

Where it sits: TacTile › Launch TacTile › iOS › iOS QA — Destinations

## The brief on file

PRODUCT DECISION, low urgency, arising from the gallery edit-mode work shipped 2026-08-02 (PR #184/#187).

THE BEHAVIOUR: a gallery holding exactly 30 items (the cap) cannot swap an item in a single save. Removing one and adding one is refused with "A gallery holds 30 items. Remove some and save, then add the new ones."

WHY, and it is not arbitrary: the three-phase save runs deletes LAST, because deletes are the only irreversible call — updateGalleryAction hard-deletes rows AND their R2 objects, against a database with pitr_enabled=false and zero stored backups, and R2 has no object versioning. Ordering deletes after the uploads means a failure anywhere earlier costs the user nothing.

The consequence is that at add time the live row count is still 30, and the server evaluates the cap against the live count (gallery.ts, addGalleryItems). It WILL reject. GallerySavePlan predicts that and refuses up front rather than failing mid-save with photos already uploaded.

THE ALTERNATIVE, and why it was not taken: delete first to make room. That is precisely the ordering that turns a failed upload into permanently destroyed photos — the user's originals are gone and the replacements never landed. On a database with no recovery path, that is not a trade worth making for convenience.

WHO IT AFFECTS TODAY: nobody. Production's largest gallery is 16 items across 23 galleries; none are near the cap. This only bites once someone fills one.

OPTIONS IF YOU WANT IT CHANGED:
  a) Leave it. The refusal message names the two-step path that works. Zero risk.
  b) Raise the cap (MAX_GALLERY_ITEMS = 30 in gallery.ts, mirrored as GallerySavePlan.maxItems). Sidesteps the collision without weakening the ordering, but pushes the same edge further out rather than removing it.
  c) Make the server evaluate the cap against the POST-DELETE count. Needs a transactional or two-phase server change so the delete is not committed until the add succeeds. Correct, and materially more work than the other two.

Do NOT "fix" this by moving deletes before uploads. That is the one option that trades data safety for convenience, and the reasoning is recorded in GallerySavePlanTests.testSwappingAtTheCapIsRefused_theDeliberatePriceOfDeletingLast — a test that failed on first write because the assumption was wrong in exactly this way.

## 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 QA — Destinations

Decide: gallery at exactly 30 items cannot swap in one save