Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›iOS›iOS — QR build·4 in this wave

Approve: iOS QR buildTo do · blocker Fix hardcoded 'A+' placeholder shown before first readability test completesTo do Approve: Mantis crop pipeline (logo + background image cropping) is live and completeTo do Approve: QR design studio controls & static-mode forms confirmed complete, no stubs foundTo do

Wave

iOS — QR build

Remaining build work on the live QR surface. Legacy QR/NFC screens excluded — see the dead-code list.

TacTile › Launch TacTile › iOS › iOS — QR build

0/4 done4 open1 open blocker

Selected taskclear

Fix hardcoded 'A+' placeholder shown before first readability test completes

To doOwner · Vivt_b99b1d3f

Unlocks 1Approve: iOS QR build

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

**Fix hardcoded 'A+' placeholder shown before first readability test completes** · to do

Where it sits: TacTile › Launch TacTile › iOS › iOS — QR build

## Unlocks 1

- Approve: iOS QR build

## The brief on file

Viv — replace the hardcoded initial readabilityResult default with nil so the badge doesn't show a false passing grade before the real test runs. Done when: readabilityResult starts as nil (matching the already-supported nil-state in readabilityBadge, which renders nothing until a grade or error exists), and QRReadabilityTester still runs on the same 350ms debounce after every design change. File: Features/QR/Pages/QRGeneratorPage.swift:528-533 (hardcoded `.init(grade: .aPlus, passedStageCount: 8, ...)`), badge fallback at :2264-2288. Today: opening the QR generator (or making any design change) shows a fake 'A+' readability badge for ~350ms until the real CoreImage-based test overwrites it — a genuinely poor design could flash a false-positive grade in that window.

## 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 — QR build

Fix hardcoded 'A+' placeholder shown before first readability test completes