Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Foundations›Database & Supabase·15 in this wave

Verify point-in-time recovery is enabledTo do · blocker Review anon-executable SECURITY DEFINER functionsDone · blocker Approve: Database & SupabaseTo do · blocker MATTHEW: profiles.visibility is nullable with no default, so any profile created without it reads as publicBlocked · blocker The RLS fixture expires 2026-09-30 and freezes main — only Matthew can refresh it (Touch ID)Done · blocker Fix v_account_tier security-definer viewDone Fix allow-all RLS policy on checklists tableDone URGENT: 202608081500_guard_analytics_rpc_callers.sql is merged to main and NOT applied to productionDone db_url and db_password now EXIST in 1Password — verify:rls-snapshot can run for the first timeTo do RLS snapshot fixture turns pnpm verify red for every branch on 5 Nov (30-day age limit)To do Hardware-ready data modelDone Document Supabase backup policyBlocked Document RLS test planDone Soft-deleted public destinations stay readableDone Confirm scan-event logging is rate-limited per destinationDone

Wave

Database & Supabase

Schema is already built (81 tables, 114 migrations, RLS on every table). This wave is the readiness pass plus three real gaps a live audit surfaced.

TacTile › Launch TacTile › Foundations › Database & Supabase

9/15 done6 open3 open blockers

Selected taskclear

RLS snapshot fixture turns pnpm verify red for every branch on 5 Nov (30-day age limit)

To doOwner · met_1b6f55fd

tests/unit/rls-cross-tenant.test.ts fails verify:unit when tests/fixtures/rls/policy-snapshot.json is more than MAX_FIXTURE_AGE_DAYS (30) old. main's copy was generated 2026-10-06T19:09Z, so from about 5 Nov 2026 every gate.sh run and every CI verify fails on main and on every branch. Branches cut before 6 Oct already fail it today (r45 saw this on #795: 35 days).

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

**RLS snapshot fixture turns pnpm verify red for every branch on 5 Nov (30-day age limit)** · to do

tests/unit/rls-cross-tenant.test.ts fails verify:unit when tests/fixtures/rls/policy-snapshot.json is more than MAX_FIXTURE_AGE_DAYS (30) old. main's copy was generated 2026-10-06T19:09Z, so from about 5 Nov 2026 every gate.sh run and every CI verify fails on main and on every branch. Branches cut before 6 Oct already fail it today (r45 saw this on #795: 35 days).

Where it sits: TacTile › Launch TacTile › Foundations › Database & Supabase

## The brief on file

[2026-10-28 · Viv] DECISION (PRODUCTION read, SELECT-only on the catalog, no writes): may Viv run `pnpm verify:rls-snapshot --write` against production through the aws-1-us-west-1 pooler, in a worktree off origin/main, and ship the refreshed fixture as a draft PR?
RECOMMEND: yes, before 5 Nov. After that, every gate and every CI verify is red on main and on all 140 open branches. That would hide real reds, and the only merge gate becomes useless.
IF YES, NEXT: Viv refreshes the fixture, deletes any KNOWN_* entry the refresh shows is fixed, gates, and opens a draft PR. Merge it first among the iOS/web PRs.
COST IF YES: one read of pg_policies and grants. No data rows are read.
COST IF NO: from 5 Nov, either the gate is red everywhere or the age limit gets raised by hand (which hides drift).
SAFE TO ASSUME: no. This is a production read, and the loop's hard limits reserve it for you.

Found by r45: the gate on #795 (5459a436) went red on this test because the branch carries the 23 Sep fixture from its old base. Evidence: the gate log in the r45 EXECUTION-LOG entry.

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

Database & Supabase

RLS snapshot fixture turns pnpm verify red for every branch on 5 Nov (30-day age limit)