OPS-39709: document PrepaidOrVcc billing automation prepayment value

[Mazaher-Bazari]

Summary

OPS-39709: PrepaidOrVcc was added to RoutingRulePrepayment in mews#86308 but left out of the Connector API contract, so a billing automation holding the value made billingAutomations/getAll throw for the whole enterprise. mews#86733 closes that gap and ships with the Tuesday 11 August 2026 release. This PR documents the new value: the changelog entry, and the Billing automation prepayment type enum on the billing automations reference page.

Important

Do not merge before Tuesday 11 August 2026. Until mews#86733 ships, this documents PrepaidOrVcc as an accepted request value that the API still rejects.

Checklist

• Documentation follows the contribution guidelines
• Changelog accurately describes all changes
• All hyperlinks tested
• SUMMARY.md updated if new pages added — n/a, no new pages

API

• Changelog highlights the affected endpoints or operations
• Changelog highlights any deprecations — n/a, additive change only
• Deprecation Table updated if any deprecations — n/a, nothing deprecated

🤖 Generated with Claude Code

[moxly]

✅ Review posted. View review · run

[moxly]

Risk Assessment

Score: 2/10 — low

Documentation-only change to a docs repository — no runtime code, so there is no direct production-incident path. The residual risk is integrator-facing and modest: the docs publish PrepaidOrVcc as an accepted request value before the contract change (mews#86733) has shipped, and the hand-written descriptions live in a generated file that the next regeneration reverts.

Review Summary

Verdict: COMMENT

2 warnings, 2 nits.

The changelog entry matches repository conventions closely: single {% updates format="full" %} wrapper, one {% update %} block, level-2 heading, three operation bullets followed by one shared detail bullet (CONTRIBUTING.md:118-127), and the additive-enum wording mirrors the existing Counter type discriminator entry at line 31. All four anchors resolve (#get-all-billing-automations → line 4, #add-billing-automations → line 221, #update-billing-automations → line 377, #billing-automation-prepayment-type → line 150). No **Breaking:** / **Deprecated** label is needed, so the deprecations table correctly stays untouched. The PR body's three claims — enum value added, the three Prepayment objects annotated, changelog entry added — are all present in the diff.

The PR template is fully filled in, with n/a rationale on the non-applicable checklist items. Both self-flagged reviewer notes are real and are addressed in the inline comments below.

I checked whether the sibling Applicability enum in routingrules.md:118-121 needed the same treatment — its values are Always / PrepaidOnly, a different contract enum, so it is correctly out of scope.

Fix All — prompt for AI agent

Fix the following issues in this PR:

1. In connector-api/operations/billingautomations.md (lines 152-154, plus the property rows at 124, 287, 429): these descriptions are hand-written into a generated file (<!-- AUTOMATICALLY GENERATED, DO NOT MODIFY -->, and _generator reads descriptions straight from the upstream swagger with no local override), so the next regeneration reverts them. Extend the mews#86733 follow-up to cover both the enum [Description] attributes on BillingAutomationPrepayment and the Prepayment property descriptions on BillingAutomation, BillingAutomationAddParameters, and BillingAutomationUpdateParameters — otherwise the property-row sentences vanish entirely and the enum bullets regress to PrepaidOrVcc - PrepaidOrVcc.
2. In connector-api/changelog/README.md (line 4): move the {% update date %} to the mews#86733 release date and hold the merge until that contract change ships. Until then, Add billing automations and Update billing automations document PrepaidOrVcc as an accepted request value that the API will reject.
3. In connector-api/changelog/README.md (line 11): optionally add a detail bullet for the All / Prepaid description clarifications ending Documentation-only, no change to API. per CONTRIBUTING.md:134.
4. In connector-api/operations/billingautomations.md (line 153): expand OTA on first use in the page (online travel agency (OTA)), matching routingrules.md:342 — best done in the upstream mews#86733 wording.

After all changes, run the project's linter/formatter.

[moxly]

✅ Review posted. View review · run

[moxly]

Risk Assessment

Score: 1/10 — low

Documentation-only change in a docs repository, and the one integrator-facing risk from the previous round — publishing PrepaidOrVcc as an accepted request value ahead of the contract change — is now closed by moving the entry to the mews#86733 release date (2026-08-11, a Tuesday, matching the PR's hold note) and keeping the PR in draft until that ships.

Review Summary

Verdict: APPROVE

Re-review scoped to changes since commit 9b8cb57 — no new issues.

4 prior findings resolved — 2 fixed, 2 dismissed; 0 carried forward. The changelog date now sits in the future per CONTRIBUTING.md:141, and the added detail bullet at connector-api/changelog/README.md:12 accurately covers the Prepayment property and All / Prepaid value clarifications, ending with the required Documentation-only, no change to API. per CONTRIBUTING.md:134. I verified the generator trace behind the dismissed regeneration finding: propertyDescription returns firstLine(description) only for enum schemas (_generator/jsonschema.js:101-106, _generator/utils.js:25-27) and the full trimmed description otherwise, so the single-line property-row sentences survive as the author described — the follow-up correctly stays scoped to the BillingAutomationPrepayment [Description] attributes. The OTA-expansion nit is likewise accepted as belonging in the upstream mews#86733 wording.