Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web·2 in this wave

Web: converge the two hand-maintained SF→lucide icon maps (they already disagree)Done verify:app-typecheck reads gitignored build output for 2 of its 27 projects, and its own header says it does notDone

Wave

Web

Two separate apps with zero shared feature code: apps/web (desktop-first) and apps/web-mobile (a deliberate mobile PWA at app.tactile-connect.com). The public destination viewer is the most customer-critical gap in the entire launch.

TacTile › Launch TacTile › Web

2/2 done0 open12 sub-waves326 incl. sub-waves

Selected taskclear

verify:app-typecheck reads gitignored build output for 2 of its 27 projects, and its own header says it does not

DoneOwner · ait_aac988b4

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

**verify:app-typecheck reads gitignored build output for 2 of its 27 projects, and its own header says it does not** · done

Where it sits: TacTile › Launch TacTile › Web

## The brief on file

[2026-10-23 · Viv] DONE (r40, 03:50 PDT) against draft PR #780 (r40/tooling-typecheck, head 5c1a4d9d, off origin/main 4f2c1d6b; not merged, not deployed).
WHAT: commit d111991b "fix(verify): app-typecheck no longer compiles gitignored .next types for web-mobile and runs-dashboard (t_aac988b4)"; files: AGENTS.md, CLAUDE.md, apps/runs-dashboard/AGENTS.md, apps/runs-dashboard/tsconfig.verify.json, apps/web-mobile/AGENTS.md, apps/web-mobile/tsconfig.verify.json, scripts/verify/app-typecheck.mjs, scripts/verify/lib/typecheck-programs.mjs, scripts/verify/ts-source-coverage.mjs, tests/unit/typecheck-program-selection.test.ts.
EVIDENCE: Option (a), in the shape #390 actually used. git show b4d8c6e1 shows #390 did NOT delete the glob from apps/web/tsconfig.json (it is still there on main, line 41); it added apps/web/tsconfig.verify.json (extends + exclude .next) and pointed the check at it.; The dev build genuinely re-adds the glob: next 14.2.35 dist/lib/typescript/writeConfigurationDefaults.js:235-237 (called from dist/lib/verify-typescript-setup.js:121 on next dev/build) pushes '.next/types/**/*.ts' into tsconfig.json include for any app/-dir project and rewrites the file. Measured by calling writeConfigurationDefaults on scratch copies of apps/web-mobile and apps/runs-dashboard tsconfig.json with the glob removed: both...
MUTATION: M1: remove ".next" from apps/web-mobile/tsconfig.verify.json exclude -> new test rc 1 (1 failed | 7 passed: 'no config the gate compiles reads Next build output > apps/web-mobile') AND node scripts/verify/ts-source-coverage.mjs rc 1 ('✗ apps/web-mobile/tsconfig.verify.json: its resolved `include`...
READERS: safety CONFIRMED (Done-when option (a) is met in the shape #390 actually used. The glob stays in tsconfig.json, which Next 14.2.35 rewrites anyway: I reproduced writeConfigurationDefaults re-adding it for both apps....); acceptance CONFIRMED (Done-when (hub text, read myself): THE WORK, (a) preferred over (b), plus the CRITICAL METHOD NOTE (membership through `tsc --showConfig`). Clause (a), 'the way #390 did for apps/web, adding a tsconfig.verify.json if the dev build genuinely needs it', is me...).
GATE: bash scripts/verify/gate.sh passed 55 of 56 (sanctioned verify:secrets-rotation only) on run 2, start load1 4.26. Hunk independence: git merge-tree clean against every open PR touching these files (builder, re-run by the safety reader).
CI on #780, read 03:45 PDT: verify red ONLY at "Secrets rotation audit"; playwright cancelled by the shared concurrency group (not run); swift-parity pass; semgrep, static-firewall, dep-scan, changes pass.
The task text's procedural line "run gate.sh before opening a PR" is met: the gate passed before the PR was opened.

Filed 2026-08-13 by the round-21 web session, found on the FIRST run of the check it was building (verify:ts-source-coverage, #415 → 5f25499b). Not a regression — a pre-existing gap that nothing could see until a second check looked.

THE DEFECT. `apps/web-mobile` and `apps/runs-dashboard` both `include` `.next/types/**` in their tsconfig — exactly the shape `apps/web` had before #390 removed it. `.next/` is gitignored generated output the gate never regenerates, so those two projects are typechecked against build artifacts that may be absent, stale, or machine-specific.

WHY IT MATTERS BEYOND TIDINESS: `scripts/verify/app-typecheck.mjs`'s own header asserts it deliberately reads no build output, citing the two occasions this repo went red on a stale tree while the source was correct. That claim is false for 2 of its 27 projects. A written guarantee that is true for 25 of 27 is the failure mode this repo keeps paying for — see the round-20 AGENTS.md numbered-list drift and `verify:no-harness-artifacts` before it.

CURRENT BLAST RADIUS: measured as harmless today — 0 tracked files lose coverage either way. It is recorded in a `DEGRADED` map in the new check rather than fixed, deliberately, because the fix belongs to `verify:app-typecheck`'s contract and not to a check that merely observed it.

THE WORK: decide whether to (a) drop `.next/types/**` from both tsconfigs the way #390 did for apps/web, adding a `tsconfig.verify.json` if the dev build genuinely needs it, or (b) amend app-typecheck's header to state the exception truthfully and keep the DEGRADED map as the record. (a) is preferred; (b) is only acceptable if something actually depends on those types.

CRITICAL METHOD NOTE, learned the expensive way in the same session: do NOT detect this by scanning resolved `.next/` paths on disk. That is machine-dependent in exactly the way the check exists to name — 43 such paths existed in this tree and 0 on a fresh checkout, and `runs-dashboard` is invisible that way because nobody has ever built it here. Membership must be decided by reading the config through `tsc --showConfig`. The first draft did it the other way and would have gone red on a clean clone.

Run `bash scripts/verify/gate.sh` before opening a PR.

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

Web

verify:app-typecheck reads gitignored build output for 2 of its 27 projects, and its own header says it does not