guides: address rev-code-01's review of #1313 (B1, B2, S1, S2)

All four findings reproduced before fixing. rev-code-01 was right on each.

B2 (blocker, mine). SEAT-IDENTITY provisioning step 4 said to symlink the
framework store entry to the seat slot, while the same file says those bridges
must not be recreated. The same bridge, told both ways, in one document. I
rewrote the resolution and token-location sections when the deploy made them
stale and did not carry the change into the numbered steps. Step 4 is gone and
the file now says explicitly that no provisioning step links the store to the
slot, so the omission cannot read as an oversight.

S1 (mine). The guide claimed the helper "attempts a fleet notification" on
refusal. The shipped helper does no such thing — its only reference to
notification is a comment saying an alert built on the record is best-effort, and
there is no send or wake call anywhere in the file. Now: it writes a durable
record, the record is what exists, and nobody should wait for a notification that
nothing sends. A guide that promises an alert is worse than one that promises
nothing.

S2. Estate-local content removed from files that ship to every estate: the
~/.mosaic/fleet/bin script paths (dead paths elsewhere) and the 2026-08-18 dates,
which dated a specific host's migration rather than describing behavior. The
bridge-removal passage now states the ORDERING that matters — remove bridges only
after a seat-aware helper can reach the slot, never before — which is the part
that transfers.

B1. prettier reformatted all three files. Reproduced the pipeline 2515 failure
locally before and confirmed clean after; the other three guides prettier flags
are untouched by this branch (0 changes vs origin/next) and are pre-existing.

Sanitization gate re-run and passing.

Verified for the record, since I could not verify my own work: rev-code-01
confirmed the no-fallback claim TRUE against helper content on origin/next, and
judged the evidence rules actionable on the grounds that each names an executable
replacement.

packages/mosaic/framework/guides/CODE-REVIEW.md

@@ -48,7 +48,7 @@ you saw. Every rule here was earned by a wrong conclusion that reached a report.
 
 ### Measuring a shell suite
 
-Earned on mosaicstack#1311, 2026-08-18. Each of these produced a wrong conclusion first.
+Each of these produced a wrong conclusion before it was written down.
 
 9. **`cmd | tail; echo rc=$?` reports `tail`'s exit code, not `cmd`'s.** It reads as a pass when
    the command failed. Redirect to a file and check `rc` directly, or use `${PIPESTATUS[0]}`.
@@ -78,16 +78,15 @@ Reviewer seats split this checklist by class rather than duplicating it. A seat
 sections in full and may raise anything it notices outside them as a Suggestion, never as a
 Blocker on someone else's ground.
 
-| Reviewer class | Owns |
-|---|---|
-| `rev-code-*` | 1 Correctness, 3 Testing, 4 Code Quality, 4a TypeScript, 5 Documentation, 6 Performance, 7 Dependencies |
-| `rev-security-*` | 2 Security, 2a OWASP |
+| Reviewer class   | Owns                                                                                                    |
+| ---------------- | ------------------------------------------------------------------------------------------------------- |
+| `rev-code-*`     | 1 Correctness, 3 Testing, 4 Code Quality, 4a TypeScript, 5 Documentation, 6 Performance, 7 Dependencies |
+| `rev-security-*` | 2 Security, 2a OWASP                                                                                    |
 
 Where two seats of the same class review the same change, they review independently and compare
 after. A second seat that reads the first seat's findings before measuring is a proofreader, not
 a second opinion.
 
-
 ### 1. Correctness
 
 - [ ] Code does what the issue/PR description says