Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Backend & Infrastructure›Custom Domains·7 in this wave

Approve: Custom DomainsTo do · blocker Verify whitelabel.tactile.to DNS + routingDone Run cf-saas-smoketest.sh in stagingTo do Verify CF_API_TOKEN + CF_ZONE_ID at worker bootTo do Set up DNS for whitelabel.tactile.toDone Train ops team on white-label runbooksTo do Add 2-hour polling timeout fallback UXTo do

Wave

Custom Domains

White-label URLs for customers. Depends on Backend API.

TacTile › Launch TacTile › Backend & Infrastructure › Custom Domains

2/7 done5 open1 open blocker

Selected taskclear

Run cf-saas-smoketest.sh in staging

To doOwner · Vivt_53fda8d4

Waiting on 1 · all clearVerify whitelabel.tactile.to DNS + routing

Unlocks 1Approve: Custom Domains

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

**Run cf-saas-smoketest.sh in staging** · to do

Where it sits: TacTile › Launch TacTile › Backend &amp; Infrastructure › Custom Domains

## Waiting on 1

- Verify whitelabel.tactile.to DNS + routing — done

## Unlocks 1

- Approve: Custom Domains

## The brief on file

Viv — prove the Cloudflare-for-SaaS custom hostname flow works end to end in staging. Done when: cf-saas-smoketest.sh runs green against staging, covering add hostname → DNS verification → certificate issuance → serving a real scan on that hostname → removal. WHY THIS IS THE GATING TEST FOR THIS WAVE: custom domains are the Pro tier's headline feature and the flow crosses four systems — your API, the Cloudflare SaaS API, the customer's DNS, and certificate issuance. Any one of them failing produces a customer-visible broken domain. Note this depends on staging actually being live, which is itself an unverified item in DevOps Foundation — so confirm staging first. Files: the cf-saas-smoketest.sh script, apps/api/tactile-api/src/utils/customDomainHealth.ts

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

Custom Domains

Run cf-saas-smoketest.sh in staging