vx status

Report the troop: every mission and scout in the current project, in
whatever state it's in. Read-only.

Usage:
  vx status [--json]

Without --json, prints one line per task (most recently updated first).

--json prints a single JSON object instead:

  {
    "schema_version": 1,
    "generated_at": "2026-09-24T12:00:00Z",
    "project_root": "/abs/path/to/this project's ~/.vexillum namespace",
    "tasks": [ ... ]
  }

"tasks" is the exact task record vexillum itself persists to
<project root>/tasks/*.json - this command adds nothing to it, so a
consumer (e.g. the /muster skill) reads the same shape vexillum
itself reasons about, never a separate reinterpretation of it. Grouping,
filtering, and judgment calls (what counts as "needs attention", what's
in the current session, GitHub PR enrichment) are left to that consumer,
not decided here.

A task in status "blocked" carries its open question in its "decision"
field (question, options, asked_at, and answer/answered_at once 'vx decide'
has run) - not just the word "blocked". Without --json, a
blocked task's question is also printed on its own indented line.