## Census
| | column guards |
|---|---|
| before | **84** |
| after | **83** |
`moves.ts`: 2 → 1. One of its two sites converts; the other **must
not**, and that difference is the useful part of this PR.
## Converted — the move target at the same-column handoff
```ts
if (internal.fromHandoff && toColumn === "in-review")
```
Against the literal this **never fired on a renamed board**, so a
same-column handoff into a renamed review lane silently took the *other*
branch — the sync-SQLite path, which throws under PostgreSQL.
It now asks `moveReviewColumns`: the broad membership set
(`mergeOrchestration ∪ mergeBlocker ∪ humanReview`) already resolved
**three lines above** for the merge-queue pair. Same value, so this
branch cannot disagree with the enqueue/dequeue calls that receive it.
## Not converted — the archived fallback arm
I named it, and `archived-column-gate-parity.test.ts` went red on
**`TypeScript encoding changed`**.
That guard's argument holds: the archived gate is enforced in three
encodings, the SQL halves still compare the raw string, and moving the
TypeScript half alone is the split brain it exists to prevent. Restored
inline **with a note recording the measurement**, so the next person
doesn't retry it and rediscover the same red.
This is the second time that guard has stopped me this session. It's
doing exactly what it was built for.
## On the pre-existing red
That suite is red on `origin/main` for an unrelated raw-SQL drift (#3072
fixes it — the drift is from my own merged #3042/#3046). I verified this
branch produces the **identical** failure and no other, so it doesn't
compound it.
## Measured
| check | result |
|---|---|
| moves / handoff / merge-queue suites | green |
| four gates + strict census | green |
| core `tsc` | clean |
| parity suite | same single raw-SQL failure as `origin/main`, nothing
added |
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
6949f22ef8