Lane D R21 (v4.0-beta close): relocation verify — A's venue cluster bias PASSES (ledger #4)

Verified A's venue cluster-adjacency bias (110c828), assigned from my R20 relocation
finding. selfcheck ALL GREEN 154141/154141 against A's re-pinned goldens.

ACCEPTANCE PASSES ON ALL FIVE (no venue with <3 shops in its 160m radius):
katoomba min 9 | newtown min 5 | bendigo min 5 | castlemaine min 4 | fremantle min 3.
Castlemaine's floor did NOT need an exemption.

MY HEADLINE FINDING IS CLOSED: katoomba's pub — "a gig with no passing crowd", 1 shop
at 1007m — now sits at 466m with 9 shops. Newtown is the dramatic fix: all three venues
were 2.2-2.4km out with 0-1 shops; its rsl now sits 29m from the hub with 11.

THE CROWD FOLLOWED (katoomba pub, same density/seed/21:00): passing crowd 34->66 (2x),
patron checks 226->442 (2x), inside frames 1042->1424, roster 2->3, 0 NaN.

TWO READINGS THAT NEED CARE:
- fremantle is the weakest pass: pub/rsl clear the >=3 bar but moved FURTHER from the
  primary hub (969->1352m, 561->1292m) — A's bias optimises local cluster adjacency and
  they found a secondary cluster. Letter satisfied, crowd healthy (pub roster 6, inside
  2741), so not a miss — just named. A's call if they want it tighter.
- venue-win % DROPPING is not a regression (newtown rsl 100%->21%). It was only 100%
  because the venue was alone; post-bias it has neighbours competing for finds while
  total crowd rose. Isolation flatters that metric — ignore it post-bias.

D->F: relocation verify GREEN, no gate concern for v4.0-beta.
FYI F: selfcheck scans every towns/*.json on disk incl. E's UNTRACKED pack WIP — I saw
it transiently RED (newcastle_real, no open-late shop) then green minutes later. If you
gate while E is mid-fetch you may catch a false red; check if a failure is a pack town.
Still filed for v4.x: GIG_RANGE 34m radius vs single-chunk lookup (8.7% chunk-blind).
Flagged as unowned: R20's main-street relocation half (hero strip vs densest cluster).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/LANES/LANE_D_NOTES.md

@@ -6,6 +6,66 @@ _rotOnly/head-bone normalize/upgradeStreetPeople). Measurements on the M3 Ultra
 
 ---
 
+## ROUND 21 — v4.0-beta CLOSE: relocation verify (ledger #4)
+
+*PROCITY-D, 2026-07-16. Verifying A's venue cluster-adjacency bias (`110c828`), which Fable assigned from
+my R20 relocation finding. `selfcheck` **ALL GREEN 154141/154141** against A's re-pinned goldens.*
+
+### Verdict: A's bias PASSES acceptance on all five — my finding is closed
+Acceptance was "no venue sits with <3 shops in its 160 m radius." Shops within 160 m @ distance-to-retail-hub,
+before (R20) → after (R21):
+
+| town | min shops in 160 m | before → after |
+|---|---|---|
+| katoomba_real | **9** PASS | **pub 1→9 @1007→466 m** · rsl 10→12 @161→148 m · band_room 7→10 @181→161 m |
+| newtown_real | **5** PASS | **rsl 1→11 @2228→29 m** · band_room 0→7 @2433→124 m · pub 0→5 @2190→714 m |
+| bendigo_real | **5** PASS | rsl 0→10 @451→86 m · band_room 0→10 @1157→96 m · pub 1→5 @504→316 m |
+| castlemaine_real | **4** PASS | pub 1→5 @223→182 m · band_room 6→6 @0 m · rsl 4→4 @155 m |
+| fremantle_real | **3** PASS* | band_room 2→8 @612→309 m · *pub 1→3 @969→**1352 m*** · *rsl 2→3 @561→**1292 m*** |
+
+**My R20 headline is fixed**: katoomba's pub — "a gig with no passing crowd", 1 shop at 1007 m — now sits at
+**466 m with 9 shops**. Newtown is the dramatic one: all three venues were **2.2–2.4 km out with 0–1 shops**;
+the rsl now sits **29 m from the hub with 11**. Castlemaine's floor did NOT need an exemption (min 4).
+
+### The crowd followed — katoomba's pub, same density/seed/21:00
+| | R20 (pre-bias) | **R21 (post-bias)** |
+|---|---|---|
+| passing crowd (maxActive) | 34 | **66** (2×) |
+| patron checks | 226 | **442** (2×) |
+| inside frames | 1042 | **1424** |
+| tonightRoster | 2 | **3** |
+| NaN | 0 | **0** |
+
+The "gig with no passing crowd" observation is retired. (null % stays ~96 % at 21:00 — retail is shut at night
+**by design**; that's my own R20 correction, not a leak.)
+
+### Two readings that need care (so nobody mis-reads my own numbers)
+- ***fremantle is the weakest pass** (\*): its pub/rsl clear the ≥3 bar but moved **further** from the primary
+  hub (969→1352 m, 561→1292 m) — A's bias optimises **local cluster adjacency**, and fremantle's venues found
+  a *secondary* cluster. It satisfies the letter of acceptance and the crowd is healthy in practice (pub:
+  roster **6**, inside **2741**, maxActive **72**), so I'm **not** calling it a miss — just naming it, since
+  "3 shops at 1.3 km" is a thinner high street than katoomba's "9 shops at 466 m". A's call if they want it tighter.
+- **venue-win % DROPPING is not a regression.** newtown's rsl went 100 %→**21 %**, fremantle's pub 100 %→62 %.
+  That metric asks "when a check finds a shop, is it the venue?" — it was only ever 100 % because the venue
+  was *alone*. Post-bias the venue has real neighbours competing for finds, while total crowd went **up**
+  (newtown rsl: roster 3, inside 1873, maxActive 55). Isolation flatters that number; ignore it post-bias.
+
+### Handshakes
+- **D → F (gate):** relocation verify **GREEN**. All five towns pass A's acceptance, the pub finding is closed,
+  0 NaN at every venue, rosters populate. No D-side gate concern for `v4.0-beta`.
+- **FYI F:** `selfcheck` scans **every** `web/assets/towns/*.json` on disk, including E's *untracked* pack WIP.
+  I saw it transiently RED mid-round (`newcastle_real`: no open-late shop) purely from E's in-flight files, then
+  green again minutes later at 154141 checks. If you gate while E is mid-fetch you may catch a false red —
+  E's pack is non-gating, so check whether a failure is a pack town before believing it.
+- **Still filed for v4.x (agreed, not a mid-beta change):** `GIG_RANGE` is a 34 m radius but `_nearestOpenShop`
+  searches only the ped's own 64 m chunk → 8.7 % of in-range peds are chunk-blind. Fix = chunk + 8 neighbours.
+- **Unowned from R20:** the *main-street* relocation half (heroes 0–19 % of the densest cluster; castlemaine's
+  main street has zero secondhand shops). E's R20 SUBTLE guardrails (texture capped at 3× heroes) address the
+  ratio town-wide; whether the **hero strip is again the densest cluster** is unverified. Not in my R21 ledger —
+  flagging it so it doesn't get lost at the epoch close.
+
+---
+
 ## ROUND 20 — v4.0-beta THE FIVE TOWNS: citizens at density (ledger #7)
 
 *PROCITY-D, 2026-07-16. Part 1 of 2: the **pre-density baseline** — the gig crowd's behaviour on all five