Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›iOS›iOS — Dead code removal·10 in this wave

Approve: iOS dead code removalTo do · blocker Delete 4 orphaned auth viewsDone Delete 4 never-compiled iOS orphan files (~600 lines, zero pbxproj surgery)Done Delete the Shop featureDone Delete dead Analytics screensDone Delete dead NFC encoder flowDone Delete dead ConnectCard viewsDone Delete dead Canvas + Assets viewsDone ~3,900 more lines of compiled-but-never-constructed code (Dash* tile family, AnalyticsKit.Shell helpers, AssetsFilter, AnalyticsOverviewViewModel)In progress Stale assertions in iOS docs and comments — AGENTS.md/CLAUDE.md name directories that do not existTo do

Wave

iOS — Dead code removal

Substantial dead code raises real risk of QA testing the wrong screen — two abandoned generations sit beside the live ones in the same directories.

TacTile › Launch TacTile › iOS › iOS — Dead code removal

7/10 done3 open1 open blocker

Selected taskclear

Delete 4 never-compiled iOS orphan files (~600 lines, zero pbxproj surgery)

DoneOwner · ait_a10a6a20

Four Swift files with zero project.pbxproj references and zero type references outside themselves. Found by re-running the wave's own 4-refs tell across the whole tree. Deletion was attempted 2026-08-05 and blocked by a permission gate — needs Matthew to allow it or do it himself.

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

**Delete 4 never-compiled iOS orphan files (~600 lines, zero pbxproj surgery)** · done

Four Swift files with zero project.pbxproj references and zero type references outside themselves. Found by re-running the wave's own 4-refs tell across the whole tree. Deletion was attempted 2026-08-05 and blocked by a permission gate — needs Matthew to allow it or do it himself.

Where it sits: TacTile › Launch TacTile › iOS › iOS — Dead code removal

## The brief on file

CLOSED 2026-08-09 — the deletion already happened, and the row's carve-out was wrong.

`git ls-files | grep -E 'ErrorStateView|FileSourceModal|TriggerLinkerHostView|QuantityStepper'` returns NOTHING. All four files are gone, despite this row saying the deletion was blocked by a permission gate and nothing was changed. There are now zero unwired Swift files anywhere in the iOS tree (566/566 referenced).

THE CARVE-OUT WAS ALSO WRONG, and acting on it would have broken the build: it listed `Features/Settings/Tests/CustomDomainViewModelTests.swift` as a fifth zero-reference file. It has FOUR references — PBXBuildFile :406, PBXFileReference :1023, group :2876, Sources phase :3038. A plain `git rm` there leaves a dangling Sources entry.

**DO NOT REUSE THE METHOD THIS ROW DOCUMENTS.** It says "every live file carries exactly 4 references, so `grep -c` returning 0 means it never compiled." That is unreliable in both directions:
 • basename grep OVER-counts on collisions — `Config.swift` reports 32, `ContentView.swift` 8;
 • this pbxproj's ids are 16 to 32 characters and several contain non-hex letters, so id-shaped assumptions fail too.

Measuring this cost the round-20 assessment THREE consecutive false findings — "6 uncompiled files", then "70 unreferenced", then "9" — each from a different wrong assumption (id length, id character class, multi-segment path values). All three were artefacts. A critic then found the assessment's own corrected headline still false by the same trap.

So if anyone builds a gate for this category: **validate it against a deliberately broken tree first.** A naive parse of this file is confidently wrong in both directions, and a scan that reports zero orphans on a tree that has them is worse than no scan.

## 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 — Dead code removal

Delete 4 never-compiled iOS orphan files (~600 lines, zero pbxproj surgery)