Skip to content

docs(payments): document PaymentSetup accommodation/airline fields - #459

Merged
armando-rodriguez-cko merged 1 commit into
masterfrom
feat/INT-1696-payment-setup-accommodation-airline-fields
Sep 17, 2026
Merged

armando-rodriguez-cko merged 1 commit into
masterfrom
feat/INT-1696-payment-setup-accommodation-airline-fields

Conversation

@armando-rodriguez-cko

Copy link
Copy Markdown
Contributor

Summary

Documents the industry.accommodation[]/industry.airline[] shapes and the new fields from the 2026-09-08 spec update in the JSDoc for createAPaymentSetup, updateAPaymentSetup, getAPaymentSetup and confirmAPaymentSetup. This SDK is untyped, so the request body already passes these fields through; only the documentation was missing.

Changes

  • src/api/payment-setups/payment-setups.js — documented total_number_of_guests, refundable, delivery_recipient, host (accommodation) and total_number_of_passengers, travel_type, trip_type, refundable, delivery_recipient, ancillaries, insurance (airline)

API Reference

  • POST /payments/setups
  • PUT /payments/setups/{id}
  • GET /payments/setups/{id}
  • POST /payments/setups/{id}/confirm/{payment_method_name}

Breaking changes

None. Documentation only.

README

No README changes needed.

Documents the industry.accommodation[] and industry.airline[] shapes
in the JSDoc for createAPaymentSetup, updateAPaymentSetup,
getAPaymentSetup and confirmAPaymentSetup, including the new
total_number_of_guests, refundable, delivery_recipient and host
(accommodation) and total_number_of_passengers, travel_type,
trip_type, refundable, delivery_recipient, ancillaries and insurance
(airline) fields. This SDK is untyped, so the body itself already
passes these fields through; only the documentation was missing.
@armando-rodriguez-cko
armando-rodriguez-cko requested a review from a team September 16, 2026 14:41
@agent-wall-e

agent-wall-e Bot commented Sep 16, 2026

Copy link
Copy Markdown

🟢 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 diff is purely JSDoc comment additions with zero runtime code changes, satisfying all conditions for a documentation-only logical extension.

Operational gates

  • ✅ jira_ticket (INT-1696)
  • ✅ independent_review

Files analysed: 1


wall-e 2026.06.19-02 · policy 376219bc71e6…

@agent-wall-e

agent-wall-e Bot commented Sep 16, 2026

Copy link
Copy Markdown
🔬 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 diff is purely JSDoc comment additions with zero runtime code changes, satisfying all conditions for a documentation-only logical extension. 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 agent-wall-e Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ 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 diff contains only JSDoc comment additions with no code logic, endpoint, auth, data persistence, or behavioral changes whatsoever.

wall-e 2026.06.19-02 · policy 376219bc71e6…

@armando-rodriguez-cko
armando-rodriguez-cko merged commit 04ae1e5 into master Sep 17, 2026
1 check passed
@armando-rodriguez-cko
armando-rodriguez-cko deleted the feat/INT-1696-payment-setup-accommodation-airline-fields branch September 17, 2026 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants