feat(recall): organize generated insights and quality - #1367
Conversation
Recall now has a corpus management surface while generated reports remain mixed with deterministic quality analytics. Define the route, capability, component, scope, and documentation boundaries before implementation so the split preserves saved-report access and removes hidden filter coupling.
The initial design left request context, route fallback, capability derivation, and panel-state lifetime open to interpretation. Make those contracts explicit so implementation preserves local date bucketing, existing read-only behavior, and user scope across tab switches.
Route parsing cannot establish whether an insight exists before the archive loads. Base tab selection on parameter presence so routing is deterministic, then leave parsing and lookup to report selection.
Keep durable context and generated reports together under Recall, with explicit report scope that survives tab changes and deep links. Move deterministic session signals to Quality so model-written output is no longer mixed with measured facts.
The approved design has been implemented and verified, so keep the durable product documentation under Recall and Quality instead of retaining the temporary working spec.
roborev: Combined Review (
|
Keep the Recall split isolated from shared session state and preserve the metadata users rely on when reviewing saved reports. Align browser coverage and docs fixtures with the new Recall and Quality destinations so the shipped routes and published assets stay in sync.
roborev: Combined Review (
|


/insightsroute is a clean break and falls through to Sessions.