Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›MCP surface·41 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 clientsTo do 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 SupabaseTo do MCP GAP INVENTORY — every unwired op, with the decision attached to eachDone Demo account for screenshots + QA — seeder is live, shape is frozenTo do Build the full medialink.* MCP tool set (3 ops)To do 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 Deploy step 1 — verify DB migration + RLS on OAuth tablesTo do 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 toolsTo do 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 toolTo do Build the full form.* MCP tool set (7 ops)Done Build the analytics automation layer MCP tools (6 ops)To do Wire inbox.list and inbox.mcp_approval to real handlersDone Add architecture test guarding against a second tool-handler implementationTo do Publish a public MCP tool manifest / discovery docsTo do 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 EXECUTEBlocked 5 proposal-only MCP ops are advertised with no task row building themTo do

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

14/41 done27 open2 open blockers

Selected taskclear

Webhook signing secret: add the one surface that can reveal it

DoneOwner · met_593955ff

Waiting on 1 · all clearSPEC → backend: webhook secret reveal/rotate endpoints + secret_fingerprint on the list

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

**Webhook signing secret: add the one surface that can reveal it** · done

Where it sits: TacTile › Launch TacTile › MCP surface

## Waiting on 1

- SPEC → backend: webhook secret reveal/rotate endpoints + secret_fingerprint on the list — done

## The brief on file

DONE — PR #253, merged to main as 5770b8e3 (ancestry verified).

Settings › Webhooks, at apps/web/features/webhooks/ + app/(app)/settings/webhooks/, with a nav entry.

BOTH GATES WERE MET THIS ROUND:
· The permission rule allowing writes under apps/web/features/webhooks/ works — the round-5 classifier block is gone.
· Backend's contract exists (t_e6d01092, in ~/TacTile-dev/TacTile-backend, uncommitted at the time of writing): POST /api/webhooks/:id/secret/reveal and .../rotate via handleSecret, returning { ok, signing_secret (64 bare hex), fingerprint, reveal_count, revealed_at } or { …, rotated_at }; 429 on rate limit, 404 for missing-or-not-yours, 500 "Could not record the disclosure, so the secret was not returned." Plus secret_revealed_at / secret_reveal_count / secret_rotated_at on GET /api/webhooks. Built against exactly that. dep_add: t_e6d01092 → this.

WHAT CHANGED SINCE THE ROUND-5 DESIGN: their lockdown migration revokes ALL privileges on webhook_configs from anon and authenticated, so the browser-PostgREST read that round 5 proved possible is now closed. The routes are the only path. lib/secretApi.ts calls them and nothing else.

ONE DELIBERATE DEPARTURE FROM THE ROUND-6 BRIEF, flagged rather than silently taken. The brief said "reveal-once semantics". Backend's migration argues that reveal CANNOT be made once-only by fiat — the secret is stored, so a second reveal is always technically possible — and that the UI must say so rather than promise it. That is correct, and a UI claiming otherwise would be lying about a security property. So the panel never claims it; it says every disclosure is counted, dated and written to the audit log. "No persistent read-back" IS enforced: the value lives in React state while the panel is open and reaches no list response, query string or storage; closing it costs another audited, counted, rate-limited POST.

Rotation gets a confirm step — it is destructive and immediate, and an endpoint still verifying with the old secret starts rejecting live deliveries.

Two footguns are on screen because both fail silently: the HMAC key is the DECODED bytes (32 from 64 hex chars), not the hex text; and the body must be verified as RAW bytes.

tests/unit/webhook-secret-surface.test.ts pins that the routes stay off the agent surface (no SDK export, no MCP source, exactly one caller in the apps), plus the two warnings and the absence of the once-only promise — an assertion that immediately caught this feature's own doc comment quoting the banned phrasing.

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

Webhook signing secret: add the one surface that can reveal it