What you can run now: an article for 0.44 to 0.50

[VeryComplexAndLongName]

Third of the five. Documentation only — no source change, and therefore
no changeset.

The last article written for somebody using this tool rather than
building it covers 0.40 → 0.44. The extension is 0.50.3, twenty-eight
changes have been archived since, and all of it is documented in
HARNESS.md and LIMITS.md — reference tables organised by
configuration key, which answers questions about a capability the reader
already knows exists.

docs/articles/2026-09-12-what-you-can-run-now-0-44-to-0-50.md covers,
in a user's terms:

• a change run from a terminal, and what its three exit codes
  distinguish;
• changes running side by side, each in its own worktree and lease, with
  overlap decided from spec deltas and changed files rather than prose;
• ready, and why it exits 0 when nothing is ready;
• one numbered task handed to one agent and actually run, from the
  inbox;
• a run scheduled for a time nobody is awake for, and what happens when
  that time passes with nothing open;
• mechanical checks that run before the verifying agent is spent;
• a change declaring a step, and declaring a blocker;
• who holds a workspace — attribution, never authentication.

Every section names the archived change it came from, so a claim can
be checked against the repository rather than believed. Every command,
VS Code command title and archive path was then checked against USAGE
in main.ts, contributes.commands, and the directories themselves —
one at a time, not by reading the prose that names them.

Nothing proposed-but-unarchived is described, including the changes
proposed in #417.

Also: a teaser in the shape 2026-09-09-teaser-0.44.md set, carrying no
fact that is not in the article, and a link from README.md's Status
section.

One item stays open on purpose: whether the article reads as something
written for a person who has the tool and does not know what is new,
rather than as a list of changes. No automated check can make that
judgement, and it is the whole point of the change.

npm run verify: exit 0, 1998 tests across 157 files.
openspec validate --strict --changes: passed.

🤖 Generated with Claude Code