Add Claude Cowork support; recover subagents in both sources

The biggest functional change since the initial release. Two things land
together because they share most of the plumbing:

1. CLAUDE COWORK SUPPORT
The local-agent desktop app stores sessions at
~/Library/Application Support/Claude/local-agent-mode-sessions/, in a
deeper hierarchy: <account>/<workspace>/local_<session>/.claude/projects/<cwd>/<id>.jsonl.
The JSONL format is identical to Claude Code, so the parser is reused;
the scanner gets a new walk to discover them.

Both sources are auto-detected — no flag required. CLI now shows a Source
column ('Code' or 'Cowork') in 'list' output, and 'export-all' organises
output as <output>/<source>/<project>/<files> so the two are clearly
separated on disk.

2. SUBAGENT RECOVERY (BOTH SOURCES)
Subagent transcripts live at <project>/<session_id>/subagents/agent-*.jsonl
and were silently dropped before — including 5 subagents in one of my own
test sessions. Now they're discovered alongside the main JSONL and rendered
as a '# Subagents' section appended to the full export, with each one as
its own '## Subagent N: <id>' block. Minimal export drops them (subagent
runs are tool plumbing, not human dialogue).

Frontmatter gains:
- 'source: code|cowork' on every export
- 'subagents: N' when N > 0 in full mode

DESIGN CHOICES IN SERVICE OF USABILITY
- Folder layout chosen to mirror the user's mental model: 'I have Claude
  Code and Claude Cowork' -> 'backups/code/' and 'backups/cowork/'.
- Cowork session directories use the friendly codenames Cowork itself
  generates ('beautiful-charming-curie') rather than UUIDs, when available.
  Sessions whose cwd is the internal outputs dir fall back to
  'session-<8-char-id>'.
- 'list' table now has Source as the first column. AI-titles are
  prioritised in the 'First Prompt / Title' column for readability.
- Error message updated for the both-sources case: lists every root tried.

TESTS
+12 new tests (was 73, now 85). New fixtures-cowork/ tree mirrors real
on-disk Cowork structure including a subagent file. test_cowork.py covers:
- Cowork scanner discovery
- Subagent linkage (in both sources)
- Source column in CLI list
- Source-based folder layout in export-all
- 'works with only Cowork data' (no Code root)
- 'errors when neither source exists'
Existing tests updated for new frontmatter ('source:'), new folder layout
('<output>/code/...'), and the unified error path.

A new conftest auto-fixture isolates every test from the developer's real
~/.claude/ and ~/Library/Application Support/Claude/, preventing tests from
accidentally scanning real data.

DOCS
README, README.ru, QUICKSTART, PROMPT all updated for the dual-source
reality. New behaviour bullets, new tree diagrams, new error messages,
new total test count (85).

Author: sedelev

PROMPT.md

@@ -18,7 +18,7 @@ Copy everything between the lines:
 ---
 
 ```
-I want to install and try `claude-backup` — a CLI tool that exports my Claude Code session history to local Markdown files. The repo is https://github.com/parallelclaw/claude-backup.
+I want to install and try `claude-backup` — a CLI tool that exports my Claude Code AND Claude Cowork session history (both apps) to local Markdown files. The repo is https://github.com/parallelclaw/claude-backup.
 
 Walk me through it step by step. After each step, wait for me to paste the output before moving on. Be terse — no walls of text, one short paragraph per step is fine. Don't run commands yourself; print the command and let me run it.
 
@@ -28,13 +28,13 @@ The full path:
 2. Have me `git clone https://github.com/parallelclaw/claude-backup.git` somewhere convenient (default: `~/Desktop`) and `cd` into the repo.
 3. Have me run `pip3 install --user -e .`. If pip warns that the install dir isn't on PATH, give me the right `export PATH=...` line for my OS AND tell me how to make it permanent (in `~/.zshrc` on macOS / `~/.bashrc` on Linux).
 4. Have me run `claude-backup --version` to confirm the CLI is reachable.
