A full-featured CRM built with React, shadcn/ui, and Supabase.
docs(harness): relay the board's ABSOLUTE path (desktop app)
Jerome324f67caad50
diff --git a/CLAUDE.md b/CLAUDE.mdindex 465fa40d..597b81d8 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -30,7 +30,7 @@ Off by default. `#harness` (or "use the agent team" / "with the harness") routes`#technical-harness` is the same opt-in for a real developer: it appends a `PERSONA: technical` line (see `orchestrator.md` -> "`PERSONA: technical`"), which (1) uses the full technical register (file paths, `TASK-XXX`, git terms, `database`/`migration`/`Supabase`), (2) reports the mechanical truth (per-ticket status, branches, SHAs, verdicts, ADR paths), (3) stops at `session/<id>` (no promotion, no migration round; you promote and migrate yourself), and (4) appends every step to `<session_dir>/harness-progress.log`.-**Live progress (technical runs).** The report lands only at the end (possibly as a `task-notification`), so surface a live view WITHOUT flooding the chat with a raw log tail. The `render-status` SubagentStop hook renders `.harness/<SESSION_SHORT_ID>/{STATUS.md,TICKETS.md,status.json,session.diff}` (gitignored, per-session, cleaned at SessionEnd) from the live session state after every agent stop. `STATUS.md` lists tickets (status + review verdict), live worktrees, a changed-files summary, and recent activity, updating itself as agents finish; `TICKETS.md` is the readable plan; `session.diff` is the actual code the harness changed (the extension does not surface the `/tmp` worktree diffs, so this file is how the user reads them). **Link it workspace-root-relative.** The board lives at `<repo>/.harness/<SESSION_SHORT_ID>/`, and the editor resolves a clickable link from the workspace root: in a multi-root workspace that means prefixing the repo folder (e.g. `atomic-crm/.harness/<SESSION_SHORT_ID>/STATUS.md`) - a bare `.harness/...` resolves to the workspace root and fails with "outside the working directory". A single-root session or the desktop app takes `.harness/<SESSION_SHORT_ID>/STATUS.md` as-is; when unsure, also give the absolute path. An opt-in compact statusline is available (`.claude/scripts/harness-statusline.mjs`; wire it in your own `settings.local.json`, see its header) - not committed, since it would override a personal statusline. Dispatch the orchestrator with `run_in_background: true`. Prefer the board; a raw `Monitor({command: "tail -n +1 -F <session_dir>/harness-progress.log", ...})` terminal feed stays available but noisier. The authoritative end signal is the `task-notification`, not the log: on it, `TaskStop` any monitor, relay the report, and run `/harness-diff` on the session branch it stopped on.+**Live progress (technical runs).** The report lands only at the end (possibly as a `task-notification`), so surface a live view WITHOUT flooding the chat with a raw log tail. The `render-status` SubagentStop hook renders `.harness/<SESSION_SHORT_ID>/{STATUS.md,TICKETS.md,status.json,session.diff}` (gitignored, per-session, cleaned at SessionEnd) from the live session state after every agent stop. `STATUS.md` lists tickets (status + review verdict), live worktrees, a changed-files summary, and recent activity, updating itself as agents finish; `TICKETS.md` is the readable plan; `session.diff` is the actual code the harness changed (the extension does not surface the `/tmp` worktree diffs, so this file is how the user reads them). **Give a path that resolves in the user's client - always the ABSOLUTE path.** The board lives at `<repo>/.harness/<SESSION_SHORT_ID>/`. A bare relative `.harness/...` fails with "outside the working directory" on both the desktop app and a multi-root VS Code workspace, because the client resolves it from the workspace root, not the repo subfolder. So ALWAYS give the absolute path (`<repo>/.harness/<SESSION_SHORT_ID>/STATUS.md`): the desktop app's file pane opens arbitrary absolute paths, and it is the universal fallback. For an additionally-clickable link in a multi-root editor workspace, prefix the repo folder (e.g. `atomic-crm/.harness/<SESSION_SHORT_ID>/STATUS.md`); a single-root editor session takes `.harness/<SESSION_SHORT_ID>/STATUS.md` as-is. An opt-in compact statusline is available (`.claude/scripts/harness-statusline.mjs`; wire it in your own `settings.local.json`, see its header) - not committed, since it would override a personal statusline. Dispatch the orchestrator with `run_in_background: true`. Prefer the board; a raw `Monitor({command: "tail -n +1 -F <session_dir>/harness-progress.log", ...})` terminal feed stays available but noisier. The authoritative end signal is the `task-notification`, not the log: on it, `TaskStop` any monitor, relay the report, and run `/harness-diff` on the session branch it stopped on.## Agents