Session resume now carries SessionStart hooks through, including partial-history resume

What

• Session resume/fork no longer passes hookMessages/hooksPromise directly to the startup path; instead it returns a sessionStartHooks promise wired through a new abortable "tail" queue. Resume also gained a precedingRows option, letting a caller resume from a subset of prior transcript rows instead of the full session.
• When resuming a session from the picker, the session's recorded sessionStartHooks are captured and threaded through as pendingHookMessages into the resumed UI state.
• Resumed sessions now propagate this sessionStartHooks field into pendingHookMessages when reconstructing state, alongside the existing sessionHooks field, which was previously missing from the restored-session object.

Why This ensures SessionStart hooks that fired for a session are correctly carried over when that session is resumed, so hook-driven setup isn't silently lost, and it also enables resuming from a partial transcript.