apiwells 0.1.0__tar.gz → 0.2.1__tar.gz

apiwells-0.2.1/CHANGELOG.md

@@ -0,0 +1,42 @@
+# Changelog
+
+## Unreleased
+
+No unreleased changes are recorded yet.
+
+## 0.2.1 — 2026-09-28
+
+- Correct the PyPI-facing README and package metadata.
+- Make the README and v0.2 specification patch-version-neutral.
+- Add verified repository and issue project URLs.
+- Replace repository-relative README documentation links with PyPI-safe
+  absolute GitHub links.
+- No runtime diagnostic behavior changes.
+
+## 0.2.0 — 2026-09-28
+
+- Add Basic connectivity/authentication/models diagnostics and explicit-model
+  Deep capability diagnostics while retaining legacy `--chat` behavior.
+- Validate Streaming/SSE and report client TTFT and total latency.
+- Parse provider-reported Usage without estimating missing token counts.
+- Validate Tool Calling through the complete local-tool/two-request round trip.
+- Validate Structured Output against JSON Schema, distinguishing strict schema
+  support from JSON-object-only behavior.
+- Separate probe execution status from capability support.
+- Add a shared error taxonomy and centralized secret redaction.
+- Add versioned structured JSON reporting alongside compatibility reports.
+- Validate live endpoint compatibility with three preserved ED-031 records;
+  results remain point-in-time observations, including partial capabilities.
+- Validate local wheel/sdist packaging and Windows clean installation, including
+  Basic and critical Deep smoke checks and 43 clean-wheel integration tests.
+- Document Local-First/no-telemetry behavior, security boundaries, test coverage
+  and completed release validation.
+- Complete RC/TestPyPI acceptance and cross-platform CI on Ubuntu, Windows and
+  macOS; publish to production PyPI and verify artifact identity, clean
+  installation, CLI/JSON contracts, real-provider Basic smoke, secret safety
+  and the five-minute onboarding target.
+
+## 0.1.0
+- Add a single-request models endpoint check and opt-in text chat smoke check.
+- Add HTTP/network failure categories, response shape checks and sanitized JSON.
+- Disable redirects, retries and implicit environment proxy use.

apiwells-0.2.1/PKG-INFO

