Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›MCP surface·47 in this wave

Approve: MCP surfaceTo do · blocker 13 production secrets overdue for rotation — the gate cannot be green until this is resolvedTo do · blocker Deploy step 2 — verify/rotate production MCP Worker secretsTo do Deploy step 4 — fix the stale "NOT DEPLOYED" banner and deploy docsDone Add action.* and bluetooth.* op groups to the MCP catalogDone Build real handlers for group.* (9 ops)Done Build real handlers for family.* (7 ops)Done Build settings.* MCP tools including custom domain managementTo do Verify/build the Connected Apps management UI for MCP OAuth clientsDone Add rate limiting, quota, and cost controls to the hosted MCP serverDone Honesty check — reconcile investor deck MCP claims against what shipsTo do Verify "everything a human can do, an agent can do over MCP" end to endTo do staging-api is a day behind main — and writes to the production SupabaseDone MCP GAP INVENTORY — every unwired op, with the decision attached to eachDone Demo account for screenshots + QA — seeder is live, shape is frozenTo do SECURITY: hosted MCP tool agent.approval.resolve may let the model approve its own proposalsDone Approvals: resume re-executes approved rows, REST resolveApproval is non-atomic, inbox.ts selects a missing expires_atTo do Build the full medialink.* MCP tool set (3 ops)Done Build the payment.* connector MCP tool set (3 ops)To do Build the full webhook.* MCP tool set (4 ops)Done Build zap.* MCP tools or explicitly cut Zapier from v1.0 MCP scopeTo do Build link.schedule.repoint, link.compound, wizard.suggest or cut themTo do QA: the public MCP tools page opens without sign-in and lists the tools (desktop web and phone)Blocked Deploy step 1 — verify DB migration + RLS on OAuth tablesDone Deploy step 3 — confirm CF route/DNS for mcp.tactile.to is production-gradeTo do Deploy step 5 — formalize the MCP smoke testTo do Build nfc.lock and nfc.unlock MCP toolsTo do Build contact.vcard.export and contact.delete MCP toolsDone Build linkhub.create and linkhub.delete MCP toolsDone Build videoaudio.create and videoaudio.replace MCP toolsTo do Build document.create and document.replace MCP toolsTo do Build the full social.* MCP tool set (6 ops)To do Build the full paylink.* MCP tool set (4 ops)Done Build wifi.edit MCP toolDone Build the full form.* MCP tool set (7 ops)Done Build the analytics automation layer MCP tools (6 ops)Blocked Wire inbox.list and inbox.mcp_approval to real handlersDone Add architecture test guarding against a second tool-handler implementationDone Publish a public MCP tool manifest / discovery docsDone Webhook signing secret: add the one surface that can reveal itDone A Website destination's URL cannot be edited through the agent surface at allDone SPEC → backend: webhook secret reveal/rotate endpoints + secret_fingerprint on the listDone NEEDS MATTHEW: decide whether resolve_trigger_destination keeps anon EXECUTEDone 5 proposal-only MCP ops are advertised with no task row building themTo do contact.delete MCP tool has no destination-type guard: any hash the caller owns is hard-deletedDone Add rule E to the single-tool-handler-path test: a handler map keyed by tool name must go red (follow-up to #698, t_27dbb775)Done notes.delete, document.delete, menu.delete and videoaudio.delete soft-delete any destination type the caller owns, and report success for a hash that matched nothingDone

Wave

MCP surface

Thesis pillar 3 — "Agentic AI + MCP." The investor deck claims first-in-category MCP-native. Audit (2026-07-26) found the hosted server IS live at mcp.tactile.to with real OAuth production traffic (14 clients, 11 tokens) — but the code's own deploy banner still says "NOT DEPLOYED" (stale), and tool coverage is genuinely incomplete: roughly half the 147-op catalog are proposer stubs that never mutate state, and 2 of 14 destination types (Action, Bluetooth) have zero MCP presence at all. Not cuttable: this is a stated structural moat.

TacTile › Launch TacTile › MCP surface

27/47 done20 open2 open blockers

Selected taskclear

