apiwells 0.2.0__tar.gz → 0.2.1__tar.gz

{apiwells-0.2.0 → apiwells-0.2.1}/CHANGELOG.md

@@ -1,9 +1,19 @@
 # Changelog
 
-## Unreleased — v0.2 development
+## Unreleased
 
-The package and CLI remain at 0.1.0 (v0.2 development build); v0.2.0 has not
-been released.
+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.
@@ -20,7 +30,11 @@ been released.
 - 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 remaining release gates.
+  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.

{apiwells-0.2.0/src/apiwells.egg-info → apiwells-0.2.1}/PKG-INFO

@@ -1,8 +1,10 @@
 Metadata-Version: 2.4
 Name: apiwells
-Version: 0.2.0
+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
@@ -22,21 +24,18 @@ 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.
 
-This checkout is a **v0.2 development build**. The installed package and CLI
-version remain **0.1.0**; v0.2.0 has not been released. Runtime dependencies
-include `jsonschema` for Structured Output validation.
+Runtime dependencies include `jsonschema` for Structured Output validation.
 
 ## Install
 
-Install the current released package from PyPI:
+Install the latest release from PyPI:
 
 ```sh
-python -m pip install apiwells
+python -m pip install --upgrade apiwells
 apiwells --version
 ```
 
-The current repository contains v0.2 development work but remains at version
-0.1.0 until RC version synchronization. v0.2.0 has not been released to PyPI.
+`apiwells --version` reports the installed package version.
 
 Install this local checkout with:
 
@@ -44,8 +43,6 @@ Install this local checkout with:
 python -m pip install .
 ```
 
-The checkout's version command currently prints `apiwells 0.1.0`.
-
 ## Basic Doctor
 
 Set `APIWELLS_API_KEY` using your shell's secret-input mechanism. Do not put a
@@ -172,26 +169,26 @@ streaming TTFT.
 - 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](SECURITY.md) for handling and reporting guidance.
+See [Security](https://github.com/apiwells/endpoint-doctor/blob/main/SECURITY.md) for handling and reporting guidance.
 
 ## Compatibility and development
 
-[Compatibility](docs/COMPATIBILITY.md) indexes three point-in-time ED-031 live
+[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](docs/V0.2_SPEC.md) summarizes the frozen
+[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](docs/TEST_PLAN.md). With the test harness installed, run:
+[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](docs/RELEASE_CHECKLIST.md) for completed evidence
-and pending release gates, and [the changelog](CHANGELOG.md) for changes.
+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.0 → apiwells-0.2.1}/README.md

@@ -4,21 +4,18 @@ 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.
 
-This checkout is a **v0.2 development build**. The installed package and CLI
-version remain **0.1.0**; v0.2.0 has not been released. Runtime dependencies
-include `jsonschema` for Structured Output validation.
+Runtime dependencies include `jsonschema` for Structured Output validation.
 
 ## Install
 
-Install the current released package from PyPI:
+Install the latest release from PyPI:
 
 ```sh
-python -m pip install apiwells
+python -m pip install --upgrade apiwells
 apiwells --version
 ```
 
-The current repository contains v0.2 development work but remains at version
-0.1.0 until RC version synchronization. v0.2.0 has not been released to PyPI.
+`apiwells --version` reports the installed package version.
 
 Install this local checkout with:
 
@@ -26,8 +23,6 @@ Install this local checkout with:
 python -m pip install .
 ```
 
-The checkout's version command currently prints `apiwells 0.1.0`.
-
 ## Basic Doctor
 
 Set `APIWELLS_API_KEY` using your shell's secret-input mechanism. Do not put a
@@ -154,26 +149,26 @@ streaming TTFT.
 - 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](SECURITY.md) for handling and reporting guidance.
