feat(issuing): add scheduled_revocation_date and status to update-card

[armando-rodriguez-cko]

Summary
Adds scheduled_revocation_date and status to UpdateCardRequest per the 2026-09-17 swagger delta (INT-1700). update-card-response no longer includes encrypted_cvv on the live API (added by INT-1695, removed by this same delta); this SDK has no typed issuing response classes, so no response-side code change is needed.

Changes

• lib/checkout_sdk/issuing/update_card_request.rb — gains scheduled_revocation_date and status, revocation_date documented as deprecated in YARD

API Reference

• PATCH /issuing/cards/{cardId}

Breaking changes
None on this SDK's side (no typed response class carried encrypted_cvv to begin with).

README
No README changes needed.

🤖 Generated with Claude Code

[agent-wall-e]

🟢 Risk Classification: LOW

Approval route: AI Auto-Approval
Rollback controls: Automated Instant Rollback + feature flags

Classification reasons

• no_low_class_matched
• prod_source_modified
• 2.2.6_logical_extension:The change only adds two new optional fields to an existing request class by extending its attr_accessor list, reusing the existing endpoint and abstraction without touching auth, persistence, external integrations, or any other sensitive concerns.

Operational gates

• ✅ jira_ticket (INT-1700)
• ✅ independent_review

Files analysed: 1

---

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.
2.2.6_logical_extension — The change only adds two new optional fields to an existing request class by extending its attr_accessor list, reusing the existing endpoint and abstraction without touching auth, persistence, external integrations, or any other sensitive concerns.	classifying	§2.2.6	Sonnet 4.6 evaluator promoted minor → low: the change reuses existing code paths and does not cross a trust boundary.

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[agent-wall-e]

✅ Auto-approved — this PR meets all Low-risk criteria.

All checks passed, no unresolved comments, and the change classification is:

• no_low_class_matched
• prod_source_modified
• 2.2.6_logical_extension:The change only adds two new optional attributes to an existing request data class, reusing the existing endpoint and abstraction without touching auth, persistence, external integrations, or any other sensitive area.

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}

[agent-wall-e]

🟢 Risk Classification: LOW

Approval route: AI Auto-Approval
Rollback controls: Automated Instant Rollback + feature flags

Classification reasons

• no_low_class_matched
• prod_source_modified
• 2.2.6_logical_extension:The change only adds two new optional attributes to an existing request class and updates YARD documentation/comments, with no new endpoints, auth changes, persisted data, external integrations, or background processes introduced.

Operational gates

• ✅ jira_ticket (INT-1700)
• ✅ independent_review

Files analysed: 3

---

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.
2.2.6_logical_extension — The change only adds two new optional attributes to an existing request class and updates YARD documentation/comments, with no new endpoints, auth changes, persisted data, external integrations, or background processes introduced.	classifying	§2.2.6	Sonnet 4.6 evaluator promoted minor → low: the change reuses existing code paths and does not cross a trust boundary.

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[agent-wall-e]

✅ Auto-approved — this PR meets all Low-risk criteria.

All checks passed, no unresolved comments, and the change classification is:

• no_low_class_matched
• prod_source_modified
• 2.2.6_logical_extension:The change only adds new optional attributes to an existing request class and updates YARD documentation/comments, with no new endpoints, persisted data, auth changes, or external integrations introduced.

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}