docs(runtime): record reveal ownership gate

docs/architecture/acdream-architecture.md

@@ -238,7 +238,10 @@ src/
       RuntimeOrdinaryPhysicsUpdater.cs -> presentation-free object simulation
       RuntimeProjectile.cs -> canonical projectile component/prediction owner
       RuntimeProjectilePhysicsUpdater.cs -> presentation-free projectile simulation
-    -> J3–J5 complete; J6 world/portal/environment handshake active
+    World/
+      RuntimeWorldEnvironmentState.cs -> canonical calendar/time/weather owner
+      RuntimeWorldTransitState.cs -> canonical reveal generation/readiness owner
+    -> J3–J5 and J6.1–J6.2 complete; J6.3 transit handshake active
     -> may reference Core, Core.Net, Content, and Plugin.Abstractions only
     -> must never reference App, UI, Silk.NET, OpenAL, Arch, or ImGui
   
@@ -281,8 +284,8 @@ src/
     Streaming/
       StreamingController.cs  -> done
       GpuWorldState.cs        -> done
-      WorldRevealCoordinator.cs -> shared login/portal lifetime owner
-      WorldRevealReadinessBarrier.cs -> canonical destination predicate
+      WorldRevealCoordinator.cs -> graphical host/reveal projection adapter
+      WorldRevealReadinessBarrier.cs -> graphical destination-readiness source
     Input/
       PlayerMovementController.cs  -> active movement driver
     Plugins/
@@ -865,12 +868,21 @@ The Slice E connected closeout is recorded in
 
 ### World-reveal readiness ownership
 
-`WorldRevealCoordinator` is the single App-layer owner of each login or portal
-reveal lifetime. It composes the canonical `WorldRevealReadinessBarrier` with
-generation-scoped lifecycle observation and the streaming destination
-reservation plus a generation-scoped render-resource profile, so begin,
-preparation, readiness, materialization, viewport release, protocol completion,
-cancellation, and reserved capacity cannot be wired independently. While the
+`RuntimeWorldTransitState` is the single presentation-independent owner of
+each login or portal reveal generation. It owns the exact destination, typed
+atomic readiness latch, materialization/simulation edge, viewport observation,
+completion, cancellation, retail wait cue, and portal materialization count.
+Stale generations, wrong destinations, invalid readiness shapes, reordered
+edges, and post-cancel acknowledgements cannot mutate the active generation.
+Once readiness is accepted it remains latched; later sampled graphical
+readiness may fall as resources transition without closing the accepted edge.
+
+`WorldRevealCoordinator` is the graphical host adapter. It evaluates App's
+`WorldRevealReadinessBarrier`, acknowledges that typed result to Runtime, and
+owns only the streaming destination reservation, render-resource profile,
+selection/audio projection edges, and viewport release. App's former lifecycle
+telemetry/generation owner is deleted and
+`WorldGenerationAvailabilityState` is a read-only Runtime projection. While the
 normal world viewport is withheld, mesh and composite upload owners may admit
 more small destination items per frame, but retain the ordinary 8 MiB byte,
 array, buffer, and mipmap ceilings. The exact profile ends at the retail