+See [Security](https://github.com/apiwells/endpoint-doctor/blob/main/SECURITY.md) for handling and reporting guidance.
 
 ## Compatibility and development
 
-[Compatibility](docs/COMPATIBILITY.md) indexes three point-in-time ED-031 live
+[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](docs/V0.2_SPEC.md) summarizes the frozen
+[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](docs/TEST_PLAN.md). With the test harness installed, run:
+[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](docs/RELEASE_CHECKLIST.md) for completed evidence
-and pending release gates, and [the changelog](CHANGELOG.md) for changes.
+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.0 → apiwells-0.2.1}/docs/COMPATIBILITY.md

@@ -1,5 +1,12 @@
 # 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

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.

{apiwells-0.2.0 → apiwells-0.2.1}/docs/TEST_PLAN.md

@@ -1,10 +1,11 @@
 # v0.2 Test Plan
 
-This plan covers the frozen Endpoint Doctor v0.2 scope summarized in
-[V0.2_SPEC.md](V0.2_SPEC.md). It describes required validation, not a claim that
-every release gate has passed. See [the release checklist](RELEASE_CHECKLIST.md)
-for evidence status. ED-031 and ED-032 remain closed; ED-033 does not rerun or
-reopen them.
+This plan describes validation methods and historical release evidence for the
+frozen Endpoint Doctor v0.2.0 scope in [V0.2_SPEC.md](V0.2_SPEC.md). The final
+release was completed on **2026-09-28**, with status **CLOSED / PASS**. See
+[the release checklist](RELEASE_CHECKLIST.md) for the completed acceptance
+record. ED-031 and ED-032 remain closed; this documentation reconciliation
+does not rerun or reopen them.
 
 ## 1. Unit testing
 
@@ -86,8 +87,8 @@ sanitized command/results evidence.
 ED-032 Windows clean-install testing is **CLOSED / PASS**. The supplied ED-032
 acceptance evidence records 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 prior observations, not new ED-033
-test runs.
+PASS and no secret leak observed. These remain historical ED-032 observations,
+separate from the subsequent formal RC and production-install acceptance.
 
 ### TESTENV-01: observed Windows QA harness
 
@@ -99,22 +100,25 @@ test runs.
 
 These are **test dependencies, not ApiWells runtime dependencies**. They describe
 the observed Windows clean-wheel integration environment, not a new supported
-dependency matrix. ED-033 neither adds them to runtime dependencies nor chooses
-a new dev-dependency packaging or management mechanism.
+dependency matrix. This record does not add them to runtime dependencies or
+choose a new dev-dependency packaging or management mechanism.
 
 ## 6. Cross-platform testing
 
-Validate the release candidate on Windows, macOS and Linux, including shell
-entry points, environment-key handling, TLS/proxy behavior, JSON encoding and
-exit codes. macOS and Linux each require installation, `--version`, `--help`,
-Basic smoke and the mock suite. Each platform run records OS, Python version
-and the tested artifact. Python must satisfy the declared `>=3.10` requirement.
-The Frozen Scope requires the specified Windows/macOS/Linux validation, not an
-exhaustive OS × Python-version matrix.
-
-Windows development-build acceptance is supported by ED-032. Remaining required
-platform validation and RC acceptance stay open until corresponding evidence
-exists. Historical 0.1.0 validation does not certify a v0.2 RC.
+The cross-platform validation method covers Windows, macOS and Linux,
+including shell entry points, environment-key handling, TLS/proxy behavior,
+JSON encoding and exit codes. macOS and Linux checks include installation,
+`--version`, `--help`, Basic smoke and the mock suite. Record whether a smoke
+test uses a local mock or a real provider. Each platform run records OS, Python
+version and the tested artifact. Python must satisfy the declared `>=3.10`
+requirement. The Frozen Scope requires the specified Windows/macOS/Linux
+validation, not an exhaustive OS × Python-version matrix.
+
+Ubuntu, Windows and macOS CI completed with **PASS**. Windows formal RC
+acceptance also completed with **PASS**, separately from historical ED-032
+acceptance. Cross-platform CI PASS does not establish macOS/Linux real-provider
+live validation. The production real-provider Basic smoke is separate evidence
+and does not replace ED-031 capability measurements.
 
 ## 7. Release evidence
 
