feat(cockpit): worker inspector drawer — timeline, worktree forensics, breadcrumbs (closes #70)

.claude/agents/implementer.md

@@ -41,6 +41,6 @@ Never call bare `gh`. EVERY `gh` invocation (PR create/update, comments, `gh api
 If a reviewer rejects your work, address every reason, re-run the gates, and report again. Iterate until approved.
 
 ## Progress events (observability)
-Best-effort, additive only — never changes gate enforcement or control flow. Log a progress event at each phase transition:
-`bash ${CLAUDE_PLUGIN_ROOT:-.claude}/scripts/log-event.sh --role implementer --task <issue id> --phase <implementing|gate-running|done> --model <your model>`
-Call it with `--phase implementing` when you start work (step 3), `--phase gate-running` before step 5's gate run, and `--phase done` when you file your report (step 7). If `log-event.sh` fails, ignore it and continue — it must never block or alter your work.
+Best-effort, additive only — never changes gate enforcement or control flow. Log a progress event at each phase transition, ALSO passing a one-line `--detail "<what you're about to do / just did>"` breadcrumb (one short terse sentence — it costs a few tokens, so keep it terse):
+`bash ${CLAUDE_PLUGIN_ROOT:-.claude}/scripts/log-event.sh --role implementer --task <issue id> --phase <implementing|gate-running|done> --model <your model> --detail "<terse breadcrumb>"`
+Call it with `--phase implementing` when you start work (step 3), `--phase gate-running` before step 5's gate run, and `--phase done` when you file your report (step 7). If `log-event.sh` fails, ignore it and continue — it must never block or alter your work (the `--detail` breadcrumb is the same best-effort deal: never let it block you either).

.claude/agents/orchestrator.md

@@ -39,9 +39,9 @@ Every subagent you spawn starts a fresh context that loads CLAUDE.md and its age
 - Git hygiene: tell workers to **stage explicit paths, never `git add -A`/`git commit -a`**. A sandboxed session masks config paths (shell rc, `.gitconfig`, `.mcp.json`, `.claude/{hooks,skills,routines}`, editor dirs) as `/dev/null` device nodes that show up in `git status`; a blanket add can abort the commit. They're expected artifacts, not the worker's changes (see `docs/HARDENING.md` → Caveats).
 
 ## Progress events (observability)
-Best-effort, additive only — never changes gate enforcement, review consensus, or control flow. After you present the plan (step 2), run:
-`bash ${CLAUDE_PLUGIN_ROOT:-.claude}/scripts/log-event.sh --role orchestrator --task <issue/task id> --phase scoped --model <your model>`
-When the run wraps (step 6), you may also log `--phase done`. If `log-event.sh` fails for any reason, ignore it and continue — never let it block or alter your loop.
+Best-effort, additive only — never changes gate enforcement, review consensus, or control flow. After you present the plan (step 2), run, ALSO passing a one-line `--detail "<what you're about to do / just did>"` breadcrumb (one short terse sentence — it costs a few tokens, so keep it terse):
+`bash ${CLAUDE_PLUGIN_ROOT:-.claude}/scripts/log-event.sh --role orchestrator --task <issue/task id> --phase scoped --model <your model> --detail "<terse breadcrumb>"`
+When the run wraps (step 6), you may also log `--phase done`. If `log-event.sh` fails for any reason, ignore it and continue — never let it block or alter your loop (the `--detail` breadcrumb is the same best-effort deal: never let it block you either).
 
 ## Status report format (your "standup")
 ```

.claude/agents/reviewer.md

@@ -43,6 +43,6 @@ If you touch GitHub at all (e.g. `gh pr diff`, `gh pr view`, `gh api`), route it
 Reject if you find anything that would block merge under your lens. Be specific and actionable so the implementer can fix without guessing.
 
 ## Progress events (observability)
-Best-effort, additive only — never changes review consensus or control flow. Log a progress event at the start of your review and when you emit your verdict:
-`bash ${CLAUDE_PLUGIN_ROOT:-.claude}/scripts/log-event.sh --role reviewer --task <issue/task id> --phase reviewing --model <your model> --lens <your lens>`
-then again with `--phase done` once you've emitted your verdict. If `log-event.sh` fails, ignore it and continue — it must never block or alter your review.
+Best-effort, additive only — never changes review consensus or control flow. Log a progress event at the start of your review and when you emit your verdict, ALSO passing a one-line `--detail "<what you're about to do / just did>"` breadcrumb (one short terse sentence — it costs a few tokens, so keep it terse):
+`bash ${CLAUDE_PLUGIN_ROOT:-.claude}/scripts/log-event.sh --role reviewer --task <issue/task id> --phase reviewing --model <your model> --lens <your lens> --detail "<terse breadcrumb>"`
+then again with `--phase done` once you've emitted your verdict. If `log-event.sh` fails, ignore it and continue — it must never block or alter your review (the `--detail` breadcrumb is the same best-effort deal: never let it block you either).