v0.4.0

What's changed in v0.4.0

npm: npm install ctscout-mcp-server@0.4.0 or npx ctscout-mcp-server@0.4.0

Added

• ctscout_submit_deep_dive (POST /jobs) and ctscout_get_job
  (GET /jobs/{id}): asynchronous Pro deep dives per ctscout-worker#344
  contract v1. Submit returns a receipt; poll with backoff (30 s → 5 min) for
  a result identical to a Pro /scan plus the worker-set snapshot,
  worker_version and signals_attempted. VLM is not part of v1. Job
  errors map 403 → Pro required (with the API's upgrade text), 404 → not
  your job / unknown id, 429 → daily jobs quota (#107)
• outputSchema on all three tools, enforced by the SDK against every
  structuredContent; proxied fields stay open so upstream additions widen
  rather than break the tool (#100)
• snapshot (warehouse/D1 sync date) and snapshot_source (scan |
  unavailable) on every response, read from the API payload when it carries
  one; no independent fallback request, so a missing date is reported as
  unknown rather than guessed. Markdown output carries the same line (#100)

Changed

• ctscout_search_company description, README and LIMITATIONS no longer carry a
  hand-typed warehouse size (the three disagreed with each other and with the
  live site); all point at https://ctscout.dev/stats instead (#101)
• Result wording is consistently "attributed" (cert-subject attribution) vs
  "candidate" (semantic name similarity, not an attribution); every table's
  organization column is "Attributed to" and the candidate table is labelled
  as candidates. Tool descriptions document match_type, candidates,
  org_match_strategy, empty_reason, and that first_seen/last_seen are
  warehouse observation times, not CT SCT times (#100)