@@ -123,10 +127,26 @@ provide credentials through environment variables or managed CI secrets.
 Keep unit/mock/secret-test summaries, sanitized compatibility records,
 build/metadata checks, artifact hashes and clean-install/platform results tied
 to the tested commit and artifact. Record failures and limitations as well as
-passes. Before formal RC/final artifacts, synchronize both version declarations
-to 0.2.0; they remain 0.1.0 in ED-033 (VERSION-01). A single version source is
-not decided here.
+passes. Both package version declarations were synchronized to **0.2.0** for
+the formal release. This documentation pass changes neither version declaration
+nor the version-source design.
+
+The following completed evidence was established during the v0.2.0 release
+process and post-release production acceptance. ED-036 records that existing
+evidence here; these are not new test runs performed by this documentation pass:
 
-TestPyPI, RC artifact/clean-install acceptance, remaining required validation,
-final PyPI release and post-release PyPI clean-install smoke are future gates,
-tracked in [RELEASE_CHECKLIST.md](RELEASE_CHECKLIST.md).
+| Stage | Completed evidence |
+|---|---|
+| ED-031 | Point-in-time real-endpoint capability certification; original build versions, dates and PASS/PARTIAL outcomes preserved |
+| ED-032 | Windows clean-wheel acceptance, including 43 integration tests and critical Deep smoke |
+| ED-034 | Windows formal RC acceptance; wheel/sdist builds and twine check; TestPyPI publication, artifact identity, clean install and Basic smoke |
+| Cross-platform CI | Ubuntu, Windows and macOS PASS; not a claim of macOS/Linux real-provider validation |
+| ED-035 | Annotated v0.2.0 tag, production PyPI publication and canonical artifact identity PASS |
+| Production post-release acceptance | Fresh PyPI install, CLI version/help, doctor help, pip check, real-provider Basic smoke, v2 JSON contract, secret safety, temporary key cleanup and the five-minute onboarding target PASS |
+
+Unit, mock integration and secret leak validation passed as part of the
+completed release acceptance. Final release status is **CLOSED / PASS**.
+The canonical release source, tag, artifact hashes and completed checklist are
+in [RELEASE_CHECKLIST.md](RELEASE_CHECKLIST.md). Historical compatibility
+evidence remains authoritative for its recorded tests and is not overwritten
+by later Basic smoke or CI results.

{apiwells-0.2.0 → apiwells-0.2.1}/docs/V0.2_SPEC.md

@@ -1,4 +1,4 @@
-# Endpoint Doctor v0.2: Release-Facing Specification
+# Endpoint Doctor v0.2.x: Release-Facing Specification
 
 ## Authority and purpose
 
@@ -6,16 +6,13 @@ Endpoint Doctor diagnoses connectivity and protocol compatibility for an
 OpenAI-compatible model API from the user's machine. It helps explain whether
 a selected endpoint/model can complete specific diagnostic requests.
 
-Endpoint Doctor v0.2 development was governed by the frozen engineering
-specification `Endpoint_Doctor_v0.2开发规范.md`, maintained as a project-level
-authority outside the repository release artifacts.
+This document is the public release-facing specification for the frozen
+v0.2 scope. It summarizes the project-level frozen engineering baseline;
+it does not replace, expand, or redefine the product scope.
 
-This document is the repository's concise release-facing specification. It
-summarizes that frozen baseline; it does not replace, expand, or redefine the
-v0.2 product scope.
-
-The current package/CLI version is **0.1.0 (v0.2 development build)**. This
-document does not announce a v0.2.0 release or authorize a version bump.
+Endpoint Doctor **v0.2.0**, released on **2026-09-28**, established the initial
+v0.2.x release baseline. Patch releases in the v0.2.x series may correct
+packaging, documentation or defects without expanding the frozen v0.2 scope.
 
 ## Modes and compatibility
 
@@ -109,8 +106,9 @@ capability.
 ED-031 live validation is CLOSED / PASS. Preserve the existing matrix and all
 three records linked in [COMPATIBILITY.md](COMPATIBILITY.md) as historical release
 evidence. ED-032 Windows clean-install validation is CLOSED / PASS; it does not
