web UI: New Session sheet has no optional title field, forcing create-then-rename #1080

The web UI's New Session sheet collects harness, cwd, and an optional initial prompt (crates/daemon/assets/index.html ~line 3360 @ 4c1459b) — but not a title. A user who wants a named session has to create it, find the new row, open its context menu, choose Rename, type, and save.

Naming is most valuable exactly when a power user is spinning up several sessions at once, which is precisely when the create-then-rename round trip is most expensive: the rows are all still showing derived names like shell, claude, claude, so the row you need to rename is the hardest one to identify.

Expected

Add an optional title field to the New Session sheet, alongside the existing optional initial prompt. Empty leaves the derived default in place — same semantics as the Rename sheet.

The daemon already accepts a title at creation for other paths, so this should be a form field plus a parameter, not new server-side state.

Notes

• Field order matters for the common case: harness, title, cwd, prompt. Title belongs near the top because it is the field a user is most likely to fill for a session they intend to keep.
• Worth mirroring in the TUI's new-session flow for parity, though the web UI is where the friction was observed.
• Related: web UI: Rename opens blank for untitled sessions and mislabels empty as "clear" #1078 covers making the default-vs-override title model legible in the Rename sheet; the same copy should be reused here.

Acceptance criteria

• A session can be created with a title in one step from the web UI.
• Leaving the field empty is identical to today's behavior.

Found during a power-user UX audit of the TUI and web UI.