Ship the session list pilot to production and write the pattern down

## Question

Turn the validated prototype into merged production code — the map's destination.

1. Bring the prototype to production quality: the amended contract applied cleanly, `bash scripts/verify.sh` green, tests covering the refetch paths and the not-connected fallback.
1. Open the PR (stacked if it splits naturally — e.g. a router-version bump separate from the page change), body carrying `Resolves #N (FR-N)` and the measured before/after from FR-3642.
1. Take it through `fw:pr-ready-gate` (Copilot first, then human review), then merge.
1. **Write the pattern down** where the next person will find it: a rule under `.claude/rules/` covering when a page's first query belongs in a route loader, the disposal and refetch-ownership rules, the not-connected fallback, and the traps the prototype hit. This is what makes the pilot a direction rather than a one-off.

Done when the PR is merged and the rule is in the tree.

Map: FR-3636.

JIRA Issue: FR-3643

Start with the validated session-list prototype and the amended contract, then run bash scripts/verify.sh to establish the current state. Check the refetch paths and not-connected fallback, and document the route-loader, disposal, and refetch-ownership rules in .claude/rules/. Done means the production PR is merged and the rule is in the tree.

Written by the indexing model from the issue text.