feat(web): choose the agent preset on the new-session screen

The composer seat spent nearly all its life disabled: a session's
composition is fixed once a turn has run. Move the choice to the
new-session screen beside the workspace picker, where it still works,
and let the session header report what a running session runs.

The hero pick is staged rather than applied — that screen precedes the
session it belongs to. It lands when a session becomes current and is
still blank, which covers both the session a workspace connect creates
and the blank one it reuses; riding `sessions.create` would miss the
second. It is spent on first use, matching the workspace picker.

Fix the durability the header field claimed but never had: `agentPreset`
was declared on `SessionHeader` and dropped by the JSONL header line, the
SQLite sessions row, the derived query index, and the cold list
projection, so every resumed session came back composed from nothing.

Add the web e2e lane that would have caught it — the one lane that mounts
the shipped roster, which needed `cordis:group` in the scaffold's Loader
builtins, as `mountRootInclude` already registers.

packages/client/runtime/src/client/sessions/service.ts

@@ -47,8 +47,8 @@ export interface SessionSummary {
   cwd?: string
   /**
    * Agent preset this session's agent was composed from; absent when the
-   * deployment composes no presets. A composer seat shows what the session
-   * actually runs rather than the deployment's current default.
+   * deployment composes no presets. The session header labels what the
+   * session actually runs rather than the deployment's current default.
    */
   agentPreset?: string
   parentId?: SessionId