test(service): bind public audit and payment boundaries - #9
Conversation
|
@codex review Review exact head |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@codex review Review exact head |
|
Codex Review: Didn't find any major issues. Delightful! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
The public Cloud Run/payment service landed through #6–#8 without service-level regression coverage, and
service.pystarted the HTTP server at import time, preventing direct boundary tests.This repair is deliberately local:
python service.py;main()/__main__so the module is import-safe;service.pyis not a distributed library module;project.licensewith the supported SPDX string form.The first exact-head CI exposed the source/sdist boundary by failing when the sdist replay contained
test_service.pybut not the deployment-onlyservice.py; this head repairs that packaging mismatch rather than expanding the published library surface.No pricing, host policy, audit semantics, Stripe network behavior, or deployment configuration changes.
hmmm: end-to-end Stripe callback and live-host clone behavior remain integration surfaces. The repository has also advanced beyond the already-published
v0.2.0source whilepyproject.tomlstill says0.2.0; do not publish rebuilt artifacts under that existing version without an explicit version/release decision.