Conversation
Adds the hand-written half of the Sell limits documentation: a nav entry, a changelog entry, a Sell limits section in the Revenue management use case, and a new Concepts page. The Concepts page covers the three behaviours a generated reference page cannot express: which limit is reported when a rate and its rate group are both capped, which reservation states count as sold, and that a limit is consumed per night of stay rather than on the departure date. It also states that a null limit is different from a configured limit of zero and that available capacity can be negative. The operations/selllimits.md reference page is generated from the demo OAS, so this cannot be merged until the operation is published and reaches demo. Until then the SUMMARY entry points at a page that does not exist. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The negative-availability section credited an override permission that does not exist; no sell-limit bypass privilege is present in the codebase, and ManageSellLimits is a profile privilege for configuring limits rather than exceeding them. Lowering a limit below the sold count is the supportable cause and is now the only one stated. The evaluation-order claim that sell limits are applied after availability and restrictions was not verified against the pricing path, so both pages now describe the limit as a separate constraint without asserting an order. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Follows the contract restructure in the monolith. The concepts page described one record per combination with scalar Limit, Sold and Available; the response is now a time series with the axis factored out once and metric arrays indexed against it, so the page documents that shape, the alignment guarantee, and how to read a single day out of it. The use case note and the changelog entry follow. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Follows the contract review. When the binding cap sits at a level broader than one resource category, every category under it reports the same shared numbers, and the level can differ per day. Summing Available across categories in that case double counts, which is the oversell the operation exists to prevent. The concept page now says so where it explains which level is reported. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Follows the monolith rename to sellLimits/getState. Anchors and link text updated; the generated reference page keeps its filename, only its heading changes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The changelog conflict was two entries prepended at the top; both kept, newest first. The sell limits entry is dated 2026-09-15 for now and should be set to the publication date when this merges. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documentation for the new Connector API operation Get sell limit state (
sellLimits/getState), which returns the effective sell limit, spaces sold and spaces available per rate, resource category and day for a daily service. The operation is merged in the monolith (MewsSystems/mews#88597 and #88008) and is being published under[Restricted].Four hand-written changes:
connector-api/SUMMARY.md: entries for the concept page and the generated operation page.connector-api/changelog/README.md: a new entry, marked as a restricted operation.connector-api/use-cases/revenue-management.md: a Sell limits section after Restrictions, in the same shape.connector-api/concepts/sell-limits.md: new page covering the behaviours a generated reference cannot carry: null limit versus a limit of zero, negative availability, which level is reported when several caps apply and that the broader level wins a tie, that pooled values must not be summed across categories, which reservations count as sold, and per-night consumption.Why this is a draft
connector-api/operations/selllimits.mdis generated by the Regenerate Connector API reference workflow from the demo Swagger, and the operation is not in the demo OAS until the publish PR deploys. Until then the links to that page are dead by construction. Sequence to land this:workflow_dispatch) or wait for the Thursday run; commit the generatedoperations/selllimits.mdonto this branch.#get-sell-limit-statematches the generated heading.Notes for reviewers
Terminology follows CONTRIBUTING.md and the tone-of-voice section of AGENTS.md. Sentences are structured to avoid dashes rather than choose between en and em.
🤖 Generated with Claude Code