vx pending

Record and clear the commander's own pending decisions.

These are things that wait on the general's approval (dispatch a mission
already designed, land a finished one, ship a PR) and would otherwise live
only in the commander's head, lost if the session is cut.

Usage:
  vx pending add <text> [--option <label>]... [--recommend <n>]
  vx pending list [--json]
  vx pending clear <id>

add records <text> as a new pending decision and prints its id. Give the
answers the general can pick from with one --option <label> per answer, in
order, and mark the one you recommend with --recommend <n> (1-based index
into the options, needs at least one --option). Put "--" before text that
starts with "--". clear removes one once the general has decided. list
prints them oldest first, with the options numbered and the recommended one
marked.

This is a different category from a blocked task: there a soldier needs the
general, and 'vx decide' answers it; here the commander needs the general. A
done mission awaiting 'vx land' needs no entry, the /muster skill derives
that from git; use this for decisions that exist nowhere else.

Items persist as <project root>/pending/<id>.json, written atomically, so
they survive a cut session. --json prints a single JSON object:

  {
    "schema_version": 0,
    "generated_at": "2026-09-24T12:00:00Z",
    "pending": [
      {"schema_version": 0, "id": "1a2b3c4d", "text": "...",
       "options": ["...", "..."], "recommended": 1, "created_at": "..."}
    ]
  }

"options" and "recommended" are left out of an item recorded without them.
The /muster skill reads this to show each item as a card in its "Decisions
for you" section.