chore: migrate `removeInvite/:_id` endpoint to chained API pattern with AJV validation

Closed
NA
7mo ago
+14-13

Closes #39199

Changes

  • Migrated removeInvite/:_id DELETE endpoint from legacy API.v1.addRoute to the new chained .delete() API pattern
  • Added AJV response schema validation for the 200 response
  • Removed manual '/v1/removeInvite/:_id' type definition from rest-typings (now auto-inferred via ExtractRoutesFromAPI)

Files Changed

No behavioral changes

The endpoint logic remains identical — only the registration pattern has been updated.

Related project

This continues the REST API migration effort described in the GSoC 2026 project: Replace old REST API definitions over the new API.

cc @diego-sampaio @ggazzo

Summary by CodeRabbit

  • API Changes

    • The removeInvite endpoint type definition was removed from the public API surface.
  • Internal Improvements

    • Invite endpoint implementation structure and route declaration were reorganized (no change to runtime behavior).