Composition notes

• Question: which sessions, out of everything on record, need a look this week? Sessions has no listing page before this cycle — only single-session detail existed. w.sessions is already a recent sample (last 7 days plus the four scenario sessions — see world/types.ts's doc comment), so the roster is every session with no further date-windowing; the header is labelled "sessions · 7d sample" rather than "sessions · 30d" so it never overstates what's on record.
• Cost/volume + named flags lead the header deliberately mirroring Teams' pattern (c89's cross-page consistency goal): a stat pair (session count against the honest window, then cost with tokens in the sub) plus a named list of flagged sessions — person + a short reason + a link straight to the receipt — capped at 5 with an overflow note, same shape as teams-v3's attention list. No donut ring here: unlike coverage (a fraction of a known denominator), "how many sessions happened" has no natural whole to divide by, so a ring would manufacture a denominator that doesn't exist.
• One attention device: a row is flagged exactly when sessionReceipt(w, s).attention is non-null — never re-derived, always read from session-detail.ts's one source of truth. Violations rank above a runaway-cost flag (rank tiers in derived/sessions.ts's sessionRoster), and the verdict goes warn only when at least one flagged session is a policy violation, else attention — the same tone hierarchy as elsewhere on phase1.
• No per-page expand: rows link straight to the existing Session detail "receipt" altitude (c77's four-altitude ladder) instead of duplicating any of it in an expand panel — session-detail.vue already owns chapters, transcript, raw events, and the actor web; a second copy here would drift. The whole row is clickable (DataTable's onRow); cells stay non-interactive (no nested links) so a click always lands on one destination, not a race between row-click and a chip's own link.
• Table is the layer's DataTable (plain rows, no #details slot) rather than the raw UxTableList family Teams uses — Sessions has no ?id= pre-open requirement and no per-row expand, so the higher-level component is the right altitude (see teams-ideas-v7.vue for the same idiom on a roster). Columns: person (avatar + name), team, agent (logo), started, duration, tokens, dollars (amber when it's the runaway flag), model(s) as un-linked entity chips (avoiding the same row-click/chip-click race), outcome as a pill carrying the flag reason or "clean".
• Derivation: every number traces to sessionRoster / sessionsBand / sessionsVerdict in derived/sessions.ts, built on sessionReceipt and sessionIncidents from session-detail.ts and derived.ts — nothing hand-typed. sessionsVerdict is deliberately NOT folded into derived.ts's central verdicts map yet (out of scope for a first pass); see teams.ts's teamsVerdict for what that folding looks like once this page reconciles.
• Open: this is net-new scope with no Linear issue yet — the page, its route, and its registry entry exist only in page-registry.ts (phase1-registry.ts's PRO-19…35 plan is untouched, per c89's scope). No per-team or per-agent rollup strip is included (a deferred fast-follow, not this pass) — global/generic filtering is c88.global-filter's territory, so this page has no local filter chips either, unlike Teams' team strip (which predates c88 and stays as page-local precedent).