@@ -0,0 +1,194 @@
+Metadata-Version: 2.4
+Name: apiwells
+Version: 0.2.1
+Summary: Endpoint Doctor for OpenAI-compatible model APIs
+License-Expression: MIT
+Project-URL: Repository, https://github.com/apiwells/endpoint-doctor
+Project-URL: Issues, https://github.com/apiwells/endpoint-doctor/issues
+Keywords: api,diagnostics,llm,endpoint
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: jsonschema<5,>=4.26
+Dynamic: license-file
+
+# ApiWells Endpoint Doctor
+
+A Local-First CLI for diagnosing OpenAI-compatible model API endpoints from
+your machine. Endpoint Doctor checks connectivity and protocol capabilities;
+it does not score model quality. Python 3.10+ is required.
+
+Runtime dependencies include `jsonschema` for Structured Output validation.
+
+## Install
+
+Install the latest release from PyPI:
+
+```sh
+python -m pip install --upgrade apiwells
+apiwells --version
+```
+
+`apiwells --version` reports the installed package version.
+
+Install this local checkout with:
+
+```sh
+python -m pip install .
+```
+
+## Basic Doctor
+
+Set `APIWELLS_API_KEY` using your shell's secret-input mechanism. Do not put a
+real key in a command, screenshot, issue or repository. Use `--api-key-env NAME`
+to select another environment variable.
+
+```sh
+apiwells doctor --base-url https://YOUR-API-HOST/v1
+apiwells doctor --base-url https://YOUR-API-HOST/v1 --v2-json
+```
+
+Basic is the default mode: **URL → DNS → TLS → HTTP → Authentication → /models**.
+It sends no inference request. HTTP, authentication and model-list checks share
+one GET to `BASE/models`. An empty model list can pass the response-shape check;
+a model list alone does not prove inference works.
+
+Supply the exact API base: `/v1` is not added automatically. For a gateway with
+`/openai/v1`, include that prefix. Do not supply the full `/models` or
+`/chat/completions` URL.
+
+For a local unauthenticated development server:
+
+```sh
+apiwells doctor --base-url http://127.0.0.1:3000/v1 --anonymous
+```
+
+## Deep Doctor
+
+```sh
+apiwells doctor --base-url https://YOUR-API-HOST/v1 --deep --model YOUR-MODEL-ID
+apiwells doctor --base-url https://YOUR-API-HOST/v1 --deep --model YOUR-MODEL-ID --v2-json
+```
+
+Deep requires an explicit, nonempty model ID and follows:
+**Basic → Chat → Streaming/SSE → Usage → Tool Calling → Structured Output**.
+Usage is extracted from Chat and Streaming responses, not a separate request.
+Capability probes run only after Basic passes and the requested model is found.
+
+Deep makes multiple potentially billable inference requests:
+
+- Chat validates a nonempty assistant text response.
+- Streaming validates SSE framing, output and terminal `[DONE]`; it reports
+  TTFT and total latency. TTFT is measured from request start to the first valid
+  model-output event. HTTP headers, keepalive, role-only, empty and metadata-only
+  events do not count.
+- Usage contains provider-reported token counts only. Missing values remain
+  unavailable or null; ApiWells never estimates them.
+- Tool Calling must complete a full round trip: tool call, validated arguments,
+  local diagnostic tool execution, tool result, second request and a final
+  response using that result. Merely accepting `tools` is insufficient.
+- Structured Output must return JSON that passes the requested JSON Schema.
+  An explicit rejection of `json_schema` as unsupported can trigger one
+  additional, potentially billable `json_object` sub-test. JSON-object-only
+  success does not certify strict JSON Schema support.
+
+There are no hidden billable retries or fallback models. The Tool Calling
+second request and conditional Structured Output sub-test are diagnostic steps,
+with request counts included in their results. `--max-tokens` controls applicable
+generation budgets and is not a guaranteed total cost ceiling; diagnostic
+sub-tests may use bounded request parameters. Provider support varies; not every
+endpoint supports every capability.
+
+## Legacy chat compatibility
+
+```sh
+apiwells doctor --base-url https://YOUR-API-HOST/v1 --chat --model YOUR-MODEL-ID --json
+```
+
+Legacy `--chat` remains a single, opt-in, potentially billable non-streaming
+request to `BASE/chat/completions`, with `Reply OK.` and default `max_tokens=8`.
+A pass requires nonempty assistant text, not exactly `OK`. Use `--max-tokens 32`
+to change the budget; some models need more output tokens. It performs no
+automatic retry or fallback model selection. `--chat` and `--deep` are mutually
+exclusive.
+
+## Results and timing
+
+Probe execution status (`PASS`, `FAIL`, `PARTIAL`) is separate from capability
+support (`SUPPORTED`, `UNSUPPORTED`, `UNKNOWN`, `NOT_APPLICABLE`). A failed or
+partial probe with unknown support does not establish that a capability is
+unsupported. Core failures make the overall result FAIL; non-passing
+Streaming, Tool Calling or Structured Output probes make it PARTIAL when core
+checks pass.
+
+The exit-code contract remains:
+
+| Code | Meaning |
+|---|---|
+| `0` | Selected check / overall diagnostics passed |
+| `1` | Endpoint diagnostics did not pass, including an overall PARTIAL |
+| `2` | Local usage or configuration error |
+
+For Basic/Deep, `--v2-json` writes a versioned JSON report with
+`schema_version: "1"`, `apiwells_version`, `overall_status` and `probes`.
+Each probe includes status, support, summary, metrics, evidence and error code.
+The report schema version is independent of the package version.
+`--json` retains the compatibility report with `ok`; legacy `--chat --json`
+retains its single-check report. Use `--json`, not `--v2-json`, for legacy chat.
+Completed checks produce one JSON object on stdout; usage/configuration errors
+go to stderr and do not produce a JSON report.
+
+Error codes distinguish configuration, DNS/TLS/connectivity/timeout, HTTP/auth,
+JSON/schema, SSE/interruption and capability validation failures. They are
+diagnostic evidence, not definitive root-cause conclusions.
+
+`--timeout 15` is a socket-operation timeout, not an overall deadline. Client
+TTFT and total latency include transport effects and are not server-only
+inference timings. Legacy `elapsed_ms` is request/response elapsed time, not
+streaming TTFT.
+
+## Security and boundaries
+
+- Local-First execution; no telemetry or hidden upload of prompts, responses or
+  usage. Requested diagnostic traffic goes to the endpoint you select.
+- API keys and Authorization header values must not be printed. Centralized
+  redaction protects console/JSON reports and error paths; raw provider bodies
+  are not dumped into reports. Review reports before sharing.
+- HTTPS certificate verification stays enabled. Remote HTTP requires
+  `--allow-http`; literal loopback addresses and localhost are allowed for
+  development.
+- All redirects, including same-host redirects, are blocked so credentials are
+  not forwarded to redirect destinations.
+- Environment proxies are ignored unless `--use-env-proxy` is supplied.
+- Test only endpoints you are authorized to test. Private/local destinations are
+  intentionally allowed; this CLI is not an unrestricted server-side URL fetcher.
+
+See [Security](https://github.com/apiwells/endpoint-doctor/blob/main/SECURITY.md) for handling and reporting guidance.
+
+## Compatibility and development
+
+[Compatibility](https://github.com/apiwells/endpoint-doctor/blob/main/docs/COMPATIBILITY.md) indexes three point-in-time ED-031 live
+certification records. These establish observed endpoint behavior, not
+universal provider support or model quality.
+
+[The release-facing specification](https://github.com/apiwells/endpoint-doctor/blob/main/docs/V0.2_SPEC.md) summarizes the frozen
+v0.2 scope. Benchmark, scoring/ranking, recommendations, cost optimization,
+Router, Gateway, long-term Monitoring, Web Dashboard, SaaS accounts, cloud
+telemetry and complete Responses API coverage are outside that scope.
+
+For test coverage and the observed QA harness dependencies, see
+[the test plan](https://github.com/apiwells/endpoint-doctor/blob/main/docs/TEST_PLAN.md). With the test harness installed, run:
+
+```sh
+python -m pytest tests -q
+```
+
+See [the release checklist](https://github.com/apiwells/endpoint-doctor/blob/main/docs/RELEASE_CHECKLIST.md) for release evidence,
+and [the changelog](https://github.com/apiwells/endpoint-doctor/blob/main/CHANGELOG.md) for version history and changes.
+License: MIT.

apiwells-0.2.1/README.md

@@ -0,0 +1,174 @@
+# ApiWells Endpoint Doctor
+
+A Local-First CLI for diagnosing OpenAI-compatible model API endpoints from
+your machine. Endpoint Doctor checks connectivity and protocol capabilities;
+it does not score model quality. Python 3.10+ is required.
+
+Runtime dependencies include `jsonschema` for Structured Output validation.
+
+## Install
+
+Install the latest release from PyPI:
+
+```sh
+python -m pip install --upgrade apiwells
+apiwells --version
+```
+
+`apiwells --version` reports the installed package version.
+
+Install this local checkout with:
+
+```sh
+python -m pip install .
+```
+
+## Basic Doctor
+
+Set `APIWELLS_API_KEY` using your shell's secret-input mechanism. Do not put a
+real key in a command, screenshot, issue or repository. Use `--api-key-env NAME`
+to select another environment variable.
+
+```sh
+apiwells doctor --base-url https://YOUR-API-HOST/v1
+apiwells doctor --base-url https://YOUR-API-HOST/v1 --v2-json
+```
+
+Basic is the default mode: **URL → DNS → TLS → HTTP → Authentication → /models**.
+It sends no inference request. HTTP, authentication and model-list checks share
+one GET to `BASE/models`. An empty model list can pass the response-shape check;
+a model list alone does not prove inference works.
+
+Supply the exact API base: `/v1` is not added automatically. For a gateway with
+`/openai/v1`, include that prefix. Do not supply the full `/models` or
+`/chat/completions` URL.
+
+For a local unauthenticated development server:
+
+```sh
+apiwells doctor --base-url http://127.0.0.1:3000/v1 --anonymous
+```
+
+## Deep Doctor
+
+```sh
+apiwells doctor --base-url https://YOUR-API-HOST/v1 --deep --model YOUR-MODEL-ID
+apiwells doctor --base-url https://YOUR-API-HOST/v1 --deep --model YOUR-MODEL-ID --v2-json
+```
+
+Deep requires an explicit, nonempty model ID and follows:
+**Basic → Chat → Streaming/SSE → Usage → Tool Calling → Structured Output**.
+Usage is extracted from Chat and Streaming responses, not a separate request.
+Capability probes run only after Basic passes and the requested model is found.
+
+Deep makes multiple potentially billable inference requests:
+
+- Chat validates a nonempty assistant text response.
+- Streaming validates SSE framing, output and terminal `[DONE]`; it reports
+  TTFT and total latency. TTFT is measured from request start to the first valid
+  model-output event. HTTP headers, keepalive, role-only, empty and metadata-only
+  events do not count.
+- Usage contains provider-reported token counts only. Missing values remain
+  unavailable or null; ApiWells never estimates them.
+- Tool Calling must complete a full round trip: tool call, validated arguments,
+  local diagnostic tool execution, tool result, second request and a final
+  response using that result. Merely accepting `tools` is insufficient.
+- Structured Output must return JSON that passes the requested JSON Schema.
+  An explicit rejection of `json_schema` as unsupported can trigger one
+  additional, potentially billable `json_object` sub-test. JSON-object-only
+  success does not certify strict JSON Schema support.
+
+There are no hidden billable retries or fallback models. The Tool Calling
+second request and conditional Structured Output sub-test are diagnostic steps,
+with request counts included in their results. `--max-tokens` controls applicable
+generation budgets and is not a guaranteed total cost ceiling; diagnostic
+sub-tests may use bounded request parameters. Provider support varies; not every
+endpoint supports every capability.
+
+## Legacy chat compatibility
+
+```sh
+apiwells doctor --base-url https://YOUR-API-HOST/v1 --chat --model YOUR-MODEL-ID --json
+```
+
+Legacy `--chat` remains a single, opt-in, potentially billable non-streaming
+request to `BASE/chat/completions`, with `Reply OK.` and default `max_tokens=8`.
+A pass requires nonempty assistant text, not exactly `OK`. Use `--max-tokens 32`
+to change the budget; some models need more output tokens. It performs no
+automatic retry or fallback model selection. `--chat` and `--deep` are mutually
+exclusive.
+
+## Results and timing
+
+Probe execution status (`PASS`, `FAIL`, `PARTIAL`) is separate from capability
+support (`SUPPORTED`, `UNSUPPORTED`, `UNKNOWN`, `NOT_APPLICABLE`). A failed or
+partial probe with unknown support does not establish that a capability is
+unsupported. Core failures make the overall result FAIL; non-passing
+Streaming, Tool Calling or Structured Output probes make it PARTIAL when core
+checks pass.
+
+The exit-code contract remains:
+
+| Code | Meaning |
+|---|---|
+| `0` | Selected check / overall diagnostics passed |
+| `1` | Endpoint diagnostics did not pass, including an overall PARTIAL |
+| `2` | Local usage or configuration error |
+
+For Basic/Deep, `--v2-json` writes a versioned JSON report with
+`schema_version: "1"`, `apiwells_version`, `overall_status` and `probes`.
+Each probe includes status, support, summary, metrics, evidence and error code.
+The report schema version is independent of the package version.
+`--json` retains the compatibility report with `ok`; legacy `--chat --json`
+retains its single-check report. Use `--json`, not `--v2-json`, for legacy chat.
+Completed checks produce one JSON object on stdout; usage/configuration errors
+go to stderr and do not produce a JSON report.
+
+Error codes distinguish configuration, DNS/TLS/connectivity/timeout, HTTP/auth,
+JSON/schema, SSE/interruption and capability validation failures. They are
+diagnostic evidence, not definitive root-cause conclusions.
+
+`--timeout 15` is a socket-operation timeout, not an overall deadline. Client
+TTFT and total latency include transport effects and are not server-only
+inference timings. Legacy `elapsed_ms` is request/response elapsed time, not
+streaming TTFT.
+
+## Security and boundaries
+
+- Local-First execution; no telemetry or hidden upload of prompts, responses or
+  usage. Requested diagnostic traffic goes to the endpoint you select.
+- API keys and Authorization header values must not be printed. Centralized
+  redaction protects console/JSON reports and error paths; raw provider bodies
+  are not dumped into reports. Review reports before sharing.
+- HTTPS certificate verification stays enabled. Remote HTTP requires
+  `--allow-http`; literal loopback addresses and localhost are allowed for
+  development.
+- All redirects, including same-host redirects, are blocked so credentials are
+  not forwarded to redirect destinations.
+- Environment proxies are ignored unless `--use-env-proxy` is supplied.
+- Test only endpoints you are authorized to test. Private/local destinations are
+  intentionally allowed; this CLI is not an unrestricted server-side URL fetcher.
+
+See [Security](https://github.com/apiwells/endpoint-doctor/blob/main/SECURITY.md) for handling and reporting guidance.
+
+## Compatibility and development
+
+[Compatibility](https://github.com/apiwells/endpoint-doctor/blob/main/docs/COMPATIBILITY.md) indexes three point-in-time ED-031 live
+certification records. These establish observed endpoint behavior, not
+universal provider support or model quality.
+
+[The release-facing specification](https://github.com/apiwells/endpoint-doctor/blob/main/docs/V0.2_SPEC.md) summarizes the frozen
+v0.2 scope. Benchmark, scoring/ranking, recommendations, cost optimization,
+Router, Gateway, long-term Monitoring, Web Dashboard, SaaS accounts, cloud
+telemetry and complete Responses API coverage are outside that scope.
+
+For test coverage and the observed QA harness dependencies, see
+[the test plan](https://github.com/apiwells/endpoint-doctor/blob/main/docs/TEST_PLAN.md). With the test harness installed, run:
+
+```sh
+python -m pytest tests -q
+```
+
+See [the release checklist](https://github.com/apiwells/endpoint-doctor/blob/main/docs/RELEASE_CHECKLIST.md) for release evidence,
+and [the changelog](https://github.com/apiwells/endpoint-doctor/blob/main/CHANGELOG.md) for version history and changes.
+License: MIT.

apiwells-0.2.1/docs/COMPATIBILITY.md

@@ -0,0 +1,41 @@
+# v0.2 Compatibility
+
+The ED-031 compatibility records below were captured before the package version
+was synchronized to 0.2.0. Their recorded package/build versions are preserved
+as historical point-in-time evidence and must not be rewritten to match the
+later final release version. Endpoint Doctor v0.2.0 was subsequently released
+on **2026-09-28**. Production Basic smoke and cross-platform CI do not replace
+these historical capability observations.
+
+ED-031 real endpoint/provider live validation is **CLOSED / PASS**. This page is
+a release-facing index; the historical
+[compatibility matrix](compatibility/compatibility-matrix.md) and individual
+records remain the authoritative detailed evidence. An overall PARTIAL record
+does not mean that the ED-031 validation work package failed.
+
+| Record | Provider | Model | Test date | ApiWells version | Overall |
+|---|---|---|---|---|---|
+| [MODEL-0001](compatibility/model0001-deepseek-flash.md) | DeepSeek Official | `deepseek-flash` | 2026-09-24 | 0.1.0 (v0.2 development build) | PARTIAL |
+| [MODEL-0002](compatibility/model0002-alibaba-qwen37-plus.md) | Alibaba Cloud Model Studio | `qwen3.7-plus` | 2026-09-27 | 0.1.0 (v0.2 development build) | PASS |
+| [MODEL-0003](compatibility/model0003-openrouter-ling30-flash-fin.md) | OpenRouter | `inclusionai/ling-3.0-flash-fin:free` | 2026-09-27 | 0.1.0 (v0.2 development build) | PARTIAL |
+
+## Interpretation
+
+- Results are point-in-time observations for the recorded endpoint, model,
+  configuration and date, not permanent provider guarantees.
+- Probe execution status and capability support are separate concepts.
+  `FAIL / UNKNOWN` does not establish permanent lack of support;
+  `PARTIAL / UNKNOWN` does not mean unsupported.
+- Tool Calling certification requires the full round trip, and Structured
+  Output certification requires successful JSON Schema validation. Request
+  acceptance alone is insufficient.
+- Some historical records use `AVAILABLE` for Usage. This is a
+  compatibility-record-local label meaning provider-reported usage data was
+  returned and parsed. It does not add a new ProbeResult support enum; those
+  remain `SUPPORTED`, `UNSUPPORTED`, `UNKNOWN` and `NOT_APPLICABLE`.
+- Compatibility evidence is not a model-quality Benchmark, ranking or
+  recommendation. Timings are observations, not a performance guarantee.
+
+Detailed metrics and qualifications belong to the linked ED-031 records and
+are not duplicated here. ED-032 Windows clean-install smoke evidence validates
+installation and execution; its metrics do not replace ED-031 measurements.

apiwells-0.2.1/docs/RELEASE_CHECKLIST.md

@@ -0,0 +1,106 @@
+# v0.2.0 Release Checklist
+
+Release date: **2026-09-28**
+
+Release status: **CLOSED / PASS**
+
+Release source: `cac558b543336f42d17b8db99bfacd6e53d1e5dd`
+
+Release tag: `v0.2.0` (annotated)
+
+Production package: `apiwells==0.2.0`
+
+Public release-facing specification: [V0.2_SPEC.md](V0.2_SPEC.md).
+
+This completed release record reflects the acceptance evidence established
+during ED-034, ED-035 and the post-release production acceptance. ED-036 only
+reconciles the repository documentation with those already-confirmed results;
+it does not represent a new build, publication or execution of acceptance tests.
+
+## Canonical final artifacts
+
+| Artifact | Filename |
+|---|---|
+| Wheel | `apiwells-0.2.0-py3-none-any.whl` |
+| sdist | `apiwells-0.2.0.tar.gz` |
+
+Wheel SHA256:
+
+```text
+AC346E77ADA9B376420BD9F3B83FDA1CAB2CFD89F80598A5937162F1EDF03168
+```
+
+sdist SHA256:
+
+```text
+CBD4D357E2DE397951B35D499A12AC89C3002F34E614634A1BFF12ECE35C32A3
+```
+
+These identify the canonical final release artifacts. The release source,
+annotated tag and published artifacts are unchanged by this documentation pass.
+
+## Completed release checklist
+
+- [x] Frozen scope validation.
+- [x] Package and CLI version synchronized to **0.2.0**.
+- [x] Unit tests.
+- [x] Mock integration tests.
+- [x] Secret leak validation.
+- [x] ED-031 real-provider compatibility evidence: **CLOSED / PASS**.
+- [x] ED-033 release documentation reviewed and accepted.
+- [x] ED-034 Windows formal RC acceptance.
+- [x] Wheel build.
+- [x] sdist build.
+- [x] `twine check`.
+- [x] TestPyPI publication.
+- [x] TestPyPI artifact identity.
+- [x] TestPyPI clean install.
+- [x] TestPyPI Basic smoke.
+- [x] Cross-platform CI — Ubuntu: **PASS**.
+- [x] Cross-platform CI — Windows: **PASS**.
+- [x] Cross-platform CI — macOS: **PASS**.
+- [x] Annotated `v0.2.0` tag created and pushed.
+- [x] ED-035 production PyPI publication.
+- [x] Production PyPI artifact identity.
+- [x] Fresh production PyPI clean install.
+- [x] `apiwells --version`: **PASS**, reports `apiwells 0.2.0`.
+- [x] `apiwells --help`: **PASS**.
+- [x] `apiwells doctor --help`: **PASS**.
+- [x] `pip check`: **PASS**.
+- [x] Production real-provider Basic smoke: **PASS**.
+- [x] v2 JSON contract: **PASS**.
+- [x] Secret not present in stdout/stderr.
+- [x] Temporary API key removed after testing.
+- [x] ≤5 minute onboarding target: **PASS**.
+- [x] Final release: **CLOSED / PASS**.
+
+## Evidence boundaries
+
+Cross-platform CI PASS is not macOS/Linux real-provider live-validation PASS.
+The production Basic smoke establishes the recorded Basic checks, not every
+Deep capability on every provider. The release record makes no claim that
+every Python version was tested or every provider capability passed.
+
+ED-031 compatibility results remain point-in-time evidence for their original
+endpoint, model, build and test date. Later production smoke and CI results
+do not replace those observations.
+
+## Historical evidence preserved
+
+- **ED-031 — CLOSED / PASS:** the [compatibility index](COMPATIBILITY.md) links
+  the authoritative matrix and MODEL-0001, MODEL-0002 and MODEL-0003 records.
+  Their original build versions, dates, metrics and PASS/PARTIAL results remain
+  unchanged.
+- **ED-032 — CLOSED / PASS:** local wheel + sdist build PASS, Windows Basic
+  real-endpoint smoke PASS, clean-wheel integration **43 passed**, critical
+  Deep smoke PASS and no secret leak observed. These are historical Windows
+  acceptance results, separate from ED-034 RC and production PyPI acceptance.
+- **TESTENV-01:** the observed ED-032 Windows harness used pytest **9.1.1**,
+  pytest-httpserver **1.1.5** and Werkzeug **3.1.8**. These are test dependencies,
+  not ApiWells runtime dependencies. See [TEST_PLAN.md](TEST_PLAN.md).
+- [0.1.0 validation](releases/0.1.0/VALIDATION.md) remains historical evidence for
+  that release; it is not relabeled as v0.2.0 acceptance.
+
+VERSION-01 was completed by synchronizing both version declarations to 0.2.0
+before the formal release. No version bump or version-source refactor is part
+of ED-036. ED-031 and ED-032 remain closed.