-5. Have me run `claude-backup list` and help me read the table — explain what each column means (Project / Session / First Prompt or Title / Msgs / Created).
-6. Pick an interesting session with me and have me run `claude-backup export <8-char-prefix> --output ./backups/`. By default this writes two files: `<id>.md` (clean dialogue, only my prompts and Claude's text replies) and `<id>.full.md` (everything, including tool calls and tool results). Explain when to use each.
+5. Have me run `claude-backup list` and help me read the table. Columns: Source (Code or Cowork) / Project / Session (8-char prefix) / First Prompt or Title / Msgs / Created. Note that the tool auto-finds both Claude Code (`~/.claude/projects/`) and Claude Cowork (`~/Library/Application Support/Claude/local-agent-mode-sessions/`); if I have only one, the other is silently skipped.
+6. Pick an interesting session with me and have me run `claude-backup export <8-char-prefix> --output ./backups/`. By default this writes two files: `<id>.md` (clean dialogue, only my prompts and Claude's text replies) and `<id>.full.md` (everything — tool calls, tool results, AND any subagent transcripts the session spawned). Explain when to use each.
 7. Have me `open ./backups/<filename>.md` (macOS) or `xdg-open` (Linux) to view the result. Ask what I think.
-8. If I want a full backup of everything, have me run `claude-backup export-all --output ~/claude-backups`. Explain that the resulting folders mirror my real working directories (with the home prefix stripped).
+8. If I want a full backup of everything, have me run `claude-backup export-all --output ~/claude-backups`. Explain that the output is split first by source — `code/` and `cowork/` subfolders — and inside each, organised by project (Code mirrors my real working dirs, Cowork uses the friendly codename like `beautiful-charming-curie` that Cowork itself generates).
 
 If a command errors: help me debug, don't just dump a fix. Common issues —
-- `~/.claude/projects/` not found → I haven't used Claude Code on this machine yet
+- "Claude data not found" → I haven't used either Claude Code or Cowork on this machine yet
 - `pip: command not found` → try `python3 -m pip` instead
 - `command not found: claude-backup` after install → PATH issue, see step 3
 - "externally-managed-environment" pip error → use `pip3 install --user --break-system-packages -e .` or a venv
@@ -51,7 +51,7 @@ Start with step 1.
 ---
 
 ```
-Я хочу установить и попробовать `claude-backup` — CLI-утилиту, которая экспортирует историю моих сессий Claude Code в локальные Markdown-файлы. Репозиторий — https://github.com/parallelclaw/claude-backup.
+Я хочу установить и попробовать `claude-backup` — CLI-утилиту, которая экспортирует историю моих сессий Claude Code И Claude Cowork (обе утилиты) в локальные Markdown-файлы. Репозиторий — https://github.com/parallelclaw/claude-backup.
 
 Проведи меня по шагам. После каждого шага жди когда я вставлю вывод. Будь лаконичен — никаких стен текста, один короткий абзац на шаг достаточно. Сам команды не выполняй — печатай команду и жди пока я выполню.
 
@@ -61,13 +61,13 @@ Start with step 1.
 2. `git clone https://github.com/parallelclaw/claude-backup.git` куда-нибудь удобно (по умолчанию `~/Desktop`) и `cd` в репозиторий.
 3. `pip3 install --user -e .`. Если pip ругается что папка не в PATH — дай правильную строку `export PATH=...` для моей системы И объясни как сделать перманентным (в `~/.zshrc` на macOS / `~/.bashrc` на Linux).
 4. `claude-backup --version` — проверить что CLI работает.
-5. `claude-backup list` — помоги прочитать таблицу, объясни колонки (Project / Session / First Prompt или Title / Msgs / Created).
-6. Выбери со мной одну сессию и вели мне `claude-backup export <8-символьный-префикс> --output ./backups/`. По умолчанию создаются два файла: `<id>.md` (чистый диалог — только мои промпты и текстовые ответы Claude) и `<id>.full.md` (всё, включая tool-вызовы и tool-результаты). Объясни когда использовать каждый.
+5. `claude-backup list` — помоги прочитать таблицу. Колонки: Source (Code или Cowork) / Project / Session (8-символьный префикс) / First Prompt или Title / Msgs / Created. Заметь что утилита авто-находит и Claude Code (`~/.claude/projects/`), и Claude Cowork (`~/Library/Application Support/Claude/local-agent-mode-sessions/`); если есть только один — другой молча пропускается.
+6. Выбери со мной одну сессию и вели мне `claude-backup export <8-символьный-префикс> --output ./backups/`. По умолчанию создаются два файла: `<id>.md` (чистый диалог — только мои промпты и текстовые ответы Claude) и `<id>.full.md` (всё: tool-вызовы, tool-результаты И transcripts subagent'ов которые сессия порождала). Объясни когда использовать каждый.
 7. `open ./backups/<filename>.md` (macOS) или `xdg-open` (Linux) — посмотреть результат. Спроси что я думаю.
-8. Если хочу выгрузить всё — `claude-backup export-all --output ~/claude-backups`. Объясни что папки в результате зеркалят реальные рабочие директории (с вырезанным home-префиксом).
+8. Если хочу выгрузить всё — `claude-backup export-all --output ~/claude-backups`. Объясни что вывод сначала разделён по источнику — подпапки `code/` и `cowork/`, — а внутри каждой организован по проекту (Code зеркалит реальные рабочие директории, Cowork использует дружелюбный кодноим типа `beautiful-charming-curie` который Cowork сам генерирует).
 
 Если команда выдаёт ошибку — помоги отладить, не вываливай готовый фикс. Частые проблемы:
-- `~/.claude/projects/` отсутствует → я ещё не пользовался Claude Code на этой машине
+- "Claude data not found" → я ещё не пользовался ни Claude Code, ни Cowork на этой машине
 - `pip: command not found` → попробовать `python3 -m pip`
 - `command not found: claude-backup` после установки → PATH, см. шаг 3
 - ошибка "externally-managed-environment" от pip → `pip3 install --user --break-system-packages -e .` или venv

QUICKSTART.md

@@ -9,7 +9,7 @@
 
 ## What this tool does
 
-Claude Code stores every conversation on your computer in a folder called `~/.claude/projects/`. Those files are in a format (`.jsonl`) that's hard to read. **`claude-backup`** turns them into nice, readable Markdown files you can open in any text editor, search, or archive.
+Claude Code and Claude Cowork (the local-agent desktop app) both store every conversation on your computer — in `~/.claude/projects/` and `~/Library/Application Support/Claude/local-agent-mode-sessions/` respectively. Those files are in a format (`.jsonl`) that's hard to read. **`claude-backup`** finds both, walks any subagents they spawned, and turns the lot into nice, readable Markdown files you can open in any text editor, search, or archive.
 
 ---
 
@@ -51,14 +51,14 @@ That's it. You can now run `claude-backup` from any folder.
 claude-backup list
 ```
 
-You'll see a table of every Claude Code session on your machine. The "First Prompt / Title" column shows the AI-generated session title when Claude Code recorded one, and falls back to your literal first prompt otherwise:
+You'll see a table of every conversation on your machine — across **both** Claude Code and Claude Cowork. The Source column tells you which app it came from. The "First Prompt / Title" column shows the AI-generated session title when Claude recorded one, and falls back to your literal first prompt otherwise:
 
 ```
-Project           Session   First Prompt / Title                          Msgs  Created
-────────────────  ────────  ────────────────────────────────────────────  ────  ───────────────────
-my-webapp         abc12345  Fix the login bug                             42    2026-05-07T10:42:00
-my-webapp         def45678  Add dark mode toggle                          18    2026-05-06T14:00:00
-notes-app         ghi78901  Refactor parser for nested blocks             7     2026-05-04T09:15:00
+Source  Project                   Session   First Prompt / Title                          Msgs  Created
+──────  ────────────────────────  ────────  ────────────────────────────────────────────  ────  ───────────────────
+Code    my-webapp                 abc12345  Fix the login bug                             42    2026-05-07T10:42:00
+Code    my-webapp                 def45678  Add dark mode toggle                          18    2026-05-06T14:00:00
+Cowork  beautiful-charming-curie  ghi78901  Q2 results slide deck                         88    2026-05-04T09:15:00
 ```
 
 Each row is one conversation. The **Session** column shows just the first 8 characters of the ID — that's all you need to copy for the next step.
@@ -85,7 +85,7 @@ Exported: backups/2026-05-07--abc12345-...full.md
 | File | What's inside | When to use |
 |------|---------------|-------------|
 | `2026-05-07--abc12345-….md` | The conversation: your prompts + Claude's text replies, nothing else | Re-reading later, archiving, sharing |
-| `2026-05-07--abc12345-….full.md` | Everything: every tool call, every shell command, every internal reasoning step | Debugging or auditing what the agent actually did |
+| `2026-05-07--abc12345-….full.md` | Everything: every tool call, every shell command, every internal reasoning step, **plus full transcripts of any subagents the session spawned** | Debugging or auditing what the agent actually did |
 
 Open the `.md` file in any text editor — that's the readable one. It looks like this:
 
@@ -140,33 +140,42 @@ claude-backup export-all --output ./backups/                    # both files per
 claude-backup export-all --output ./backups/ --mode minimal     # only the clean .md files
 ```
 
-The backup tree mirrors the real directories where you ran Claude Code (with your home prefix stripped). For example:
+The backup tree is split by source first, then mirrors how each app organises sessions. For example:
 
 ```
 backups/
-├── Documents/Claude/
-│   ├── 2026-04-22--<id>.md
-│   └── 2026-05-07--<id>.md
-└── code/some-project/
-    └── 2026-04-10--<id>.md
+├── code/                              ← Claude Code sessions, mirroring your real working dirs
+│   └── Documents/Claude/
+│       ├── 2026-04-22--<id>.md
+│       └── 2026-05-07--<id>.md
+└── cowork/                            ← Claude Cowork sessions, by friendly codename
+    ├── beautiful-charming-curie/
+    │   └── 2026-04-06--<id>.md
+    └── upbeat-epic-feynman/
+        └── 2026-04-20--<id>.md
 ```
 
-You now have a complete Markdown archive of your Claude Code history, organised the way your projects are organised.
+You now have a complete Markdown archive of every Claude conversation across both apps.
 
 ---
 
 ## Common questions
 
 **Where does it look for my conversations?**
 
-Default: `~/.claude/projects/` on macOS/Linux, `C:\Users\YourName\.claude\projects\` on Windows (WSL path: `/mnt/c/Users/YourName/.claude/projects/`).
+Two places, both auto-detected:
+- **Claude Code:** `~/.claude/projects/` (Windows/WSL: `/mnt/c/Users/YourName/.claude/projects/`)
+- **Claude Cowork:** `~/Library/Application Support/Claude/local-agent-mode-sessions/` (macOS only)
+
+If only one exists, the tool just uses that one. No flag needed.
 
 **Can I point it at a different folder?**
 
-Yes — use `--claude-home`:
+Yes — each source has its own override:
 
 ```bash
-claude-backup --claude-home /some/other/path list
+claude-backup --claude-home /some/other/code-path list
+claude-backup --cowork-home /some/other/cowork-path list
 ```
 
 **Does it modify or delete anything?**