Pin executing groups and guard lazy loads by core contracts
This commit is contained in:
@@ -30,3 +30,14 @@ background-group synchronization commit f804a23; ordered build-local loader with
|
||||
unit tests (not yet wired into index.html). No layout or feature was removed
|
||||
from the current eager path. Full browser/layout/performance acceptance remains
|
||||
outstanding. This is a QUESTION checkpoint, not a completed phase report.
|
||||
|
||||
## Accepted owner decision
|
||||
|
||||
The owner accepted pinning on 2026-10-08. Already executing stale groups remain
|
||||
pinned until their session ends or the next explicit playback-guarded reload.
|
||||
P2P/direct and other stateful instances are never re-evaluated live; Phase 4 must
|
||||
add disposal/state handoff before permitting replacement. An unexecuted group
|
||||
may use newly cached URLs only when its contract equals the running core's
|
||||
embedded contract. A different contract keeps the running build's N-1 URLs,
|
||||
marks reload required and prompts the existing build-tag-based Refresh UI banner.
|
||||
Unit tests cover all three cases. Continue Phase 3 under these rules.
|
||||
|
||||
Reference in New Issue
Block a user