feat: support Cursor agent in history with resume and workspace recovery

[cbb330]

Summary

• add Cursor agent resume support end-to-end, including frontend command generation, server-side resume handling, and macOS terminal launch behavior for Ghostty and other openers
• support Cursor agent's nested transcript layout during discovery/sync and recover workspace roots plus terminal cwd from Cursor transcript metadata, with lazy ambiguity handling so --workspace only needs transcript scanning when multiple filesystem matches exist
• add regression coverage for nested transcripts, workspace path ambiguity, symlink normalization, command_only resume output, and Ghostty AppleScript launch behavior

Test plan

• CGO_ENABLED=1 go test -tags fts5 ./internal/server/...
• go vet ./...
• make build
• Manual: resume a Cursor agent session from the UI and verify terminal cwd plus --workspace
• Manual: verify Ghostty opens a fresh terminal and does not restore stale saved tabs

Made with Cursor

[roborev-ci]

roborev: Combined Review (dd0aa8b)

Verdict: 2 medium-severity issues should be addressed before merge.

Medium

• internal/server/resume.go (handleResumeSession, command_only response path)
  Cursor resumes depend on launchDir to preserve the prior shell working directory, but the command_only response returns only cursor agent --resume ... --workspace ... and leaves the directory in a separate cwd field. Any caller that executes or copies only command can resume from the wrong directory.
  Suggested fix: make the returned command self-contained, for example by prepending cd <launchDir> && ... when launchDir is known, or guarantee that clipboard/command-only consumers also apply cwd.

• internal/server/resume.go (resumeLaunchCwd, used from handleResumeSession)
  On macOS, resumeLaunchCwd clears the launch directory for Cursor when using auto, iTerm2, Terminal, or Ghostty. If workspace resolution fails but launchDir is still available from the transcript, the launch loses the only known directory context and starts from the terminal’s default directory instead.
  Suggested fix: preserve launchDir unless there is a confirmed equivalent cwd mechanism, or prepend cd <launchDir> && to the launched Cursor command.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (525a200)

Verdict: No medium-or-higher issues found in the reviewed changes.

All review outputs that reported findings agreed the change is clean. The security review found no issues, and the general review found no medium, high, or critical concerns.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (3c51a3f)

Verdict: One medium-severity regression needs to be addressed; no high or critical issues were identified.

Medium

• internal/server/resume.go (handleResumeSession, resumeLaunchCwd): Cursor resumes launched on macOS via auto, iTerm2, Terminal.app, or Ghostty drop launchDir because resumeLaunchCwd() returns "" for those launchers. As a result, the AppleScript path runs cursor agent --resume ... --workspace <workspace> without restoring the last working directory, while the clipboard fallback still uses cd <last-working-dir> && .... This causes resumed sessions to reopen from the workspace root instead of the recorded shell directory, which can break relative-path behavior and undercuts the resume-path restoration added by this patch.
  Suggested fix: Preserve launchDir for Cursor macOS launches, or inject cd <launchDir> && into the AppleScript command while keeping --workspace <workspace> for workspace selection.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)