Skip to content

v5.1.2 — swarm artifact archive

Latest

Choose a tag to compare

@rmzi rmzi released this 04 Aug 23:10

Documentation only. No runtime, agent, hook, or skill changes from 5.1.1.

If you're upgrading from 5.1.0 or earlier, the release you actually care about is v5.1.1 — it restores agent dispatch, which was completely non-functional. Everything functional in this line shipped there.

Added

Archived the dispatch-restoration swarm artifacts under docs/swarm-reports/2026-08-04-1804-dispatch-restoration/ — validation report, review report, scout report, and PR body.

The scout report is the part worth keeping. It records that both fatal dispatch bugs shipped through a fully green test suite, why no self-consistency check could have caught either — the violated contract was Claude Code's, not PDS's, so PDS was internally coherent and completely non-functional at the same time — and six patterns that generalize:

  1. An empty list in an error message is a filter signal, not an absence. Available agents: with nothing after it meant "your filter matched zero things, so I discarded the whole set," not "nothing is installed."
  2. Differential probing beats re-reading code. Both root causes were pinned by building minimal variants and comparing outcomes, not by inspection.
  3. Never accept a model's account of a tool result over the raw tool result.
  4. A changed error message is progress, and often a second bug. Treating it as "still broken" would have shipped one of the two defects.
  5. Verify the premise, not just the conclusion. The previous fix rested on an assumption nobody tested; one instrumented hook falsified it immediately.
  6. Registering a hook can silently take ownership you didn't intend to accept.

Upgrading

Nothing to do if you're already on 5.1.1. Otherwise:

claude plugin update pds@pds-marketplace

Then restart Claude Code.