Skip to content

Spec drift: regenerate models - #35

Merged
cubehouse merged 4 commits into
mainfrom
bot/spec-drift
Oct 30, 2026
Merged

cubehouse merged 4 commits into
mainfrom
bot/spec-drift

Conversation

@tpw-drift

@tpw-drift tpw-drift Bot commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

Automated regeneration from https://api.themeparks.wiki/docs/v1.yaml

  • regenerate: success
  • live smoke tests: success

A regenerate failure means the upstream contract changed in a way
this client cannot absorb automatically. Do not merge until green.

@tpw-drift
tpw-drift Bot force-pushed the bot/spec-drift branch 2 times, most recently from c25aca4 to 74b0134 Compare October 2, 2026 12:49
cubehouse and others added 2 commits October 30, 2026 20:46
The regenerated HistoryDailyRow adds implausibleWaits and
inParkHours.implausibleWaits, each with standby and singleRider counts.
The CSV columns are derived from the schema, so the file now has 45
columns. The new ones sit after extremeWaitsSingleRider and after
inParkHoursExtremeWaitsSingleRider, so the fingerprint changes and any
in-flight resume is refused, which is what the fingerprint is for.

csv_contract.json is the copy shared with the JavaScript SDK and is
byte-identical there (same 45 columns, same fingerprint). The data column
count assertion goes from 36 to 40 and the contract guard from 41 to 45.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@cubehouse
cubehouse merged commit fd79e22 into main Oct 30, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant