chore(main): release 1.0.0

[OgeonX-Ai]

🤖 I have created a release beep boop

1.0.0 (2026-07-13)

Features

• 02-01: consume shared evaluation contract (99d3310)
• 02-02: expand representative benchmark corpus (34d2e04)
• 02-03: publish reproducible benchmark release (a51d1b3)
• add deterministic reference product evaluation (2a89a9a)
• complete Phase 2 shared contracts and corpus (8b98613)
• contracts: verify registry-fetch smoke check + update vendored $id to resolvable Pages URL (#9) (4652531)
• ship reproducible evaluation framework v0.1 (cec9519)

Bug Fixes

• 02-03: preserve cross-platform release bytes (83f91cf)
• cas-evals: preserve transport failure causes; add codeowners and harden workflows (#8) (4fe936c)
• ci: repin release-please reusable workflow to reachable SHA (#14) (cd5486b)
• ci: wire release-please PAT into reusable workflow caller (#18) (46c646c)
• preserve adapter failure diagnostics (#7) (801fe14)

Performance Improvements

• evaluate: optimize reference product evaluation with concurrency (#4) (f4c4912)

---

This PR was generated with Release Please. See documentation.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b57dc2db73

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align the release manifest with package metadata

This records the release state as 1.0.0, but the Python package still builds and reports 0.2.0 in pyproject.toml and src/cas_evals/__init__.py. When the release-please workflow cuts a v1.0.0 GitHub release from this manifest, users installing or building from that tag will get a distribution whose metadata/API version is still 0.2.0, which makes the published release non-reproducible and can confuse any downstream pinning by package version. Please bump the package metadata or configure release-please to manage those version files before releasing.

Useful? React with 👍 / 👎.

[OgeonX-Ai]

🤖 Created releases:

• v1.0.0

🌻