Qualify native subscription grace and exact-payload test fixtures #565

Description

Hosted run 42983035068, head 2f09173, passed 1112 ordinary iOS tests but failed two of the 25 native-commerce cases:

• StoreKitProSubscriptionTests.testBillingGraceMapsVerifiedStatusAndKeepsAccess timed out at its existing 75-second bound. Retained diagnostics show an empty received-status trace, session issue=false, and the SDK/source still reporting subscribed with no retry or grace end after the recorded expiry. This does not establish a production entitlement defect.
• testVerifiedRenewalMetadataMatchesApplePayloadExactly failed its exact signedAt/signedDate equality at line28, though both dates print the same second. The test reads subscription.status separately from source.snapshot(), which reads status again. The intended contract is exact mapping of one verified Apple payload, not equality between independently obtained payloads.

Original logs/artifact are retained on Mini at /home/franz/ios562-0c08ab71-evidence-RzPKpy/run42983035068. These source tests are unchanged from main53e5383. PR563 is blocked and has no hosted qualification at its current head.

Why

A failing native-commerce gate prevents guarded source delivery. Neither green ordinary tests nor weakened expectations would qualify native commerce.

Goal

Establish the actual fixture/lifecycle/oracle seams and apply only demonstrated test/fixture corrections while preserving all 25 cases and exact grace/access and renewal metadata contracts.

Acceptance Criteria

• Preserve every native-commerce case and all intended assertions, account/transaction isolation and synthetic product configuration.
• Exact metadata checks compare the actual production mapping against the same verified Apple payload, with no tolerance or changed expected values.
• Distinguish SDK grace generation, fixture settings, stream delivery and service mapping before claiming a grace fix.
• No deadline increase, skip, retry-for-green, disabled phase, automatic CI expansion or production commerce/auth/release behavior change.

Definition of Done

• Issue-linked reviewable test/fixture correction with meaningful regression and counter-control evidence.
• Exact-head hosted manual validation of the named failures and all 25 native-commerce cases; all other actual gates green before merge.
• Fresh independent exact-head review, preserved original failures and explicit unqualified boundaries where no safe test repair is established.

Validation

Use only the existing hosted manual synthetic runner. Inspect the original native-commerce xcodebuild.log and summary.log. Preserve original grace/access assertions and exact metadata equality. Record exact source, settings, payload identity/timing and all native case outcomes. A production defect requires a source-linked boundary report and smallest proposed correction, not an unauthorized production edit.

API contract: signedDate identifies the signed JWS renewal information; synthetic billing grace requires retry and grace settings. Context7 unavailable; official Apple docs consulted. Duplicate search covered both exact method names and billing-grace/renewal-metadata terms. Closed523 records older qualification, not these two current failures. Release470 and ASC469 remain prohibited and are not this test-only issue.