[jeremydixon22]

Summary

Marketplace review cannot yet bind the bundled core wheel to its public source commit. Add a pinned recipe that rebuilds the historical source twice, requires the exact shipped wheel digest, and compares every delivered package file, including resources. A separate main-only job signs and verifies the explicit source-to-wheel record with GitHub artifact attestations.

Closes #17. The existing wheel, release tag, client behavior, and plugin commit remain unchanged. This authenticates a new reproduction of the existing release; it does not claim an attestation was recorded during the original build.

Verification

• Local Python 3.12 suite: 220 tests and 23 subtests pass; Python 3.11/3.12 coverage runs in CI.
• Rejection cases cover changed Python/resources, added or missing files, duplicate wheel members, and a mismatched source checkout.
• Public recipe, build record, and verification instructions documented.
• No credentials, receiver source, private catalog data, internal evidence, or generated receipts included.
• Sdist contains the helper, recipe, and guide. Two local builds match the exact existing wheel SHA-256.

Ruff, Bandit, dependency audit, and source quickstart checks also pass locally.

Public information review

Yes: a reproducible build recipe and independently generated build evidence for an already public source tree and release. Publication is intentional to satisfy public runtime review. The workflow emits the public source commit, package hashes, build tools, and public CI identity.

Compatibility and security

No runtime, wire schema, installation, or compatibility changes. Signing permissions are confined to a separate job on main; pull requests can reproduce the wheel but cannot sign evidence. Actions and build tools are pinned. Full-wheel hash mismatch aborts before attestation. The evidence establishes source correspondence, not a security audit.