v0.1.38

fix: optimize_passives full-tree default + unique base parse (v0.1.38)

Dogfooding v0.1.37 live verified all of its new capabilities work (crit terminology fix,
support-pool fix, ascendancy auto-allocation + reporting, plan_gear auto-base, relevant_uniques,
the trigger guardrail). It surfaced two fixes:

- optimize_passives: the MCP tool defaulted points=3, so a bare optimize_passives() allocated only
  3 passive points and then reported pointsRemaining:0 — which reads as 'tree fully allocated', so a
  model building a build would ship a 3-point tree. The default is now 0 (the whole tree, the usual
  intent; pass a positive number only to cap it), and the shim reports pointsRemaining as the
  build's TRUE unspent passive points so a capped call can never misread as done.

- pipeline: a unique's 'Source:' drop line was mistaken for its base (Hand of Wisdom and Action read
  'Source: Drops from...' instead of 'Furtive Wraps'). UNIQUE_META_RE now filters Source: lines
  (1 of 433 uniques affected; corrects on the next corpus rebuild).

Full gate green (ruff, mypy, pytest).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>