Add native session restore for Kiro CLI

[thuanlm215]

Kiro CLI panes are detected by Herdr, but after a Herdr server restart they return as shells instead of resuming their conversations. This makes Kiro behave differently from other agents that report native session identity.

Current Kiro hooks expose the conversation session_id, and Kiro can resume a specific conversation with kiro-cli chat --resume-id <id>. That appears to provide the two capabilities Herdr needs for native restore without relying on Kiro session files or process inspection.

Would a session-identity integration for Kiro fit Herdr? Lifecycle state could remain owned by the existing screen manifest; the integration would only report the native session reference used during restore.

One scope question is Kiro CLI 2.x versus the 3.0 early-access engine: 3.0 changes the hook format and session storage, and its sessions are not backward-compatible with 2.x. It would be useful to know whether support should initially target stable 2.x, 3.x, or both.

[thuanlm215]

I can reproduce this with Kiro CLI 2.16.2 and am available to test the full session-report and restore flow on Linux if the direction is accepted.

[rohatgunes]

Came here to open this, this is the main thing missing for Kiro. When pitched Herdr over KiroCrew for fellows, they questioned if they can resume their sessions when herdr is invoked again.

Along with this, if server is rebooted, herdr should still be able to resume its sessions along with Kiro CLI resume-ids that are exposed as described above.

This would be a true recovery.

I'm happy to give it a hand to test it out too.
but seems like #1649 is more comprehensive.

[thuanlm215]

Thanks — true recovery after restart/reboot is exactly the gap.

I'll take a crack at implementing the full path myself (session identity + actual resume after restart). #1649 is useful context; I'll open a PR once it's in better shape. Would love your help testing.

Direction I'm locking in so far:

• session-identity-only integration (herdr integration install kiro), lifecycle still from the existing Kiro screen manifest
• SessionStart hook reports pane.report_agent_session with herdr:kiro / kiro
• prefer $KIRO_SESSION_ID (and hook payload if present) over scanning ~/.kiro/sessions/ — multi-pane race otherwise
• wire agent_resume + session-identity registration so restore actually rebuilds kiro-cli chat --resume-id <id>
• target stable 2.x first; v3 hook/schema as a follow-up once verified