ap2_mandate_verifier 0.8.0 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: ap2_mandate_verifier
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.8.0
4
+ version: 1.0.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - AP2 Mandate Verifier contributors
8
8
  bindir: bin
9
9
  cert_chain: []
10
- date: 1980-01-02 00:00:00.000000000 Z
10
+ date: 2026-11-01 00:00:00.000000000 Z
11
11
  dependencies:
12
12
  - !ruby/object:Gem::Dependency
13
13
  name: json
@@ -79,10 +79,11 @@ dependencies:
79
79
  - - '='
80
80
  - !ruby/object:Gem::Version
81
81
  version: 3.2.1
82
- description: Stateless verification of the fixed AP2 profile with immutable Evidence
83
- using verify_checkout and the retained verify_research API. Requires trusted Host
84
- inputs and the documented runtime; not Host authorization, payment permission or
85
- general AP2 conformance.
82
+ description: 'Framework-independent Ruby SDK for supported AP2 Checkout profiles:
83
+ Merchant JWT signing, Direct and conditional Mandate issuance and presentation,
84
+ full verification with immutable Evidence, and Checkout Receipt signing and verification.
85
+ Requires independently trusted application inputs; verification does not grant purchase
86
+ or payment permission.'
86
87
  executables: []
87
88
  extensions: []
88
89
  extra_rdoc_files: []
@@ -90,13 +91,17 @@ files:
90
91
  - LICENSE
91
92
  - README.ja.md
92
93
  - README.md
94
+ - SECURITY.md
93
95
  - docs/BUYER_DIRECT_CHECKOUT.md
94
96
  - docs/CONDITIONAL_CHECKOUT.md
95
97
  - docs/DIAGNOSTICS.ja.md
96
98
  - docs/DIAGNOSTICS.md
99
+ - docs/INPUT_BUILDER.md
97
100
  - docs/MERCHANT_SIGNING.md
98
101
  - docs/MULTI_ITEM_CHECKOUT.md
99
- - docs/RELEASE_080_CANDIDATE.md
102
+ - docs/POST_RELEASE_MAINTENANCE.md
103
+ - docs/PUBLIC_API.md
104
+ - docs/RELEASE_100_CANDIDATE.md
100
105
  - docs/SUPPORT_CONTRACT.md
101
106
  - examples/conditional_checkout.rb
102
107
  - lib/ap2_mandate_verifier.rb
@@ -139,5 +144,5 @@ required_rubygems_version: !ruby/object:Gem::Requirement
139
144
  requirements: []
140
145
  rubygems_version: 3.6.9
141
146
  specification_version: 4
142
- summary: Fixed-profile AP2 verification for Ruby
147
+ summary: Ruby SDK for supported AP2 Checkout Mandates
143
148
  test_files: []
