harness-clientlisted

<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. --> # Harness Client ## Scope Owns being the **client** of a running supervisor: attach, observe, answer. It is not for driving work yourself — `harness-loop` owns single-track work (`basicly loop run`), and the supervisor itself owns fan-out over lanes (`basicly loop supervise <root>`). Reach for this skill when a supervisor is already running, or may be, and you are a *second* session looking in. Every command here is either a pure read or a write to one decision item, and none of them touches a worktree, a branch, or a gate. The one exception is the board's default action route, below: it can approve a checkpoint or kill a lane. ## Attach: one command, no lock ```sh basicly loop session <root-issue> # live status of the session basicly loop session <root-issue> --json # same, machine-readable ``` It reads the tracker and the supervisor's lockfile and writes nothing, so it never contends with the supervisor and any number of clients may attach at once. It answers four things: - **supervisor** — who holds the repo's singleton lock, and how old their heartbeat is. `(none running)` means the root is unsupervised; a *stale* heartbeat means the holder crashed. - **lane** — each in-flight lane, its worktree and branch, whether that worktree still exists, and what the lane last ran (agent, outcome, tokens). - **decisions** — how many judgments the session is waitin