Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Inbox — on deck·56 in this wave

Wave

Inbox — on deck

Briefs Nova has teed up and are ready to run — each task's prompt is a complete, self-contained brief.

TacTile › Inbox — on deck

44/56 done12 open2 open blockers

Selected taskclear

Merge-order trap: #759's migration-order rule 3 flags open PRs whose migration sorts before main's newest (202610052300); #699 first

To doOwner · Vivt_013f5f47

PR #759 (c05709c4) adds tests/unit/supabase-migrations-order.test.ts. Rule 3 requires every migration a PR adds to sort after the newest one at the merge-base (main today: 202610052300_revoke_anon_resolve_trigger_destination.sql). Six open PRs add older-dated migrations, including #699 under the #702 stack. Found by the r32 safety reader of t_3ef8ebe2.

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

**Merge-order trap: #759's migration-order rule 3 flags open PRs whose migration sorts before main's newest (202610052300); #699 first** · to do

PR #759 (c05709c4) adds tests/unit/supabase-migrations-order.test.ts. Rule 3 requires every migration a PR adds to sort after the newest one at the merge-base (main today: 202610052300_revoke_anon_resolve_trigger_destination.sql). Six open PRs add older-dated migrations, including #699 under the #702 stack. Found by the r32 safety reader of t_3ef8ebe2.

Where it sits: TacTile › Inbox — on deck

## The brief on file

[2026-10-15 · Viv] DECISION (NEEDS MATTHEW, merge order only): land #699, and any of #654, #659, #662, #737 you mean to ship, BEFORE #759, or have each re-timestamped later than 202610052300.
RECOMMEND: order only. Merge #699 first (it carries the #702 stack), then #759. Re-timestamp only what is still open when #759 lands.
IF YES, NEXT: you merge in that order. For anything left behind I cut a NEW branch off that PR's head with the migration renamed to a timestamp after main's newest, re-run the gate and open a replacement PR; I do not touch the r28 or older branches.
COST IF YES: none beyond the order. A renamed migration changes its version, so supabase/migrations/RECONCILIATION.md must agree; none of these migrations is applied anywhere.
COST IF NO: #759 merges first and each affected PR goes red at supabase-migrations-order until it is re-timestamped. No data effect.
SAFE TO ASSUME: nothing merges, migrates or deploys without you; every migration named here is DRAFT - NOT APPLIED.

DO NOT RUN until Matthew names the order (the r28 and older branches are not mine to edit).

CONTEXT (read 15 Oct 22:50, nothing run): #759 head c05709c4, tests/unit/supabase-migrations-order.test.ts header lines 29-32: "Every file ADDED since the merge-base with the base branch sorts after the newest file present at the merge-base", versions of different width compared right-padded to 14 digits. origin/main 4f2c1d6b newest migration is 202610052300_revoke_anon_resolve_trigger_destination.sql. Files ADDED (git diff --diff-filter=A origin/main...head) by open PRs that sort below it: #699 202610020410 (MERGEABLE; under #702 / t_3ef8ebe2), #662 and #659 202609291200 (MERGEABLE), #737 202609292210 (MERGEABLE; its three 2026100821xx files are fine), #655 202609300100 (CONFLICTING), #654 202609292210 (CONFLICTING). #735 adds 202610082330, which is fine. The rule only looks at files added since the merge-base, so a PR that has already merged is not flagged. I read the rule and did not run the test against any of these heads.

DONE WHEN: Matthew has named the order, or every affected PR still open has its migration later than main's newest, or has merged, with supabase-migrations-order passing on its head. No push to anyone's r28 or older branch.

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

Inbox — on deck

Merge-order trap: #759's migration-order rule 3 flags open PRs whose migration sorts before main's newest (202610052300); #699 first