[v1.0] Publish independent adopter case studies and metrics

[codeforester]

Goal

Turn independent adoption into credible evidence for future users.

Scope

• Publish permissioned case studies covering starting point, integration path, operational benefits, and limitations.
• Report metrics such as time to first production command, migration effort, contract failures, diagnostic usefulness, and support requests.
• Include negative findings and accepted residuals.
• Link case studies from the README, PyPI page, and adoption-readiness documentation.

Acceptance criteria

• At least three public or appropriately redacted adopter stories are available.
• Metrics have a documented collection method and timeframe.
• Claims distinguish measured outcomes from qualitative feedback.
• Case studies are kept current across major releases.

Project fields

• Status: Backlog
• Priority: P2
• Area: Product
• Initiative: Adoption Polish
• Size: M

[codeforester]

Review follow-up (2026-09-01): the evidence policy correctly states that there are zero confirmed independent external adopters and that Atlas/Beacon/Cinder are reference fixtures. However, the README calls them "three independent downstream compatibility consumers", and the workflow job is named "Install and test independent consumers". Before publishing adopter evidence under this issue, reserve "independent adopter/consumer" for an external team outcome and rename fixture-facing copy/jobs to "reference consumers" or "independently packaged reference fixtures". This keeps engineering isolation evidence distinct from adoption evidence.

[codeforester]

2026-09-12 repository review refresh

The maintained consumer matrix is engineering evidence, not external adoption. Keep case studies downstream of #248 and record approved before/after outcomes, ongoing usage, exact dependency revisions and permission. There is no verified public adopter outcome in the repository at the reviewed revision.

Validated against current main (7faf347a5b90969e169c88f3ac18e7202d142dd0). This review files and scopes work; it does not claim implementation or authorize release/admin changes.