v0.1.0-rc.1

AgentAPI Doctor v0.1.0-rc.1

Summary

This first release candidate packages the doctor command as a native binary
for Linux, macOS, and Windows on amd64 and arm64. It provides a credential-free
offline demo and bounded raw-HTTP checks for the OpenAI Chat Completions,
OpenAI Responses, and Anthropic Messages API shapes.

This is an evaluation release for early users. It is not a vendor
certification, a complete protocol conformance suite, or proof that a specific
SDK or Agent works with an endpoint.

Compatibility and breaking changes

There is no earlier tagged AgentAPI Doctor release to remain compatible with.
The CLI, configuration, report, evidence, pack, and profile schemas are
pre-1.0 contracts and may change in a later release candidate with documented
migration guidance.

Each endpoint run selects four candidate raw-HTTP checks for one configured API
shape. The larger Requirement Catalog is metadata and does not represent an
equal number of executable tests. Real SDK and Agent execution is not included
in this release candidate.

Migration

Users of an untagged source build should replace that binary with the exact
archive for this release and confirm doctor version --json reports
0.1.0-rc.1. Existing local run records remain private local state; archive or
remove them according to the data policy rather than copying them into the
installation directory.

No Registry, reference-server, OCI image, Homebrew tap, Scoop bucket, composite
Action, or reusable workflow is published as a supported v0.1.0-rc.1 install
channel. Their repository files remain development candidates.

Known issues

• The release executes raw HTTP checks only; it does not run a real OpenAI,
  Anthropic, Vercel AI, or Agent client.
• A PASS is bound to the exact endpoint, model, built-in profile and pack
  digests, and four executed checks. It is not a broad compatibility claim.
• Each request asks the provider for at most 64 output tokens, but the provider
  may reject or ignore that field. It is not an enforced cost ceiling.
• The CLI stores redacted evidence under .agentapi/. Redaction is not
  anonymization: structured model output and tool arguments may remain and
  must be reviewed before sharing.
• There is no project-operated hosted verifier, public Registry, compatibility
  matrix, telemetry service, or long-term support commitment.
• Windows release archives use ZIP; Linux and macOS archives use tar.gz.

Support window

Support for this release candidate begins when the GitHub Release becomes
public and ends on 2026-08-13 or when a newer release candidate or stable
release supersedes it, whichever occurs first. Security reports remain welcome
after that date, but fixes may require upgrading to a newer release.

Verification

The release tag identifies the exact source commit. doctor version --json
inside every archive reports the release version and that full commit ID.

The release workflow builds six archives, publishes checksums.txt and one
SPDX JSON SBOM, signs the checksum manifest with Sigstore keyless signing, and
records GitHub build-provenance attestations for every published file. Before
publication it verifies the signature against the exact tag-bound workflow
identity. Linux amd64, macOS arm64, and Windows amd64 runners verify the
complete asset set, extract their native archive, run version --json, and run
the credential-free demo. After publication, the same representative
platforms download the archive, checksum manifest, and signature bundle without
an authorization header, verify the signature and checksum, and repeat the
smoke test within a two-minute packaging budget. Linux also executes the
public fixed-tag installer into a temporary user directory.

The canonical verification commands and certificate identity are documented in
docs/operations/release-verification.md. A failed workflow does not justify a
compatibility or publication claim.