v0.1.1

AgentAPI Doctor v0.1.1

Summary

v0.1.1 is a focused diagnostic patch for the supported AgentAPI Doctor CLI.
Terminal exactly-once failures now show a bounded ordered trace of the observed
terminal markers, including the logical SSE event index, so a result such as
Observed: 2 can be explained as response.completed followed by [DONE].

The release also freezes an offline OpenAI Responses boundary case for
response.incomplete with incomplete_details.reason=max_output_tokens.
Complete and missing provider usage are both covered through normal
four-request product runs; no live-provider request or fifth Quick Check was
added.

Compatibility and breaking changes

There are no changes to commands, configuration, schemas, report-envelope
versions, exit codes, request count, request budgets, or built-in candidate
pack/profile identities. Existing v0.1.0 baselines remain comparable.

For a terminal_event_count failure, an assertion's schema-permitted
observed value changes from a number to an object containing
terminal_count, framing_complete, terminal_trace, and
trace_entries_omitted. Consumers that inspect this diagnostic field directly
must accept the structured value. Because finding fingerprints bind observed
evidence, a rerun of an existing terminal-count failure receives a new
fingerprint; verdicts and unrelated findings are unchanged.

Migration

No configuration, baseline, or stored-report migration is required. Install
the v0.1.1 binary and rerun the affected check to obtain the richer terminal
trace. Automation that reads AssertionResult.observed for
terminal_event_count should switch from a numeric assumption to the named
object fields above.

Do not relabel or edit prior evidence. Historical v0.1.0 reports remain
readable and retain their original fingerprints and observations.

Known issues

• The built-in protocol interpretations remain
  0.1.0-candidate.3 / pending_review; this patch improves evidence but does
  not turn a bounded Quick Check into vendor certification.
• Under the current candidate interpretation, a Responses
  response.completed followed by [DONE] is reported as two terminal
  markers. The new trace explains that result but does not attribute it to an
  endpoint, proxy, SDK, or normalization layer.
• OpenAI Chat and Responses terminal-status checks request 512 output tokens;
  structural checks remain at 64. These provider-side limits are not billing
  ceilings, and an honest output-limit result remains INCONCLUSIVE.
• Provider usage is optional diagnostic evidence. Missing usage remains
  unknown and does not become a target failure or an observed zero. Doctor
  does not perform price calculations.
• content_filter fixture taxonomy is unchanged in this patch pending a
  separately reviewed terminal-outcome contract.

Support window

Support begins when the immutable v0.1.1 GitHub Release becomes public and
ends on 2026-10-14 or when a newer 0.1.x release supersedes it, whichever
comes first. Publication supersedes the v0.1.0 support window; its immutable
artifacts remain available for historical reproduction.

Support is best-effort and covers security and critical Doctor defects. It does
not establish support for the experimental Registry, authored packs, generic
drivers, package-manager candidates, or a hosted service.

Verification

The exact immutable v0.1.1 tag binds these notes to a protected-main
commit. The release workflow reruns the complete offline product gate, race
tests, the locked OpenAI Python SDK cases, release-tool checks, archive smoke
tests, and public post-publication verification.

Six native archives must report version 0.1.1, the tagged commit, and Go
1.26.5. Checksums, the SPDX SBOM, GitHub build provenance, and the keyless
Sigstore bundle bind the nine-file allowlisted release asset set. No external
security review, vendor endorsement, or arbitrary-endpoint compatibility claim
is implied by those checks.