Add rule E to the single-tool-handler-path test: a handler map keyed by tool name must go red (follow-up to #698, t_27dbb775)

DoneOwner · Vivt_ff7a5463

Done when: tests/architecture/single-tool-handler-path.test.ts has a rule E that goes red on (a) a new packages/agent-core/src module exporting a bare Record<string, (input) => Promise<unknown>> keyed by tool name and called from runner.ts, and (b) the same bare map called from the approve path of apps/api/tactile-api/src/routes/agent.ts; the real tree stays green; fixtures show it red on MAP[name](...), MAP[name]?.(...) and `const h = MAP[name]; h(...)` and green on tool.handler(...), an uncalled array index and a plain local function call. File: tests/architecture/single-tool-handler-path.test.ts only. Held by #698 (the file is new there): build it as a stacked follow-up on #698's head or after #698 merges; do not push to r28/single-tool-handler-guard.

Unlocks 1Add architecture test guarding against a second tool-handler implementation

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

**Add rule E to the single-tool-handler-path test: a handler map keyed by tool name must go red (follow-up to #698, t_27dbb775)** · done

Done when: tests/architecture/single-tool-handler-path.test.ts has a rule E that goes red on (a) a new packages/agent-core/src module exporting a bare Record<string, (input) => Promise<unknown>> keyed by tool name and called from runner.ts, and (b) the same bare map called from the approve path of apps/api/tactile-api/src/routes/agent.ts; the real tree stays green; fixtures show it red on MAP[name](...), MAP[name]?.(...) and `const h = MAP[name]; h(...)` and green on tool.handler(...), an uncalled array index and a plain local function call. File: tests/architecture/single-tool-handler-path.test.ts only. Held by #698 (the file is new there): build it as a stacked follow-up on #698's head or after #698 merges; do not push to r28/single-tool-handler-guard.

Where it sits: TacTile › Launch TacTile › MCP surface

## Unlocks 1

- Add architecture test guarding against a second tool-handler implementation

## The brief on file

[2026-10-23 · Viv] DONE (r40, 03:56 PDT) against draft PR #790 (r40/stack-698-rule-e-v3, head 45518c48, stacked on #698 r28/single-tool-handler-guard; not merged, not deployed; no CI on a non-main base, the local gate is the check).
WHAT: commit 30635218 rule E in tests/architecture/single-tool-handler-path.test.ts only; #698's branch untouched.
EVIDENCE: Acceptance found that rule E missed a destructured entry: `const { run } = T[key]; run(input)` passed (G1, G3, G4), but the header said E sees a lookup that a const is initialised from. Fix: in nameKeyedDispatch, viaLookup now climbs from a BindingElement to its VariableDeclaration, so whole, renamed, array and nested patterns are all caught. isKeyedLookup also looks through `await`. Header E and the cannot-see bullet now say 'bound whole or destructured'. The cannot-see list now covers, in general terms, a lookup 'wrapped in anything but parentheses, await, !, as, satisfies or <T> before the call'. New fixtures: destructured red, `await` ...
READERS (second fix round, independent): safety CONFIRMED (Judged against hub to-do steps (1)-(4): - (1) MET. The stack sits on #698's head 3f8c44a4, which is an ancestor of both new commits. r28 is untouched on the remote, and no r40 branch is pushed. - (2) MET. - Rule E is ...); acceptance CONFIRMED (Judged against the hub to-do steps (1) to (4), read with hubnote get. The task has no literal Done-when line. (1) MET. The work is stacked on #698's head 3f8c44a4, which is an ancestor (rc=0), in a fresh worktree. r28/single-tool-handler-guard is untouched: ls-remote shows it still at 3f8c44a4, a...).
GATE: run 3 passed 55 of 56 (sanctioned verify:secrets-rotation only). Run 1 failed for missing node_modules in a fresh worktree; run 2 failed only at the known ts-source-coverage SIGSEGV flake, which passed alone (logs ~/TacTile-dev/evidence/r40/gate-s698-v3-run*.log).

[2026-10-15 · Viv] Context: r32 verify of #698 (head 3f8c44a4) found two mutations that stay green: a bare name-keyed handler map in agent-core called from runner.ts (84/84 pass), and the same map in the route's approve path (84/84 pass). A draft fix exists: ~/TacTile-dev/evidence/r32/verify-698-712/rule-E-draft-pin.patch (applies to the #698 version of the test file; patched copy single-tool-handler-path.test.ts.with-rule-E-draft beside it; harness mut698.sh and pin698.py, logs v698-mut-*-with-ruleE.log). It adds nameKeyedDispatch(raw, fileName): flags a call whose callee (after unwrap) is an ElementAccessExpression, or an identifier whose every declaration is initialised from one, over packages/agent-core/src and apps/api/tactile-api/src/routes/agent*. Real tree: zero hits, 87/87. Mutations a2 and a9 go red; a1, b1, b2 stay red. To do: (1) wait for #698 to merge or stack on its head in a fresh worktree off it (never commit to r28/single-tool-handler-guard); (2) re-apply the draft, add the rule E line to the file header and to the "cannot see" list what remains (Map<string, fn>.get(name)(...), Object.values(map), a function table built at runtime); (3) re-run the six mutations in the harness with and without the rule, keep the logs; (4) pnpm verify:arch, gate, draft PR. Then t_27dbb775 can close on that 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

MCP surface

Add rule E to the single-tool-handler-path test: a handler map keyed by tool name must go red (follow-up to #698, t_27dbb775)