v0.2.0

agentseam 0.2.0 rebuilds how vendor support is expressed: eleven of the twelve
adapted agents are no longer Python modules but JSON config entries driving a
shared family engine. Adding a comparable vendor is now a config file, not code —
and that is a tested property, not a claim: the suite adds a synthetic
thirteenth vendor by config alone and proves its bundle matches the library.

Highlights

• Vendor config layer (src/agentseam/data/vendors/): a schema plus one
  entry per agent, carrying events, field chains, claims markers, verdict
  dialects, hook-entry shapes — and per-claim evidence (basis/date/test);
  schema validation fails any claim without a basis. Every entry is derived by
  a committed recount tool that executes or AST-reads the source of truth,
  never hand-transcribed.
• Family engines replace bespoke adapters for claude_code, codex_cli,
  kimi_code, devin, gemini_cli, tabnine, junie, grok, cursor, windsurf and
  antigravity. vscode_copilot remains a dialect module by recorded design
  decision (its claims/parse logic branches on payload content).
• Bundles are engine + entry, trimmed per family: each single-file plugin
  now carries only the renderer grammars its gates speak, plus its own vendor
  literal, with a structural test enforcing exactly one of each.

Changed / deprecated

• Decision vocabulary aligned to the Agent Control Standard: ASK →
  ESCALATE, REWRITE → TRANSFORM. The old names and
  Decision.ask()/Decision.rewrite() remain as deprecated aliases (the
  classmethods emit DeprecationWarning). New WARN outcome; no adapted
  agent has an established warning channel yet, so it degrades to an
  honestly-labelled allow.
• matrix.capability() returns both "rewrite" and "transform" keys (same
  value) for one minor version; can_transform() joins can_rewrite().
• Breaking: degraded_from in a decision's evidence now reports the
  canonical spelling ("transform", not "rewrite").
• Bundle output bytes differ from 0.1.1 (comment strip + recomposition);
  regenerate vendored bundles with this version rather than diffing against
  0.1.1 output.

What did not change

The wire. Every payload → response pair an agent sees is byte-for-byte
identical to 0.1.1, enforced by a golden fixture suite (546 frozen wire
exchanges across all 12 agents) that every change in this release was gated
on and which was never regenerated.

Fixed

• tools/capture.py probe file permissions tightened to 0o700 (CodeQL
  py/overly-permissive-file).
• matrix.json's kimi_code row named the wrong config file; corrected via
  recount, evidence record untouched.
• pyproject.toml's version is now test-checked against
  agentseam.__version__ (a wheel can no longer ship disagreeing).
• CI installs from hash-pinned lockfiles; OSSF Scorecard Pinned-Dependencies
  4 → 10.

Full detail: CHANGELOG.md.