@@ -1,109 +0,0 @@
1
- # 0.8.0 candidate — conditional Checkout delegation, unpublished
2
-
3
- Compatible feature release preparation for approved conditional purchasing:
4
- `ConditionalCheckout.issue_open` → Agent `.issue_closed` → `.present` → existing
5
- full `InputBuilder.verify` → `CheckoutReceipt.sign/verify`. The installed
6
- [standalone example](../examples/conditional_checkout.rb) uses A/B×1 and C×2,
7
- three rows and repeated C products. [API/specification](CONDITIONAL_CHECKOUT.md).
8
-
9
- Published stable remains 0.7.0, verified from the official RubyGems versions API
10
- on 2026-11-01; 0.8.0 is absent, so no version-plan collision is currently observed.
11
- 0.7.0 source/tag is `9b4b78a7ed9aa95e7d35e01a64efc1281ba95be3`; its published
12
- 64,000-byte SHA256 is `baab8c68355b5e6c9351e7d86a836fab50652cdad662bbc99d1676c5e6134447`.
13
- Current base main is `50f9639a4fe316556189088ab6b737a642f5f6e2`, initially no open PRs.
14
- No verified prior artifact or previous task checkout was modified.
15
-
16
- ## Validation and compatibility
17
-
18
- All 17 source-suite entry points pass offline on MRI 3.4.12 and 4.0.9. Existing
19
- regression includes Direct, both old profiles, signed missing/unknown/duplicate
20
- disclosures, original-wire binding, InputBuilder save/restore, Result/Evidence,
21
- diagnostics and Receipt outcomes. New tests add 8 cases (123 assertions on MRI
22
- 3.4.12 / 126 on MRI 4.0.9, including installed-Gem execution) for
23
- issuance, sign-before-check prevention, bounds, 8×8 candidate/requirement cases,
24
- same-product separate rows, wrong keys/time/audience/nonce, restoration closure,
25
- and exact final Closed Receipt reference. A long-ID/title eight-row Checkout
26
- also completes through the larger existing Agent-terminal bounds while Merchant
27
- JWT and Direct signing bounds remain unchanged. Suite counts include shared legacy
28
- dependencies; no misleading aggregate of repeated assertion counters is claimed.
29
-
30
- Official pinned Python comparison passes for signatures in both directions,
31
- Open/Closed/Checkout/Receipt Schemas, complete Open commitments and normative
32
- sd_hash including final `~`, both receipt outcomes and negative controls. SDK
33
- high-level Closed helper emits an unsupported SD form; it is a rejection control,
34
- not claimed accepted interoperability. Existing max-flow shortage/empty-candidate
35
- differences and compact-only Receipt helper remain documented and fail closed.
36
-
37
- Candidate Gem identity, corresponding final source SHA, payload hashes, byte size,
38
- ordinary installation on both Rubies and exact example output are recorded in the
39
- external candidate manifest beside the Gem. The Gem includes both READMEs, this
40
- decision document, the API contract and the standalone example. Dependencies and
41
- supported MRI versions are unchanged; old callers require no migration.
42
-
43
- ## Review and external-operation status
44
-
45
- Initial independent Codex review found one substantive P2 (restoration Root
46
- closure); fixed through shared structural parsing and signed negative regression.
47
- GitHub review additionally found that the Merchant signing helper's 12,000-byte
48
- claims / 16,384-byte JWS limits prevented valid larger Agent terminals. KB terminal
49
- signing now uses its existing verifier's 24,576-byte payload / 32,768-byte wire
50
- bounds only; JWT and Direct retain the old limits. Long-ID/title eight-row Ruby
51
- and official Python signature/Schema/hash regressions exercise this fix.
52
- Latest-HEAD independent review must be completed and identified in the external
53
- verification report. Review no-findings alone is not a security proof.
54
-
55
- Initial Draft PR branch push was denied by automatic approval review before
56
- execution. Owner subsequently explicitly authorized the specified commit/branch
57
- push, Draft PR, existing-budget CI, latest-HEAD Codex review/fixes and conditional
58
- Squash Merge at 2026-11-01 14:41 JST. The branch was pushed and
59
- [Draft PR #231](https://github.com/cuichangquan/ap2-mandate-verifier/pull/231)
60
- created. No alternate route bypassed the denial; authorization resolved it first.
61
- No owner approval review is submitted. Current exact-HEAD review, CI and merge
62
- results are recorded in that PR and the external final verification report.
63
- Only existing `merchant-source-package.yml` is expected to trigger for this diff:
64
- two MRI jobs in one workflow run, existing Ubuntu runner/15-minute job timeout,
65
- public dependencies, no secrets, extra cost zero. No workflow edits. Issue #101's
66
- maximum 3 runs/PR is a ceiling, no blind reruns; the PR records every consumed run.
67
-
68
- ## Build and final candidate evidence
69
-
70
- Use the final committed tree, existing pinned Docker images and no network:
71
-
72
- ```sh
73
- gem build ap2_mandate_verifier.gemspec --output /out/ap2_mandate_verifier-0.8.0.gem
74
- sh scripts/check_candidate_package.sh /out/package /out/ap2_mandate_verifier-0.8.0.gem
75
- ```
76
-
77
- Run source regression with `sh scripts/check_ruby_compatibility.sh /out/source`.
78
- The packaging script installs the **same** built Gem with normal RubyGems
79
- resolution (`gem install --local`), audits every source/archive/installed payload,
80
- then executes detached old APIs and the example physically inside the installed
81
- Gem. Reuse one artifact across both MRI runtimes. Do not substitute an earlier
82
- working-tree package or rebuild a lookalike after approval. Exact source SHA and
83
- Gem SHA cannot be embedded recursively in their own bytes; use external manifest.
84
-
85
- ## Publication decision and recovery plan
86
-
87
- 1. Review final source SHA, strict latest-HEAD review, all tests/independent
88
- comparison, exact candidate manifest and remaining GitHub PR/CI gates.
89
- 2. Obtain separate Owner authorization for that exact Gem publication; **no push,
90
- public tag or GitHub Release is authorized by this request**.
91
- 3. After explicit authorization only, RubyGems push the approved exact artifact,
92
- fetch the official distribution and compare bytes/SHA/size and every payload.
93
- 4. Only under publication/tag/Release authorization, bind `v0.8.0` to its verified
94
- source, publish release notes and update stable install guides/demo after the
95
- registry version is actually available. A candidate README is not publication.
96
- 5. On mismatch, invalid dependency/content, signature or material regression,
97
- stop rollout and retain evidence. Do not overwrite a published version; assess
98
- scoped yank/patch publication with separate Owner decision. Keep 0.7.0 install
99
- guidance until the successor is independently verified. Preserve original
100
- saved mandates/challenges; do not reinterpret them under a changed profile.
101
-
102
- Limits: one merchant/Checkout, all candidates disclosed, ES256/P-256, exact finite
103
- profile, no real Issuer trust/production Host proof. Authentication/consent,
104
- revocation/key lifecycle, persistence/CAS/nonce consumption, execution and payment
105
- remain app responsibilities. Payment Mandates, budgets, repeating/split orders,
106
- User Credentials and tax/shipping/discount engines remain out of scope.
107
- Production/real wallet/payment/deployment, RubyGems push and public tag/Release
108
- are NOT_RUN. Release readiness requires the final exact-HEAD PR/review/CI and
109
- package gates; the external report records their actual completion state.