-replace ED-031 metrics. Remaining formal release gates are tracked in
-[RELEASE_CHECKLIST.md](RELEASE_CHECKLIST.md).
+replace ED-031 metrics. The final v0.2.0 release is **CLOSED / PASS**;
+[RELEASE_CHECKLIST.md](RELEASE_CHECKLIST.md) records completed release acceptance,
+the canonical source/tag and final artifact identities.
 
 ## Explicit non-goals
 

{apiwells-0.2.0 → apiwells-0.2.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "apiwells"
-version = "0.2.0"
+version = "0.2.1"
 description = "Endpoint Doctor for OpenAI-compatible model APIs"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -23,6 +23,10 @@ classifiers = [
   "Topic :: Software Development :: Testing",
 ]
 
+[project.urls]
+Repository = "https://github.com/apiwells/endpoint-doctor"
+Issues = "https://github.com/apiwells/endpoint-doctor/issues"
+
 [project.scripts]
 apiwells = "apiwells.cli:main"
 

{apiwells-0.2.0 → apiwells-0.2.1}/src/apiwells/__init__.py

@@ -1,2 +1,2 @@
 """Small diagnostics for OpenAI-compatible endpoints."""
-__version__ = "0.2.0"
+__version__ = "0.2.1"

{apiwells-0.2.0 → apiwells-0.2.1/src/apiwells.egg-info}/PKG-INFO

@@ -1,8 +1,10 @@
 Metadata-Version: 2.4
 Name: apiwells
-Version: 0.2.0
+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
@@ -22,21 +24,18 @@ 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.
 
-This checkout is a **v0.2 development build**. The installed package and CLI
-version remain **0.1.0**; v0.2.0 has not been released. Runtime dependencies
-include `jsonschema` for Structured Output validation.
+Runtime dependencies include `jsonschema` for Structured Output validation.
 
 ## Install
 
-Install the current released package from PyPI:
+Install the latest release from PyPI:
 
 ```sh
-python -m pip install apiwells
+python -m pip install --upgrade apiwells
 apiwells --version
 ```
 
-The current repository contains v0.2 development work but remains at version
-0.1.0 until RC version synchronization. v0.2.0 has not been released to PyPI.
+`apiwells --version` reports the installed package version.
 
 Install this local checkout with:
 
@@ -44,8 +43,6 @@ Install this local checkout with:
 python -m pip install .
 ```
 
-The checkout's version command currently prints `apiwells 0.1.0`.
-
 ## Basic Doctor
 
 Set `APIWELLS_API_KEY` using your shell's secret-input mechanism. Do not put a
@@ -172,26 +169,26 @@ streaming TTFT.
 - 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](SECURITY.md) for handling and reporting guidance.
+See [Security](https://github.com/apiwells/endpoint-doctor/blob/main/SECURITY.md) for handling and reporting guidance.
 
 ## Compatibility and development
 
-[Compatibility](docs/COMPATIBILITY.md) indexes three point-in-time ED-031 live
+[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](docs/V0.2_SPEC.md) summarizes the frozen
+[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](docs/TEST_PLAN.md). With the test harness installed, run:
+[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](docs/RELEASE_CHECKLIST.md) for completed evidence
-and pending release gates, and [the changelog](CHANGELOG.md) for changes.
+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.0/docs/RELEASE_CHECKLIST.md

@@ -1,79 +0,0 @@
-# v0.2 Release Checklist
-
-Repository release-facing scope reference: [V0.2_SPEC.md](V0.2_SPEC.md), derived
-from the project-level frozen engineering baseline maintained outside the
-repository release artifacts.
-
-A checked evidence item applies only to its recorded development build/environment,
-not automatically to a future RC or final artifact. Unverified work stays unchecked.
-
-Current baseline: branch `feature/v0.2-diagnostics`, starting commit
-`f63de41`, package/CLI **0.1.0 (v0.2 development build)**.
-v0.2.0 has not been released.
-
-## Completed development-build evidence
-
-- [x] ED-031 real endpoint/provider live validation: **CLOSED / PASS**.
-  The [compatibility index](COMPATIBILITY.md) links the authoritative matrix
-  and MODEL-0001, MODEL-0002 and MODEL-0003 records.
-- [x] ED-032 Windows clean-install test: **CLOSED / PASS**.
-- [x] Local wheel + sdist build: **PASS**.
-- [x] Windows Basic real endpoint smoke: **PASS**.
-- [x] Windows clean-wheel integration suite: **43 passed**.
-- [x] Windows critical Deep smoke: **PASS**.
-- [x] No secret leak observed in the recorded validation.
-
-The ED-032 outcomes above are carried forward from the supplied ED-033
-acceptance baseline; they are not newly executed ED-033 checks. They do not
-replace or overwrite ED-031 compatibility measurements. Historical
-[0.1.0 validation](releases/0.1.0/VALIDATION.md) remains separate evidence, not
-v0.2 RC acceptance.
-
-## Frozen Scope gates (section 46)
-
-| Gate | Required evidence | Current release disposition |
-|---|---|---|
-| A — Baseline | v0.1 regression tests, editable install, CLI smoke, clean baseline | Historical gate evidence must be included in final release review; no new PASS claimed here |
-| B — Core Architecture | Unified ProbeResult; runner independent of console; reporters do not send HTTP | Implementation described in the spec; final gate acceptance remains to be recorded |
-| C — Functional | Success, unsupported and failure paths for Models, Chat, Streaming, Tools and Structured Output | Test plan covers these paths; complete release validation evidence remains pending |
-| D — Security | Secret Leak Test passes; any complete credential leak blocks release | No leak observed in accepted validation; retain the dedicated release test evidence before final acceptance |
-| E — Real Providers | At least 3 independent providers/endpoints covering 3–5 Chinese models | PASS: closed ED-031 records |
-| F — Package | Build wheel + sdist and clean install | PASS for the development build via ED-032; RC/final artifact acceptance remains pending |
-| G — Release Documentation | README, CHANGELOG, SECURITY and the four release documents | PASS — ED-033 documentation reviewed and accepted |
-
-## Documentation acceptance (ED-033)
-
-- [x] Reconcile the release-facing specification/checklist with the supplied
-  frozen specification and current CLI compatibility behavior.
-- [x] Reviewer acceptance of README, changelog, security guidance, specification,
-  test plan, compatibility index and this checklist (Gate G): PASS.
-
-TESTENV-01: the observed 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).
-No new dev-dependency packaging mechanism is selected in ED-033.
-
-## Remaining formal release gates
-
-- [ ] Complete remaining required release validation under the frozen scope:
-  unit, mock integration, Secret Leak Test and any outstanding platform/Python
-  coverage; retain evidence tied to the release candidate.
-- [ ] Complete macOS and Linux installation, `--version`, `--help`, Basic smoke
-  and mock-suite validation required by section 38.
-- [ ] Verify the minimal CI checks: unit tests, mock integration, wheel/sdist build
-  and package verification; live provider tests stay separately controlled.
-- [ ] Synchronize production version declarations to **0.2.0** in both
-  `pyproject.toml` and `src/apiwells/__init__.py` before formal RC/final artifacts.
-- [ ] Build and identify the formal **RC artifact**; validate metadata and
-  preserve artifact hashes and provenance.
-- [ ] Complete **TestPyPI** publication/installation validation.
-- [ ] Complete **RC clean-install acceptance** against the actual RC artifact.
-- [ ] Review all required release evidence and approve the final release.
-- [ ] Publish the final **PyPI 0.2.0 release**.
-- [ ] Complete **post-release PyPI clean-install smoke**, including the frozen
-  onboarding target of a first Basic check within about five minutes.
-
-VERSION-01: both version declarations remain 0.1.0 in ED-033. Whether to refactor
-to a single version source is undecided. Closed ED-031/ED-032 work is not
-reopened by these future artifact-specific gates. This checklist does not
-authorize publishing.