diff --git a/docs/api/openapi.yaml b/docs/api/openapi.yaml index 7e5d2455a..b852045d7 100644 --- a/docs/api/openapi.yaml +++ b/docs/api/openapi.yaml @@ -20416,6 +20416,36 @@ paths: application/json: schema: $ref: "#/components/schemas/ErrorEnvelope" + /api/auth/check-user: + post: + security: [] + deprecated: true + tags: + - Retired + summary: POST /api/auth/check-user — removed in v1.38.19 + description: >- + Removed in v1.38.19. Every request to this path answers 410 Gone, whatever the method and whatever credential it + carries. There is no replacement; the capability is gone rather than moved. + + + Took an email address or a username and answered, to any caller and with no credential at all, whether an + account existed here and whether it carried a passkey or a password. It was built to decide which field a + sign-in screen shows first, which is not worth telling the world who has an account. Send the credential to POST + /api/auth/login or run the passkey ceremony and read the answer; both refuse identically whether or not the + account exists. + + + Retiring a path is deliberate, so the answer says so rather than leaving a client to read a 404 as a broken + deployment and retry forever. Treat 410 as terminal: drop the call, degrade the surface that depended on it, and + do not offer a retry. + responses: + "410": + description: The path was removed in v1.38.19 and will not answer again. `meta.errorCode` = `route.retired`, + `meta.removedIn` carries the version, and `meta.replacedBy` carries the replacement path or null. + content: + application/json: + schema: + $ref: "#/components/schemas/ErrorEnvelope" /api/auth/me/research-mode: get: security: [] diff --git a/src/lib/http/retired-routes.ts b/src/lib/http/retired-routes.ts index 0f38cc2a0..11eb825fd 100644 --- a/src/lib/http/retired-routes.ts +++ b/src/lib/http/retired-routes.ts @@ -55,14 +55,17 @@ * client's repository, not in this one, and an inference drawn from this side * would be a guess wearing a citation. Nothing below is a claim about a caller. * - * How the set was found: every route path under `src/app` at every release tag, - * unioned, then differenced against the current tree. Twenty-seven paths have - * been removed across the project's history. The five here are the ones that - * were published or client-facing. The other twenty-two are admin-console - * routes, operator diagnostics, aggregators superseded in place, and the - * moodLog bridge — surfaces reachable only from the operator's own browser, - * which ships with the server and reads no contract to find out what it talks - * to. `moodlog-removal-guard.test.ts` separately holds that bridge removed. + * How the set was seeded: every route path under `src/app` at every release + * tag, unioned, then differenced against the current tree. Twenty-seven paths + * had been removed across the project's history up to that point. Five of them + * were published or client-facing and are the first five entries below; the + * other twenty-two are admin-console routes, operator diagnostics, aggregators + * superseded in place, and the moodLog bridge — surfaces reachable only from + * the operator's own browser, which ships with the server and reads no + * contract to find out what it talks to. `moodlog-removal-guard.test.ts` + * separately holds that bridge removed. Every entry after those five was + * written by the release that removed the path, which is where a tombstone + * belongs. * * Sample tags instead of all of them and this undercounts badly: six evenly * spaced tags find fourteen of the twenty-seven, because a path added and @@ -141,6 +144,14 @@ export const RETIRED_ROUTES: readonly RetiredRoute[] = [ "The whole-record operation moved under the resource type it operates on, which is where FHIR R4 defines it and where the capability statement points.", methods: ["GET"], }, + { + path: "/api/auth/check-user", + removedIn: "1.38.19", + replacedBy: null, + reason: + "Took an email address or a username and answered, to any caller and with no credential at all, whether an account existed here and whether it carried a passkey or a password. It was built to decide which field a sign-in screen shows first, which is not worth telling the world who has an account. Send the credential to POST /api/auth/login or run the passkey ceremony and read the answer; both refuse identically whether or not the account exists.", + methods: ["POST"], + }, { path: "/api/auth/me/research-mode", removedIn: "1.37.2",