Parallel missions

Each soldier gets its own camp, so you can ask for several things at once:

> have one soldier add rate limiting to the API, another migrate the logging
  library, and a scout map where we parse dates

The commander dispatches three tasks. They run side by side; the sentinel wakes the commander as each one settles.

Keep an eye on the troopCopy Anchor Link

vx status

prints one line per task, most recently updated first: id, kind, status, camp branch and the start of the prompt. A blocked task also prints its question on an indented line. For a richer view, use the muster skill.

Landing several missionsCopy Anchor Link

Landing is a fast-forward and vexillum never rebases for you. So when sibling missions were all dispatched from the same starting point, landing the first moves your base branch, and every other mission stops being a clean fast-forward. That is expected, not an error:

1. Land the first: vx land <task-id>.
2. For the next one, ask its own soldier (re-prompt its still-open pane) to rebase its branch onto the updated base. It has the full context of its change.
3. Retry vx land.

If the soldier's pane already closed, no fresh soldier can rebase a branch it never touched; the commander tells you instead of guessing.

Good habitsCopy Anchor Link

• Commit the scaffold first. land refuses a dirty checkout, and init leaves new files uncommitted.
• Keep missions independent. Two missions editing the same lines will conflict at rebase time.
• Match model to task. The commander picks a profile from models.json: haiku for mechanical edits and sonnet with high effort for large ones, unless you changed them.