# Rank activities by sequence, scope the seed guard, unify the probes · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/6045ce23d0bd5a51b1a65ed9c5aeb42ca9050312)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 6045ce23d0bd5a51b1a65ed9c5aeb42ca9050312

Requested commit: 6045ce23d0bd5a51b1a65ed9c5aeb42ca9050312

Commit: 6045ce23d0bd5a51b1a65ed9c5aeb42ca9050312

Tree: 6256c0dd50b438763a2ff9e73f065e14538ac595

Author: Theo Browne

Committer: Theo Browne

## Message

```
Rank activities by sequence, scope the seed guard, unify the probes

Two Cursor Bugbot findings on the merge, plus the simplification they
enabled:

- The activity cap ordered `created_at` before `sequence`; the app ranks
  `sequence` first. The keys disagree outright under clock skew — a
  higher-sequence activity can carry an older timestamp — and then the
  cap keeps rows the timeline treats as oldest. Reordered to match, with
  the regression test now covering a skewed row, not just a tied one.
- The running-server guard blocked on a live server in either state
  directory while the seed touches exactly one. A server using only the
  other directory's database now no longer refuses the seed; both the
  pre-copy check and the pre-commit re-check take the resolved state dir.
- Scoping the probe meant threading one rule through both variants, so
  they now share a single implementation: the sync function reads and
  checks, and the Effect wrapper just lifts it. That deletes the schema
  decoder the Effect path used, removes the duplicated parsing, and
  makes the parity the tests pin structural rather than incidental.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

```

## Parents

- [9c61dbed190d8822760952a607266dae4c73299f](https://git.cafe/pingdotgg/t3code/commit/9c61dbed190d8822760952a607266dae4c73299f?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/6045ce23d0bd5a51b1a65ed9c5aeb42ca9050312?format=markdown)