The /queue-status-lite command provides a read-only dashboard. It lists every active plan under a project's resolved state directory — its vault directory's tasks/ on a synced backend, or a repo-local .harness/ for a project with no vault. Each entry shows the plan status and the head of the progress log. The command is deterministic. It makes no writes. It arbitrates no claims — the human stays the arbiter. The reasoning lives in Named plans; this page is the lookup.

On a synced backend the script reads every active task under the project's tasks/ directory — a finished (done or dropped) task is left out, since a dashboard of active work doesn't list closed tasks. With no vault it reads the repo-local .harness/'s flat pair: the singleton PLAN.md, then any named PLAN-<name>.md file, alphabetically. The two are never combined — a project resolves to exactly one of them (agentm-vault plan 15):

Archived plans (PLAN.archive.*.md) and GDrive conflict copies (PLAN-foo (conflicted copy …).md) are excluded — the former by the PLAN-* glob, the latter via hm._conflict_family.

Active plans in <dir>:

  PLAN.md      [in-progress]
               last: <most-recent progress line, truncated to 120 chars with …>
  PLAN-foo.md  [planning]
               last: <…>

A plan with no matching progress file still lists, with the head shown as (no progress file). An unresolved or missing state directory prints No plan state directory to read (...); a resolved but empty one prints No plans found in <dir>. Both still exit 0.

• Read-only. The command performs zero filesystem mutation. Its test asserts the fixture state directory is byte-identical before and after a run.
• Deterministic. The script enumerates the resolved state directory — no network, no transcript mining, no sub-agent dispatch. Output depends only on the directory contents.
• No arbitration. It does not claim, lease, lock, or assign plans to workers. It surfaces state for a human coordinator to read; the design deliberately omits queue/lease machinery.
• Always exit 0. Success exits 0; so does every graceful path — no resolvable state directory, a missing directory, or an empty one. A status read never errors on absence.

• Named plans — the naming contract (PLAN-<name>.md / progress-<name>.md) this command enumerates, and why the human is the arbiter.
• Vault write protocol — the write protocol named plans go through; this read-model takes no lock because it never writes.
• CI gates — check-multi-plan-naming (#13) locks the naming contract this command reads against.
• Repo layout — where scripts/ lives (test infra + read-model scripts; never propagated to target projects).