workstatuslisted

# Workstatus Not `start`. `start` orients a clean session from documents; this reports **live state**, mid-session, by running a command and describing what it printed. Its whole point is narrower than it sounds: report what was seen, not what is remembered. **Rule that matters more than the format below: never answer from conversation memory.** Anything checkable gets checked with a command first. "The run is probably still going" without looking at its log is exactly the kind of guess this report exists to rule out. ## What to run ```bash bash .floppy/run status ``` One call collects background jobs, git state (divergence from the remote, uncommitted files), and the memory wiring, and prints an answer rather than raw material — a bare `ps` or `git status -uall` costs far more to read for three lines that matter. If the repository defines a project-specific hook (`.floppy/workstatus-project.sh` — servers, corpora, anything specific to this project's own data), the command runs it automatically; nothing extra to call for that. A repository split into halves (see `agent-memory`) may also support a `--flow` flag for the state of the process half itself (memory lint, wrap-lock, worktrees, recent process edits): ```bash bash .floppy/run status --flow ``` Use it only when the task is about the process itself — on any other branch of work that half's state is someone else's business, not news. Beyond the command, three things are worth checking only if the report flagged