Record corrected Route fixture and failed compilation boundary

harness/STATE.md

@@ -9,7 +9,7 @@ excluded by the user's explicit request, including after networking recovers.**
 
 ## Assembled source and acceptance boundary
 
-Combined code **a6b9f6029aad618a84d136c5293353688d36809f** adds the reviewed
+Combined code **4deced53b98cd4d7649ba7aa60fa4b9b30d2f3b8** adds the reviewed
 Connection/Route early-admission correction to the assembled Scenario/Text,
 ordinary/State/Process/Allocation selection, direct drawing, Traceability and
 picker changes. The [source handoff](prerelease-integrated-source-20260924.md)
@@ -18,7 +18,10 @@ The nine event regressions and existing completed-Text-Apply cases are retained.
 Direct formatting and whitespace checks pass; this source checkpoint does not
 claim combined Cargo, native, packaged or release acceptance. The independent
 [event-fix review](reviews/prerelease37-event-admission-20260924.md) found no
-further material source defect in its stated scope.
+further material source defect in its stated scope. A subsequent peer compile
+found a missing `projection::` qualification in the new Route test helper;
+the current code includes that one-line correction. The original compile failed
+before running tests. Combined execution remains pending.
 
 Live build, final-source and publication results belong in
 [issue37](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/issues/37).

harness/prerelease-integrated-source-20260924.md

@@ -82,6 +82,14 @@ combined execution. The vendor patch-description correction is incorporated at
 
 ## Combined gates and package handoff
 
+The first peer compilation exposed E0425 in the new Route fixture: its
+`project_view` call lacked the `projection::` qualification used by the parent
+helpers. Combined successor `4deced53b98cd4d7649ba7aa60fa4b9b30d2f3b8`
+cherry-picks peer `e68a83959900e556768d8470640e28a7df7d8cb8` to correct that
+single test line. Production code is unchanged. This concrete finding supersedes
+the earlier `9e99618c` build handoff; the failed compile ran no tests and remains
+part of the peer's evidence. Source review and formatting did not catch it.
+
 Codex-ytr83r owns the exact-candidate Windows build/package on its separate
 machine. Codex-9e8r6t owns independent source/seam review and a downloaded-package
 check. Codex-956atf remains the sole integration, tag and release publication owner.

harness/reviews/prerelease37-event-admission-20260924.md

@@ -2,6 +2,14 @@
 
 2026-09-24. Independent source review; no confirmed actionable finding in the bounded change.
 
+Parent follow-up: the later peer compile found E0425 at
+`route_lifetime.rs:40`, which this source review missed. Peer correction
+`e68a83959900e556768d8470640e28a7df7d8cb8` qualifies the call as
+`projection::project_view`; combined code `4deced53b98cd4d7649ba7aa60fa4b9b30d2f3b8`
+incorporates it. This is test-only and does not change the guard analysis below.
+The failed compile ran no tests; passing corrected execution must be recorded
+separately. The original review is retained below with its original scope.
+
 Reviewed exact delta `340a5c56b0783e22d7336a07ce96ddb7c2b79b0d..6f247af795b7bec1818c588b2dabf203f8f68d8a` (code commits `44217307`, `72b1bb7`, `6f247af`) against combined candidate `17eaa03fd69741dff746f21d150dc04c341411b3`. This is compatibility review before the parent's integration, not verification of an already integrated commit. Read AGENTS.md, App update/connection/route handlers, Allocation retirement adapter, both new regression modules, group fixtures/history evaluator, and existing combined Allocation connection regressions. Formed independent judgment before reading peer reviews at `c655c5eeaaa32c1c21074a7543844ae99a1d6fd5`.
 
 The 21-line early guards precede pending-reveal reconciliation, allocation_before, inner dispatch and post-dispatch reconciliation. The preceding preview/selection-boundary computations are reads. Connection Endpoint/Restart require both current route Context and extant matching session; Choose/Begin retain their intentional new-owner behavior. Current Restart remains admitted and creates a fresh Choose session. Route Commit/CommitAttachment require current Context and payload edge equal to current selected edge, without incorrectly demanding a Connection session or armed attachment.