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 7 · SESSION — Backend: un-quarantine the hidden tests, then the honest MCP surface

DoneOwner · ait_6527f10c

Waiting on 1 · 1 still openSPEC → backend: checkout returns every buyer to ONE origin, so app.tactile-connect.com buyers land on tactile.to

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 7 · SESSION — Backend: un-quarantine the hidden tests, then the honest MCP surface** · done

Where it sits: TacTile › Inbox — on deck

## Waiting on 1

- SPEC → backend: checkout returns every buyer to ONE origin, so app.tactile-connect.com buyers land on tactile.to — to do

1 of those is still open. If one genuinely blocks this, say so and stop rather than working around it.

## The brief on file

DONE 2026-08-07 — PRs #260/#261 (ancestry-verified). Suite runs whole: 36 files, 675 assertions, and a guard fails if an exclusion list returns.

THE QUARANTINE WAS HIDING FALSE CONFIDENCE, NOT JUST FAILURES — the most valuable finding of the round. All three excluded files failed for the same reason and none was a product bug: the mocks had drifted. Two mocked the old subscription_plans:{features} embed after v_account_tier began returning features directly; one matched /rest/v1/groups after the table became asset_groups — and that file's own console.warn("unhandled URL") had been printing the answer the whole time, unread, because the file was excluded by name. Then the part that matters: with features resolving to {}, NEIGHBOURING assertions were passing for the wrong reason — every tier gate denies on empty features, so `assert.ok(res instanceof Response)` held no matter what the gate did. Three one-line mock fixes turned vacuous assertions into real ones.

DELETE SEMANTICS: Matthew chose a true row delete; the session flagged first that it is unrecoverable here and takes agent_pending_actions with it, then built it. Mitigation is ordering — the audit_log row is written BEFORE the delete, because that table has no FK to conversations and is the only durable trace once the row is gone. Auditing afterwards would mean a crash in between leaves nothing.

SSE DOC found both existing descriptions wrong. AGENTS.md claimed all AgentEvent payloads carry __stubbed:true — wrong three ways: it is on the provider's Message not on AgentEvents, only turn_end.stubbed reaches the wire, and DeepSeek is the customer default so it is not Anthropic-specific. A client written from that sentence searches for a field that is never there. Both event lists also omitted preview_proposed and preview_resolved — the two carrying the entire approval flow. Honest caveat recorded in the doc: freezing the contract does NOT make the 13-type live pass runnable; the runner has no client-injection seam and AGENT_PROVIDER has no fixture mode, so stub mode exercises decoding, not tool selection.

ITEM 5 NOT DONE: group/family reconciliation is unchanged from round 6 and remains substantial (three ops fail on every call; family's are modelled against the wrong entity). One thing this round added: groups-merge-eject.test.ts is un-quarantined and green, so those routes finally have a working harness to reconcile against — that was the missing prerequisite.

## 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 7 · SESSION — Backend: un-quarantine the hidden tests, then the honest MCP surface