Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Inbox — on deck·49 in this wave

Wave

Inbox — on deck

Briefs Nova has teed up and are ready to run — each task's prompt is a complete, self-contained brief.

TacTile › Inbox — on deck

39/49 done10 open3 open blockers

Selected taskclear

ROUND 8 · SESSION — Web: clear the four hazards, then finish QR depth

DoneOwner · ait_55533fed

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

**ROUND 8 · SESSION — Web: clear the four hazards, then finish QR depth** · done

Where it sits: TacTile › Inbox — on deck

## The brief on file

DONE 2026-08-08 — PR #270 (ancestry-verified). All four hazards cleared, each with a test verified by actually reintroducing the fallback rather than assuming.

THE DECORATIVE ONE NEEDS A CORRECTION TO HOW IT WAS REPORTED. The session described it as "the resolver falls back to 0.5" and implied that was fixed. Viv checked: resolve-options.ts:417 STILL reads `?? 0.5`, and qr-studio-silent-substitutions.test.ts:47-50 deliberately PINS that — `expect(shape?.outlineWidth).toBe(0.5)` plus `.not.toBe(DECORATIVE_DEFAULT_OUTLINE_WIDTH)`. The hazard was closed at the WRITER (every decorative patch must now carry an explicit width, line 62), which makes the fallback unreachable in practice and is a legitimate strategy — but a future session reading `?? 0.5` will "fix" it and fail two assertions in a way that makes the TEST look wrong. A comment now says so at that exact line (#271), including what to change first if the reader is ever hardened too.

THE HONEST NON-FIX: one hazard-list item was wrong and the session said so instead of quietly "fixing" it. Transparency does not poison the meter — the grader resolves "transparent" to null, tracks it, and caps at C saying contrast "could not be verified", which is correct behaviour. What was wrong was the REMEDY text, which blamed the user for a deliberate choice. The toggle was genuinely missing; the meter now gives the true reason.

LOGO INTERACTIVE CROP DELIBERATELY NOT BUILT, and this was the right call. All five logo snapshot fields — crop rect, slider, shape, corner rounding, logoEnabled — are read by NOTHING in either renderer package outside the type declaration. They are iOS-only state; the logo comes from CenterElement, which the snapshot cannot represent. A crop UI would have written five fields no web path reads — a control whose every output is ignored, which is the exact hazard shape the round existed to eliminate. Filed as t_57483e80 with the two package changes that unblock it.

Four of five depth items shipped (decoratives, stickers, randomised palette, gradient midpoints); the 44 render tests stayed green.

CROSS-PLATFORM DECISIONS locked in context/decisions/2026-08-08-one-qr-vocabulary-across-three-platforms.md. What the sticker one costs today: Android writes the kebab id straight into stickerAsset and the lookup fails SILENTLY, so a sticker applied on Android renders as no sticker everywhere else — specced as t_d5b7c2f2 with the iOS/Android halves named.

NOTE FOR WHOEVER IS NEXT: qr-studio-shape-coverage.test.ts will start failing once backend makes squircle/diamond/cross render. That is intended — DELETE those three assertions rather than weakening the test, and the pickers pick the values up with no code change because they derive from the resolver.

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

Inbox — on deck

ROUND 8 · SESSION — Web: clear the four hazards, then finish QR depth