feat(workspace-server): import & store Claude Code CLI sessions

[adboio]

Problem

Changes

How did you test this?

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

[adboio]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(code): import claude code sessions #2873
• feat(workspace-server): import & store Claude Code CLI sessions #2877 👈 (View in Graphite)
• feat(agent): replay imported Claude Code CLI transcripts #2876
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit 8cbec5f.}

[greptile-apps]

Comments Outside Diff (2)

1. packages/workspace-server/src/services/claude-cli-sessions/claude-cli-sessions.ts, line 2177-2182 (link)

   Files deleted before the DB row is cleared

   removeSnapshotFiles runs first, then deleteByTaskId. If anything interrupts execution between those two steps (process crash, unexpected exception after force: true actually succeeds), the import row survives while its files are gone. On the next listForRepo call the source session shows "imported" with a now-deleted importedTaskId, and there is no way to re-import without manually clearing the DB.

   Reversing the order — delete the DB row first, then the files — produces better failure semantics: if the file deletion subsequently fails, the source session already shows "new" and can be re-imported; any orphaned file wastes only disk space.

2. packages/workspace-server/src/services/claude-cli-sessions/claude-cli-sessions.ts, line 2099 (link)

   Full-file read in importSession vs chunked reads in the listing path

   fs.readFile(sourcePath, "utf-8") loads the entire transcript into a JavaScript string before any processing, while listForRepo deliberately uses bounded head/tail reads. A CLI session with thousands of turns can easily be several megabytes; this import call then allocates a second copy while building the rewritten array. Using readline (or createReadStream) would keep memory usage proportional to a single line at a time and is consistent with the chunked approach already used in scanning.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

_{Reviews (1): Last reviewed commit: "feat(workspace-server): import & store C..." | Re-trigger Greptile}