Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›DevOps·1 in this wave

Wave

DevOps

Two gates. Foundation is unblocked now and closes early. Launch Readiness is gated by the surfaces existing — Android is the long pole.

TacTile › Launch TacTile › DevOps

1/1 done0 open2 sub-waves56 incl. sub-waves

Selected taskclear

PROD INCIDENT: sign-in and sign-up are dead on tactile.to

DoneOwner · met_657e1246Blocker

tactile.to/signin and /signup render "Something went wrong". Every conversion path from the marketing site dead-ends. Cause found and fixed; the fix is on feature/web and needs merging + a prod deploy.

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

**PROD INCIDENT: sign-in and sign-up are dead on tactile.to** · done · blocker

tactile.to/signin and /signup render "Something went wrong". Every conversion path from the marketing site dead-ends. Cause found and fixed; the fix is on feature/web and needs merging + a prod deploy.

Where it sits: TacTile › Launch TacTile › DevOps

## The brief on file

LIVE PRODUCTION INCIDENT, found 2026-08-06 while running the form E2E (t_557d52d9). Fix is written and PROVEN ON STAGING; production is still broken and needs a deploy.

SYMPTOM: https://tactile.to/signin and /signup render the "Something went wrong / An unexpected error occurred" error boundary. The marketing home page renders fine, so the only visible effect is that "Start free" and "sign in" both dead-end — every conversion path on the site.

CONSOLE: "@supabase/ssr: Your project's URL and API key are required to create a Supabase client!" followed by React error #423.

CAUSE: NEXT_PUBLIC_* is inlined by Next at BUILD time. scripts/deploy/deploy.sh resolved ONLY the Cloudflare credentials from 1Password, so every OpenNext build ran with NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY unset and baked `undefined` into the bundle. createBrowserClient then throws on any page that constructs a Supabase client — /signin, /signup and every authenticated page. Deploys only ever produced a working bundle when the operator happened to have those values in their shell or a .env file.

WHY NOTHING CAUGHT IT:
· The failure is a CLIENT-side error boundary, so the server still returns HTTP 200. deploy.sh's smoke test checks the status code and passes.
· CI has never run (Actions billing wall), so no e2e ran either.
· Confirmed on BOTH tactile.to and staging.tactile.to, with different build hashes — two independent builds, same missing vars. Not a one-off bad deploy.

FIXED ON branch feature/web (PR #224), two commits:
· bbd04464 — deploy.sh resolves op://TacTile/Supabase/url and /anon_key for OpenNext units and REFUSES to build if either is empty. Both values are publishable by design (the anon key is meant for browsers); the service-role key is NOT added, and the existing artifact secret gate still scans for it.
· 57aa4858 — deploy.sh now clears .next/.open-next first. Worth knowing: the first corrected redeploy shipped the SAME broken bundle because opennextjs-cloudflare reused the cached .next — the client chunk hash did not even change, so it looked exactly like the fix had failed.

VERIFIED: after a clean rebuild, https://staging.tactile.to/signin renders the real sign-in card (Apple / Google / email). Screenshot taken.

TO CLOSE THIS: merge PR #224 and run `scripts/deploy/deploy.sh web production`. Note deploy.sh REFUSES to deploy production from a non-main branch, so the merge is a hard prerequisite — the fix cannot be shipped from the feature branch.

WORTH DOING NEXT, separately: the deploy smoke test cannot see a client-side error boundary. A one-line check that /signin contains the expected sign-in copy, or any headless load asserting zero console errors, would have caught this on the day it started.

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

DevOps

PROD INCIDENT: sign-in and sign-up are dead on tactile.to