fix: extract session summaries from Claude JSONL files

[AgentWrapper]

Summary

• Fix toClaudeProjectPath() encoding bug — the function stripped the leading / before encoding, producing Users-equinox-... while Claude's actual project directories are -Users-equinox-.... This was the root cause of getSessionInfo() never finding JSONL files.
• Add live agent info enrichment in session manager's enrichSessionWithRuntimeState() so the dashboard gets summaries, cost estimates, and agent session IDs on every refresh.
• Add background summary persistence in lifecycle manager polling — writes summary to metadata files so they survive dashboard restarts.

Before/After

Before: Sessions without PRs show generic info:

💤 ao-37
spawning
terminal
detached

After: Sessions show actual agent summaries:

💤 Better Agent-to-Agent Communication Architecture
ao-37 • spawning • detached
terminal

Test plan

• All existing tests updated and passing (85 agent-claude-code tests, 131 core tests)
• pnpm build succeeds
• Path encoding verified against actual ~/.claude/projects/ directories
• Manual verification: start dashboard, confirm sessions display summaries

🤖 Generated with Claude Code

[cursor]

Full JSONL file parsed twice per session per poll

Medium Severity

During each poll cycle, getSessionInfo() is called twice per active session — first in sessionManager.list() via enrichSessionWithRuntimeState(), then again in checkSession(). Since getSessionInfo() reads and parses entire JSONL conversation files (which grow with every message), this doubles the file I/O on every poll interval. The session object passed to checkSession already has agentInfo populated from enrichment, so the lifecycle manager could use session.agentInfo?.summary instead of re-invoking getSessionInfo().

Additional Locations (1)

• packages/core/src/session-manager.ts#L199-L211

 

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Newlines in summary corrupt metadata file format

Medium Severity

The summary from getSessionInfo (sourced from JSONL files) can contain newline characters — either from Claude's auto-generated summaries or from multi-line user prompts used as fallback. Writing this unsanitized value via updateMetadata into the newline-delimited key=value metadata format corrupts the file. On the next read, the summary is silently truncated at the first newline, and any subsequent lines containing = overwrite other metadata keys like status or pr.