fo-status-viewer

# First Officer Status Viewer ## Status Viewer The `${SPACEDOCK_BIN:-spacedock} status` launcher owns path resolution and mutation guards; skill instructions stay declarative and never reference a plugin-private script path. Invoke it as: ``` ${SPACEDOCK_BIN:-spacedock} status --workflow-dir {workflow_dir} [--page N|--limit N|--next-id|--next|--archived|--where ...|--boot|--validate|--resolve REF] ``` - `--boot` — startup roll-up (mods, ID style, next-ID candidate, orphans, PR state, dispatchables). Incompatible with `--next`, `--next-id`, `--archived`, `--where`. - `--validate` — run before trusting manually edited workflow state. - `--resolve REF` — deterministic lookup by slug, exact stored ID, or sd-b32 address prefix; `--root` rejects unqualified cross-workflow ambiguity rather than guessing. - `--next-id` — preview the next-id candidate for `sequential` and `sd-b32` (n/a for `slug`). For `sd-b32`, pass `--id-seed "{slug-or-title}"` and optionally `--id-actor "{actor-or-agent}"` so creation context enters the candidate. To file a new entity, do NOT pair `--next-id` with a hand-written file — use `spacedock new` under the eagerly loaded `«write.classify»` contract, which mints the id and atomically writes the stamped entity in one call. `--next-id` is candidate-preview only. - `--where <field>=<value>` — **THE entity query.** One clause per flag; repeat the flag to AND clauses (`--where sprint=X --where 'sprint-readiness!=defer'`). Two clauses in one string is an ...