light-entry¶
Provenance¶
- Source:
.spec/spexcode/spec-dashboard/dashboard-ui/review-surfaces/review-chrome/light-entry/spec.md - Source SHA-256:
25390dbd38295abea85a471f83b3d9e77c508edf803d6f86b8b0cf4bcedf77d8
light-entry¶
An external Evals LIST or DETAIL link, or a top-level Issues LIST link, is a review page before it is a
dashboard visit. The root route selector resolves and normalizes the hash before importing the board runtime.
A canonical #/evals or
#/evals/<node>/<scenario> address and its legacy session-scoped spelling both mount the SAME
[[evals-view]] components behind a small responsive shell; canonical #/issues mounts the SAME
[[issues-view]] list there. There is no second renderer, data projection, or URL vocabulary.
The cold review boundary may request one bounded [[paged-review]] page or detail response, its evidence, and
route-local review resources. It does not fetch /api/graph, open [[graph-stream]], read a session
collection/timeline/detail, open a session terminal socket, or import graph/terminal chunks. Desktop keeps
the ordinary [[side-nav]] rail. Phone width reuses [[mobile-ui]]'s review face and bottom navigation over an
empty board projection, so responsive chrome does not become a reason to boot the board.
Navigation owns initialization. Following a real anchor from the review shell to the graph, session, issue detail, or settings route swaps in [[dashboard-shell]]'s ordinary App runtime; only then do graph freshness, session summaries, and any visited terminal transport begin. A node reference preserves its intended graph focus through the existing tab-scoped focus key. Once started in a tab, App stays mounted across later route changes exactly as before: graph camera and visited terminal warmth survive a return to Evals, and the lightweight entry is not re-entered until a genuinely new cold tab/reload starts at a detail address. This node changes no route shape and weakens no detail loading/error/evidence behavior; it only decides which runtime is allowed to exist for that address.
The root still mounts [[transient-notices]] around both runtime choices. That provider is chrome only: a lightweight review entry can acknowledge its own completed write without importing the board, while mounting it does not fetch graph data, open a transport, or change the cold-route boundary above.