v1.0.1

Additive guidance and field evidence. The runtime code is unchanged from 1.0.0; this is a guidance/docs
patch, and the frozen contract (the loop and routing gate, the lane map and four bundled agents, the
RunRecord ledger shape, MCP-via-.mcp.json) is untouched.

• Verify-step guidance: one line on assessing advisory/dependency reachability before acting — fix
  what the code actually calls, document what it does not, and defer to a security-review skill or
  references/Security.md when the project provides one.
• Field notes Run 8: a real security-remediation run where reachability tracing surfaced a
  command-injection RCE (in two duplicate paths) that a 437-alert dependency scan and the test suite
  both missed. Existence-and-severity evidence, not a frequency claim; injection itself is a known
  pattern a SAST scanner owns.
• README: storefront polish (renders off-GitHub, concrete use cases, a regulated-fitness line) and
  one honest security-use-case line.
• Evidence chart: the "When Baton helps" figure now plots Run 8 (a NestJS security remediation) as a
  fourth field project, where a separate audit pass caught what the unit tests and the dependency scan
  missed; chart source committed at docs/make-evidence-chart.R.