242 operations removed from this spec without a deprecation notice #7370

I scanned this repo’s spec history for operations that disappeared without a deprecated: true marker first, and found 242 of them. Three recent ones, with the commit that removed each:

The practical cost is that a client generated from an older commit keeps calling an endpoint that no longer exists, and the break surfaces in production instead of at build time.

I’m building DriftLock, which detects exactly this kind of drift between a published spec and the code that consumes it. Two things I can do if useful, no strings:

• send the full list for this repo as a CSV, or
• open a PR that adds deprecated: true + x-removal-date before the next removal, so consumers get a compile-time warning

No action needed if these were announced elsewhere and the removals were deliberate — in that case I’d like to know where, so the detector can read that channel too.

(Separately: 40 operations in this repo are currently marked deprecated and still present, oldest 2280 days — that part looks intentional, not a problem.)