@fleetless/contracts 5.3.0-next.1 → 6.0.0-next.2

package/artifacts/openapi.json

@@ -69,50 +69,6 @@
     }
   ],
   "paths": {
-    "/api/auth/signup": {
-      "post": {
-        "operationId": "post_api_auth_signup",
-        "summary": "Creates an org and its founding Owner, and answers a developer session.",
-        "tags": [
-          "developer-auth"
-        ],
-        "security": [],
-        "parameters": [],
-        "responses": {
-          "201": {
-            "description": "Success.",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/sign-up-response"
-                }
-              }
-            }
-          },
-          "default": {
-            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `signup_closed`, `validation_error`, `email_taken`.",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/api-error"
-                }
-              }
-            }
-          }
-        },
-        "description": "While the deployment runs in closed beta this answers `403 signup_closed` before it looks at the body — there is nothing for a validation message, or an `email_taken` answer, to be right about when nothing will be created. Email is globally unique, so an address already registered in any org is refused.",
-        "requestBody": {
-          "required": true,
-          "content": {
-            "application/json": {
-              "schema": {
-                "$ref": "#/components/schemas/sign-up-request"
-              }
-            }
-          }
-        }
-      }
-    },
     "/api/auth/refresh": {
       "post": {
         "operationId": "post_api_auth_refresh",
@@ -144,7 +100,7 @@
             }
           }
         },
-        "description": "The whole family is re-checked here, not just the token: an account that has been removed from the org, or whose `token_version` was bumped by a password change, cannot mint a fresh console token and answers `token_revoked`. Refusing that only on the other routes would leave a session that is dead everywhere but here.",
+        "description": "The whole family is re-checked here, not just the token: an account that has been removed from the org, or whose `token_version` was bumped by an owner's two-factor reset, cannot mint a fresh console token and answers `token_revoked`. Refusing that only on the other routes would leave a session that is dead everywhere but here.",
         "requestBody": {
           "required": true,
           "content": {
@@ -277,10 +233,48 @@
         }
       }
     },
-    "/api/auth/password/change": {
+    "/api/auth/two-factor": {
+      "get": {
+        "operationId": "get_api_auth_two_factor",
+        "summary": "Answers the calling developer's passkeys, authenticator, recovery codes left and the org's policy.",
+        "tags": [
+          "developer-auth"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/developer-two-factor"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "What Settings › Profile › Security draws. No key material, secret or code travels here — the passkeys are names and dates, the authenticator is a date, the recovery codes are a count."
+      }
+    },
+    "/api/auth/passkeys/options": {
       "post": {
-        "operationId": "post_api_auth_password_change",
-        "summary": "Verifies the current password, sets a new one and answers a fresh session.",
+        "operationId": "post_api_auth_passkeys_options",
+        "summary": "Answers the WebAuthn creation options for registering a passkey.",
         "tags": [
           "developer-auth"
         ],
@@ -296,13 +290,51 @@
             "content": {
               "application/json": {
                 "schema": {
-                  "$ref": "#/components/schemas/session-tokens"
+                  "$ref": "#/components/schemas/webauthn-options-response"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "Hand `options` to the browser's WebAuthn API as it is. The relying party is `fleetless.dev`, so the passkey works on the auth portal and in the console alike; user verification is required and the credential is discoverable, so it can sign the person in without an address. The passkeys the caller already has are excluded. The challenge is single-use and expires with the ceremony."
+      }
+    },
+    "/api/auth/passkeys": {
+      "post": {
+        "operationId": "post_api_auth_passkeys",
+        "summary": "Registers a passkey from the browser's answer to the creation options.",
+        "tags": [
+          "developer-auth"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [],
+        "responses": {
+          "201": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/create-passkey-response"
                 }
               }
             }
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `validation_error`, `invalid_credentials`.",
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `validation_error`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -312,34 +344,55 @@
             }
           }
         },
-        "description": "Every session of this account ends, including the caller's — the request carries nothing identifying its own refresh family, so there is none to spare. The answer is a working replacement pair, which is what the promise has to mean when nothing distinguishes one session from another.",
+        "description": "A ceremony that does not verify — a wrong challenge, origin or relying party, no user verification — is `400 validation_error` naming `credential`. When this is the account's first second factor, ten recovery codes are issued and answered once; otherwise `recovery_codes` is `null` and the existing ones stay valid. Audited as `developer.two_factor_added` with `details.kind` `passkey`.",
         "requestBody": {
           "required": true,
           "content": {
             "application/json": {
               "schema": {
-                "$ref": "#/components/schemas/password-change-request"
+                "$ref": "#/components/schemas/create-passkey-request"
               }
             }
           }
         }
       }
     },
-    "/api/auth/password/reset": {
-      "post": {
-        "operationId": "post_api_auth_password_reset",
-        "summary": "Mails a password-reset link to the address, and answers the same either way.",
+    "/api/auth/passkeys/{id}": {
+      "patch": {
+        "operationId": "patch_api_auth_passkeys_id",
+        "summary": "Renames one of the caller's passkeys.",
         "tags": [
           "developer-auth"
         ],
-        "security": [],
-        "parameters": [],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [
+          {
+            "name": "id",
+            "in": "path",
+            "required": true,
+            "description": "The passkey's uuid, as listed by `GET /api/auth/two-factor`; another person's passkey answers `404`.",
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
         "responses": {
-          "202": {
-            "description": "Success."
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/developer-passkey"
+                }
+              }
+            }
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`.",
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `validation_error`, `not_found`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -349,34 +402,112 @@
             }
           }
         },
-        "description": "Status, body and timing are identical for a known and an unknown address — any difference is an account-enumeration oracle, which is why the unknown branch still pays a real SMTP round trip to a discard address. An account provisioned through OIDC has no Fleetless password and is mailed nothing. A browser form post gets a `303` to the \"check your mail\" card instead of this `202`.",
         "requestBody": {
           "required": true,
           "content": {
             "application/json": {
               "schema": {
-                "$ref": "#/components/schemas/password-reset-request"
+                "$ref": "#/components/schemas/rename-passkey-request"
               }
             }
           }
         }
+      },
+      "delete": {
+        "operationId": "delete_api_auth_passkeys_id",
+        "summary": "Removes one of the caller's passkeys.",
+        "tags": [
+          "developer-auth"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [
+          {
+            "name": "id",
+            "in": "path",
+            "required": true,
+            "description": "The passkey's uuid, as listed by `GET /api/auth/two-factor`; another person's passkey answers `404`.",
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "204": {
+            "description": "Success."
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `not_found`, `target_state_conflict`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "`409 target_state_conflict` names `two_factor` with rule `required_by_org` when this is the caller's last second factor and the organisation requires one. Removing the last one otherwise also voids the recovery codes. Audited as `developer.two_factor_removed` with `details.kind` `passkey`."
       }
     },
-    "/api/auth/password/reset/confirm": {
+    "/api/auth/totp": {
       "post": {
-        "operationId": "post_api_auth_password_reset_confirm",
-        "summary": "Spends a reset token, sets the new password and ends every session of the account.",
+        "operationId": "post_api_auth_totp",
+        "summary": "Starts an authenticator setup and answers its secret and otpauth URL.",
         "tags": [
           "developer-auth"
         ],
-        "security": [],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/two-factor-setup-response"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "The secret is pending until `POST /api/auth/totp/confirm` accepts a code from it; a second call replaces a pending secret. A developer who already has an authenticator keeps it until the new one is confirmed, which is how `Replace…` works."
+      },
+      "delete": {
+        "operationId": "delete_api_auth_totp",
+        "summary": "Removes the caller's authenticator app.",
+        "tags": [
+          "developer-auth"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
         "parameters": [],
         "responses": {
           "204": {
             "description": "Success."
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `token_spent`.",
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `not_found`, `target_state_conflict`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -386,19 +517,95 @@
             }
           }
         },
-        "description": "Unknown, spent and expired tokens all answer `410 token_spent`. Sessions are revoked under the account's actual kind — a console admin holds developer sessions, an app user holds end-user ones — so an app user's open `/realtime` socket does not outlive the reset. A browser form post gets the rendered \"done\" page instead of this `204`.",
+        "description": "`404 not_found` when there is no authenticator. `409 target_state_conflict` names `two_factor` with rule `required_by_org` when it is the caller's last second factor and the organisation requires one. Audited as `developer.two_factor_removed` with `details.kind` `authenticator`."
+      }
+    },
+    "/api/auth/totp/confirm": {
+      "post": {
+        "operationId": "post_api_auth_totp_confirm",
+        "summary": "Confirms the pending authenticator with a code it shows now.",
+        "tags": [
+          "developer-auth"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/totp-confirm-response"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `rate_limited`, `validation_error`, `invalid_code`, `token_spent`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "A code that does not match the pending secret is `400 invalid_code`; no pending setup is `410 token_spent`. On success the new authenticator replaces any earlier one. Ten recovery codes are answered when it is the account's first second factor, otherwise `null`. Audited as `developer.two_factor_added` with `details.kind` `authenticator`.",
         "requestBody": {
           "required": true,
           "content": {
             "application/json": {
               "schema": {
-                "$ref": "#/components/schemas/password-reset-confirm"
+                "$ref": "#/components/schemas/totp-confirm-request"
               }
             }
           }
         }
       }
     },
+    "/api/auth/recovery-codes": {
+      "post": {
+        "operationId": "post_api_auth_recovery_codes",
+        "summary": "Issues ten new recovery codes and voids the old ones.",
+        "tags": [
+          "developer-auth"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/recovery-codes-response"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `target_state_conflict`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "The codes are shown this once. `409 target_state_conflict` names `two_factor` with rule `off` when the caller has no second factor: recovery codes only stand in for one. Audited as `developer.recovery_codes_generated`."
+      }
+    },
     "/api/waitlist": {
       "post": {
         "operationId": "post_api_waitlist",
@@ -525,17 +732,6 @@
               "maxLength": 40
             }
           },
-          {
-            "name": "target_id",
-            "in": "query",
-            "required": false,
-            "schema": {
-              "description": "Events whose target is this id; for a robot also the events that name it in `details.robot_id` (`action.invoked`, `service.called`, …), so a robot's events include what was started on it.",
-              "type": "string",
-              "minLength": 1,
-              "maxLength": 200
-            }
-          },
           {
             "name": "from_ms",
             "in": "query",
@@ -687,17 +883,6 @@
               "maxLength": 40
             }
           },
-          {
-            "name": "target_id",
-            "in": "query",
-            "required": false,
-            "schema": {
-              "description": "Events whose target is this id; for a robot also the events that name it in `details.robot_id` (`action.invoked`, `service.called`, …), so a robot's events include what was started on it.",
-              "type": "string",
-              "minLength": 1,
-              "maxLength": 200
-            }
-          },
           {
             "name": "from_ms",
             "in": "query",
@@ -1080,7 +1265,7 @@
             }
           }
         },
-        "description": "The body is `{ \"name\": string }` — non-empty, trimmed, at most 60 characters as on `role.name` — and is deliberately not a contract shape: contracts define the `role` this answers with, not this one trivial request. **The answer is a bare `role`, not an envelope**, unlike the listing beside it."
+        "description": "The body is `{ \"name\": string }` — non-empty, trimmed, at most 120 characters — and is deliberately not a contract shape: contracts define the `role` this answers with, not this one trivial request. **The answer is a bare `role`, not an envelope**, unlike the listing beside it."
       },
       "get": {
         "operationId": "get_api_apps_id_roles",
@@ -1307,132 +1492,6 @@
         "description": "Built by the same builder the MCP server's own `robot_describe` uses, so the two cannot drift. It answers what the role *would* be offered and consults nothing about any user's actual MCP entitlement. A robot the role grants nothing on still appears, with an empty `exposures` — dropping it would read as \"not attached\", which is a different fact."
       }
     },
-    "/api/apps/{id}/roles/{roleId}": {
-      "patch": {
-        "operationId": "patch_api_apps_id_roles_roleId",
-        "summary": "Renames a role; its users keep it.",
-        "tags": [
-          "apps"
-        ],
-        "security": [
-          {
-            "developerSession": []
-          }
-        ],
-        "parameters": [
-          {
-            "name": "id",
-            "in": "path",
-            "required": true,
-            "description": "The app's uuid, as returned by `POST /api/apps` or listed by `GET /api/apps`.",
-            "schema": {
-              "type": "string"
-            }
-          },
-          {
-            "name": "roleId",
-            "in": "path",
-            "required": true,
-            "description": "The role's uuid, from `GET /api/apps/:id/roles`; a role of another app answers `404`.",
-            "schema": {
-              "type": "string"
-            }
-          }
-        ],
-        "responses": {
-          "200": {
-            "description": "Success.",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/role"
-                }
-              }
-            }
-          },
-          "default": {
-            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `not_found`, `validation_error`, `role_name_taken`.",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/api-error"
-                }
-              }
-            }
-          }
-        },
-        "description": "Names are unique per app, compared exactly as stored after trimming. Built-in roles can be renamed.",
-        "requestBody": {
-          "required": true,
-          "content": {
-            "application/json": {
-              "schema": {
-                "$ref": "#/components/schemas/role-rename-request"
-              }
-            }
-          }
-        }
-      },
-      "delete": {
-        "operationId": "delete_api_apps_id_roles_roleId",
-        "summary": "Deletes a role, moving its users, pending invitations and default-role status to another role.",
-        "tags": [
-          "apps"
-        ],
-        "security": [
-          {
-            "developerSession": []
-          }
-        ],
-        "parameters": [
-          {
-            "name": "id",
-            "in": "path",
-            "required": true,
-            "description": "The app's uuid, as returned by `POST /api/apps` or listed by `GET /api/apps`.",
-            "schema": {
-              "type": "string"
-            }
-          },
-          {
-            "name": "roleId",
-            "in": "path",
-            "required": true,
-            "description": "The role's uuid, from `GET /api/apps/:id/roles`; a role of another app answers `404`.",
-            "schema": {
-              "type": "string"
-            }
-          },
-          {
-            "name": "move_to",
-            "in": "query",
-            "required": false,
-            "schema": {
-              "description": "Another role of the same app that takes over the deleted role's app users, pending invitations and, when it applies, the app's default. The role itself or a role of another app answers `400 validation_error`.",
-              "type": "string",
-              "format": "uuid",
-              "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
-            }
-          }
-        ],
-        "responses": {
-          "204": {
-            "description": "Success."
-          },
-          "default": {
-            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `not_found`, `validation_error`, `role_in_use`, `last_role`.",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/api-error"
-                }
-              }
-            }
-          }
-        },
-        "description": "Without `move_to`, a role that app users or pending invitations hold, or that is the app's default, answers `409 role_in_use` with `{ users, invitations, is_default }`. With `move_to` — another role of the same app, else `400 validation_error` — one transaction moves `app_users.role_id`, pending invitations and `default_role_id`, then deletes the role and its permissions. The app's only role answers `409 last_role`. Built-in roles can be deleted like any other."
-      }
-    },
     "/api/apps/{id}/server-keys": {
       "post": {
         "operationId": "post_api_apps_id_server_keys",
@@ -1952,7 +2011,57 @@
             }
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `not_found`, `target_state_conflict`.",
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `not_found`, `target_state_conflict`, `method_not_allowed`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "The support door beside `POST /api/client/password/reset`, refused like it with `403 method_not_allowed` while the app has the password method off: the same one-hour token and the same link, triggered by a developer for a user who asked them rather than the form. **No enumeration discipline applies** — the caller is authenticated into the app and can read the user list — so this one answers what actually happened: `{ \"mail\": mailStatus }`, where `not_configured` is a deployment without a mailer and `failed` is the state worth somebody's attention. The link points at the app's `reset_url`, or at the hosted reset page when the app has configured none. `409 target_state_conflict` names `password` with rule `not_set` for an account that has none — an OIDC-only app user, whom a reset link would hand a second, quieter door — and `status` with rule `blocked` for a blocked one, since `POST /api/client/password/reset` mails a blocked account nothing and the two doors may not disagree. Setting the password directly is deliberately not offered; a developer who could would hold their customers' credentials."
+      }
+    },
+    "/api/apps/{id}/users/{userId}/two-factor": {
+      "delete": {
+        "operationId": "delete_api_apps_id_users_userId_two_factor",
+        "summary": "Removes an app user's authenticator and recovery codes and ends every session they hold.",
+        "tags": [
+          "apps"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [
+          {
+            "name": "id",
+            "in": "path",
+            "required": true,
+            "description": "The app's uuid, as returned by `POST /api/apps` or listed by `GET /api/apps`.",
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "userId",
+            "in": "path",
+            "required": true,
+            "description": "The app user's uuid, from `GET /api/apps/:id/users`; a user of another app answers `404`.",
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "204": {
+            "description": "Success."
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `not_found`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -1962,7 +2071,7 @@
             }
           }
         },
-        "description": "The support door beside `POST /api/client/password/reset`: the same one-hour token and the same link, triggered by a developer for a user who asked them rather than the form. **No enumeration discipline applies** — the caller is authenticated into the app and can read the user list — so this one answers what actually happened: `{ \"mail\": mailStatus }`, where `not_configured` is a deployment without a mailer and `failed` is the state worth somebody's attention. `409 target_state_conflict` names `reset_url` when the app has configured none: the token would be minted and the link would point nowhere, so nothing is minted. The same `409` names `password` with rule `not_set` for an account that has none — an OIDC-only app user, whom a reset link would hand a second, quieter door — and `status` with rule `blocked` for a blocked one, since `POST /api/client/password/reset` mails a blocked account nothing and the two doors may not disagree. Setting the password directly is deliberately not offered; a developer who could would hold their customers' credentials."
+        "description": "The support door for a person who lost their authenticator and their recovery codes. The authenticator and every recovery code go, and so does every session of the account — whoever held one may be the reason for the reset. **A user with no second factor answers `204` too**: that is the end state being asked for. When the app requires two-factor, the person sets it up again at their next sign-in, before any session exists. Audited as `app_user.two_factor_reset`."
       }
     },
     "/api/apps/{id}/users/{userId}/mcp-grants": {
@@ -2172,7 +2281,7 @@
             }
           }
         },
-        "description": "**An app user, not a team member.** `POST /api/org/invitations` is the other space and leads to the console; this link leads into the developer's own app. The role is resolved and stored now, so a later change to `default_role_id` does not re-aim a link already sent. An invitation **always bypasses `allowed_domains`**. \n\nThe answer carries `accept_url`, which is `null` when the app has configured no `invite_url` — there is nowhere for the link to point, and Fleetless serves an app user no page of its own. That is a `201` with a null link, not a refusal: the invitation exists and a developer may hand the token over by another route. Asking to **mail** it in that state is `409 target_state_conflict` naming `invite_url`, because a mail carrying a dead link is worse than no mail. The same `409` names `default_role_id` when `role_id` is absent and the app has no default role, or its default no longer resolves: an invitation that names no role has nothing to hand its acceptor, so it is refused here rather than at the acceptance a week later. `409 email_taken` is an address the app already has as a user; `404 not_found` is the app or a `role_id` that is not one of its roles. \n\nCreating shares the reissue route's ceiling of **five invitation mails a minute per app**, answering `429 rate_limited` with `retry_after_ms`: re-creating an invitation for one address replaces it and mails again, so a limit that bound only reissue would be a limit on the wrong door.",
+        "description": "**An app user, not a team member.** `POST /api/org/invitations` is the other space and leads to the console; this link leads into the developer's own app. The role is resolved and stored now, so a later change to `default_role_id` does not re-aim a link already sent. An invitation **always bypasses `allowed_domains`**. \n\nThe answer carries `accept_url`: the app's `invite_url` with the token in it, or the Fleetless-hosted invitation page when the app has configured none — so mailing it is never refused for a missing URL. `409 target_state_conflict` names `default_role_id` when `role_id` is absent and the app has no default role, or its default no longer resolves: an invitation that names no role has nothing to hand its acceptor, so it is refused here rather than at the acceptance a week later. `409 email_taken` is an address the app already has as a user; `404 not_found` is the app or a `role_id` that is not one of its roles. \n\nCreating shares the reissue route's ceiling of **five invitation mails a minute per app**, answering `429 rate_limited` with `retry_after_ms`: re-creating an invitation for one address replaces it and mails again, so a limit that bound only reissue would be a limit on the wrong door.",
         "requestBody": {
           "required": true,
           "content": {
@@ -2569,7 +2678,7 @@
     "/api/apps/{id}/auth-config": {
       "get": {
         "operationId": "get_api_apps_id_auth_config",
-        "summary": "Reads the app's auth settings: self-registration, domains, origins, URLs and the MCP switch.",
+        "summary": "Reads the app's auth settings: sign-in methods, two-factor, registration, pages, the hosted look and the MCP switch.",
         "tags": [
           "apps"
         ],
@@ -2611,7 +2720,7 @@
             }
           }
         },
-        "description": "One row per app, created with the app and never absent — an app that has configured nothing reads back the defaults rather than a `404`. `oidc_callback_url` is in the answer and not in the request: it is minted by the cloud from its own public base URL, is the same for every app and every provider, and is the value a developer registers at their identity provider. It stays read-only on every slice write below for a second reason: a writable callback URL would let a caller point the return leg of an OIDC sign-in, which carries an authorization code, at a host they own. `updated_at` is read-only for a duller one: the server stamps it on every write, and a client-supplied value would be a lie about when the row last changed."
+        "description": "One row per app, created with the app and never absent — an app that has configured nothing reads back the defaults rather than a `404`. `oidc_callback_url` is in the answer and not in the request: it is minted by the cloud from its own public base URL, is the same for every app and every provider, and is the value a developer registers at their identity provider. It stays read-only on every slice write below for a second reason: a writable callback URL would let a caller point the return leg of an OIDC sign-in, which carries an authorization code, at a host they own. `updated_at` is read-only for a duller one: the server stamps it on every write, and a client-supplied value would be a lie about when the row last changed. `hosted_pages` and `hosted_logo_url` are read-only as well: the cloud mints both from the auth portal's base URL and the app's identifier."
       }
     },
     "/api/apps/{id}/auth-config/registration": {
@@ -2659,7 +2768,7 @@
             }
           }
         },
-        "description": "**A replace, not a merge, and `.strict()`**: `self_registration`, `allowed_domains` and `allowed_origins` all arrive or the write is refused, so a client built against an older shape cannot silently clear a setting it does not know about. `oidc_callback_url` and `updated_at` are the server's, refused in this body as in every slice's — see `GET`'s notes for why. \n\n`400 validation_error` is where the two field rules land: an entry in `allowed_domains` must be lowercase, since a capitalised one can never match a lowercased address, and an entry in `allowed_origins` must be a bare scheme-host-port with no path, since a browser sends nothing longer in its `Origin` header. Each refuses at configuration time rather than failing silently later. \n\nThe merge is server-side against the stored row, so this write never disturbs the urls or mcp slice.",
+        "description": "**A replace, not a merge, and `.strict()`**: `self_registration`, `allowed_domains` and `allowed_origins` all arrive or the write is refused, so a client built against an older shape cannot silently clear a setting it does not know about. `oidc_callback_url` and `updated_at` are the server's, refused in this body as in every slice's — see `GET`'s notes for why. \n\n`400 validation_error` is where the two field rules land: an entry in `allowed_domains` must be lowercase, since a capitalised one can never match a lowercased address, and an entry in `allowed_origins` must be a bare scheme-host-port with no path, since a browser sends nothing longer in its `Origin` header. Each refuses at configuration time rather than failing silently later. \n\nThe merge is server-side against the stored row, so this write never disturbs another slice.",
         "requestBody": {
           "required": true,
           "content": {
@@ -2672,10 +2781,68 @@
         }
       }
     },
+    "/api/apps/{id}/auth-config/sign-in": {
+      "put": {
+        "operationId": "put_api_apps_id_auth_config_sign_in",
+        "summary": "Replaces how the app's users sign in and whether they give a second factor.",
+        "tags": [
+          "apps"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [
+          {
+            "name": "id",
+            "in": "path",
+            "required": true,
+            "description": "The app's uuid, as returned by `POST /api/apps` or listed by `GET /api/apps`.",
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/app-auth-config"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `validation_error`, `not_found`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "**A replace, not a merge, and `.strict()`**: `sign_in_methods` and `two_factor` both arrive or the write is refused. Both methods off is `400 validation_error` naming `sign_in_methods.password` — an app needs at least one door besides its identity providers. \n\nTurning a method off refuses its routes with `method_not_allowed` from the next request on; a stored password stays stored. Setting `two_factor` to `required` signs nobody out: each person without an authenticator sets one up at their next sign-in, before any session exists. Audited with both old and new values. The merge is server-side against the stored row, so this write never disturbs another slice.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/put-app-auth-sign-in-request"
+              }
+            }
+          }
+        }
+      }
+    },
     "/api/apps/{id}/auth-config/urls": {
       "put": {
         "operationId": "put_api_apps_id_auth_config_urls",
-        "summary": "Replaces the three pages Fleetless's mails point at.",
+        "summary": "Replaces the app's home page and the four pages Fleetless's mails and MCP sign-in point at.",
         "tags": [
           "apps"
         ],
@@ -2717,7 +2884,7 @@
             }
           }
         },
-        "description": "**A replace, not a merge, and `.strict()`**: `invite_url`, `verify_url` and `reset_url` all arrive or the write is refused, so a client built against an older shape cannot silently clear a setting it does not know about. `oidc_callback_url` and `updated_at` are the server's, refused in this body as in every slice's — see `GET`'s notes for why. \n\n`400 validation_error` is where the field rule lands: a URL template must be https (or `http` on `localhost`) and carry its placeholder exactly once — a second occurrence leaves one literal in a mailed link, refused here rather than failing silently once the mail is sent. \n\nThe merge is server-side against the stored row, so this write never disturbs the registration or mcp slice.",
+        "description": "**A replace, not a merge, and `.strict()`**: `app_url`, `invite_url`, `verify_url`, `reset_url` and `mcp_login_url` all arrive or the write is refused, so a client built against an older shape cannot silently clear a setting it does not know about. `oidc_callback_url` and `updated_at` are the server's, refused in this body as in every slice's — see `GET`'s notes for why. \n\nEach may be `null`, and then the Fleetless-hosted page in `hosted_pages` stands in for it: nothing is refused for a missing URL. `400 validation_error` is where the field rules land: a URL template must be https (or `http` on `localhost`) and carry its placeholder exactly once — a second occurrence leaves one literal in a mailed link, refused here rather than failing silently once the mail is sent — and `app_url` takes the same host rule with no placeholder. `mcp_login_url` moved here from the `mcp` slice, because one screen owns all four pages. \n\nThe merge is server-side against the stored row, so this write never disturbs another slice.",
         "requestBody": {
           "required": true,
           "content": {
@@ -2733,7 +2900,7 @@
     "/api/apps/{id}/auth-config/mcp": {
       "put": {
         "operationId": "put_api_apps_id_auth_config_mcp",
-        "summary": "Replaces the MCP switch and its login URL together.",
+        "summary": "Turns the app's MCP endpoint on or off.",
         "tags": [
           "apps"
         ],
@@ -2775,7 +2942,7 @@
             }
           }
         },
-        "description": "**A replace, not a merge, and `.strict()`**: `mcp_enabled` and `mcp_login_url` both arrive or the write is refused, so a client built against an older shape cannot silently clear a setting it does not know about. `oidc_callback_url` and `updated_at` are the server's, refused in this body as in every slice's — see `GET`'s notes for why. \n\n`mcp_login_url` answers to the same rule as the `urls` slice's three templates — https (or `http` on `localhost`), its placeholder exactly once — refused as `400 validation_error` rather than left to fail mid-OAuth, in a client's browser where no console screen is watching. \n\nThe merge is server-side against the stored row, so this write never disturbs the registration or urls slice.",
+        "description": "**A replace, not a merge, and `.strict()`**: `mcp_enabled` arrives or the write is refused. It used to take `mcp_login_url` as well, because on without a URL refused every sign-in; the hosted MCP sign-in now stands in for an unset URL, and the URL moved to the `urls` slice. A body still carrying it is `400 validation_error`. `oidc_callback_url` and `updated_at` are the server's, refused in this body as in every slice's. The merge is server-side against the stored row, so this write never disturbs another slice.",
         "requestBody": {
           "required": true,
           "content": {
@@ -2788,6 +2955,158 @@
         }
       }
     },
+    "/api/apps/{id}/auth-config/look": {
+      "put": {
+        "operationId": "put_api_apps_id_auth_config_look",
+        "summary": "Replaces the hosted pages' accent colour.",
+        "tags": [
+          "apps"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [
+          {
+            "name": "id",
+            "in": "path",
+            "required": true,
+            "description": "The app's uuid, as returned by `POST /api/apps` or listed by `GET /api/apps`.",
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/app-auth-config"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `validation_error`, `not_found`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "**A replace, and `.strict()`**: `hosted_accent` arrives, `#rrggbb` in lowercase, or `null` for the neutral shell's own accent. The logo is its own write, `PUT /api/apps/:id/auth-config/logo`, because it is an image rather than a field. The merge is server-side against the stored row, so this write never disturbs another slice.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/put-app-auth-look-request"
+              }
+            }
+          }
+        }
+      }
+    },
+    "/api/apps/{id}/auth-config/logo": {
+      "put": {
+        "operationId": "put_api_apps_id_auth_config_logo",
+        "summary": "Stores the logo the hosted pages show above the app's name.",
+        "tags": [
+          "apps"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [
+          {
+            "name": "id",
+            "in": "path",
+            "required": true,
+            "description": "The app's uuid, as returned by `POST /api/apps` or listed by `GET /api/apps`.",
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/app-auth-config"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `validation_error`, `not_found`, `unsupported_media_type`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "The body is the **raw image**, not JSON, so it has no request schema: `Content-Type` is one of `HOSTED_LOGO_TYPES` (`image/png`, `image/svg+xml`) and anything else is `415 unsupported_media_type`. At most `HOSTED_LOGO_MAX_BYTES` (100 KB); a larger body, or one that is not the image its type names, is `400 validation_error`. A new logo replaces the stored one. The hosted pages load it from `hosted_logo_url` as an image only, and the cloud serves an SVG sandboxed, so a script inside one never runs."
+      },
+      "delete": {
+        "operationId": "delete_api_apps_id_auth_config_logo",
+        "summary": "Removes the logo from the hosted pages.",
+        "tags": [
+          "apps"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [
+          {
+            "name": "id",
+            "in": "path",
+            "required": true,
+            "description": "The app's uuid, as returned by `POST /api/apps` or listed by `GET /api/apps`.",
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/app-auth-config"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `invalid_uuid`, `not_found`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "Answers the whole configuration, with `hosted_logo_url` now `null`; the hosted pages show the app's name alone. An app with no logo answers the same: that is the end state being asked for."
+      }
+    },
     "/api/apps/{id}/mail-templates": {
       "get": {
         "operationId": "get_api_apps_id_mail_templates",
@@ -2833,7 +3152,7 @@
             }
           }
         },
-        "description": "Answers `{ \"templates\": [appMailTemplate, …] }` with **only the kinds that have a custom template** — at most three. A kind that does not appear is one using the Fleetless default text, which is an ordinary state and not a missing row. Mails to *Fleetless* users, a team invitation or a console password reset, are not in this list and are deliberately not customisable: they are about this platform, not about the developer's product."
+        "description": "Answers `{ \"templates\": [appMailTemplate, …] }` with **only the kinds that have a custom template** — at most four. A kind that does not appear is one using the Fleetless default text, which is an ordinary state and not a missing row. Mails to *Fleetless* users, a team invitation or a console sign-in code, are not in this list and are deliberately not customisable: they are about this platform, not about the developer's product."
       }
     },
     "/api/apps/{id}/mail-templates/{kind}": {
@@ -2862,7 +3181,7 @@
             "name": "kind",
             "in": "path",
             "required": true,
-            "description": "Which of the three mails this template replaces — a `mailTemplateKind`: `invite`, `verify` or `reset`.",
+            "description": "Which of the four mails this template replaces — a `mailTemplateKind`: `invite`, `verify`, `reset` or `login_code`.",
             "schema": {
               "type": "string"
             }
@@ -2917,7 +3236,7 @@
             "name": "kind",
             "in": "path",
             "required": true,
-            "description": "Which of the three mails this template replaces — a `mailTemplateKind`: `invite`, `verify` or `reset`.",
+            "description": "Which of the four mails this template replaces — a `mailTemplateKind`: `invite`, `verify`, `reset` or `login_code`.",
             "schema": {
               "type": "string"
             }
@@ -2982,7 +3301,7 @@
             "name": "kind",
             "in": "path",
             "required": true,
-            "description": "Which of the three mails this template replaces — a `mailTemplateKind`: `invite`, `verify` or `reset`.",
+            "description": "Which of the four mails this template replaces — a `mailTemplateKind`: `invite`, `verify`, `reset` or `login_code`.",
             "schema": {
               "type": "string"
             }
@@ -3032,7 +3351,7 @@
             "name": "kind",
             "in": "path",
             "required": true,
-            "description": "Which of the three mails this template replaces — a `mailTemplateKind`: `invite`, `verify` or `reset`.",
+            "description": "Which of the four mails this template replaces — a `mailTemplateKind`: `invite`, `verify`, `reset` or `login_code`.",
             "schema": {
               "type": "string"
             }
@@ -3099,7 +3418,7 @@
             "name": "kind",
             "in": "path",
             "required": true,
-            "description": "Which of the three mails this template replaces — a `mailTemplateKind`: `invite`, `verify` or `reset`.",
+            "description": "Which of the four mails this template replaces — a `mailTemplateKind`: `invite`, `verify`, `reset` or `login_code`.",
             "schema": {
               "type": "string"
             }
@@ -3496,7 +3815,7 @@
     "/api/org/invitations/accept": {
       "post": {
         "operationId": "post_api_org_invitations_accept",
-        "summary": "Spends an invitation token and creates the login it was addressed to.",
+        "summary": "Spends an invitation token and creates the account it was addressed to.",
         "tags": [
           "users"
         ],
@@ -3517,7 +3836,7 @@
             }
           }
         },
-        "description": "**`204`, not a session.** The console signs in through its own OAuth portal, so a session minted here would be a second credential door for one account — and every security property would then have to be right in two places. Unknown, expired and already-accepted tokens collapse into `410 token_spent`. A browser form post gets the rendered \"you're in\" page instead.",
+        "description": "**`204`, not a session.** The console signs in through its own OAuth portal, so a session minted here would be a second credential door for one account — and every security property would then have to be right in two places. **No password**: the mailed link proves the address, so accepting needs no code either, and the new member signs in by emailed code from then on. When the organisation requires two-factor, the member sets one up at their first sign-in. Unknown, expired and already-accepted tokens collapse into `410 token_spent`. A browser form post gets the rendered \"you're in\" page instead.",
         "requestBody": {
           "required": true,
           "content": {
@@ -3554,18 +3873,69 @@
           }
         ],
         "responses": {
-          "200": {
-            "description": "Success.",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/fleetless-user"
-                }
-              }
-            }
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/fleetless-user"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `tier_required`, `invalid_uuid`, `not_found`, `validation_error`, `last_owner`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "Owner tier, unconditionally — this is the route the whole owner-exclusive list is about. A uuid that is not a Fleetless user of this org answers `404 not_found`, the same as one that does not exist anywhere: the `409 target_state_conflict` documented here until the two-space cut had exactly one producer, the Org Admins membership check, and went with it. Demoting the last Owner is `409 last_owner`, decided by a row lock inside the writing transaction rather than by a read beforehand. Setting the tier already held changes nothing and writes no audit event. No session is revoked: a tier is re-read from the row on every request, so no issued token carries a stale copy of it.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/tier-change-request"
+              }
+            }
+          }
+        }
+      }
+    },
+    "/api/org/users/{id}/two-factor": {
+      "delete": {
+        "operationId": "delete_api_org_users_id_two_factor",
+        "summary": "Removes a team member's passkeys, authenticator and recovery codes and ends their sessions.",
+        "tags": [
+          "users"
+        ],
+        "security": [
+          {
+            "developerSession": []
+          }
+        ],
+        "parameters": [
+          {
+            "name": "id",
+            "in": "path",
+            "required": true,
+            "description": "The Fleetless user's uuid, as listed by `GET /api/org/users`.",
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "204": {
+            "description": "Success."
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `tier_required`, `invalid_uuid`, `not_found`, `validation_error`, `last_owner`.",
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `tier_required`, `invalid_uuid`, `not_found`, `target_state_conflict`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -3575,23 +3945,13 @@
             }
           }
         },
-        "description": "Owner tier, unconditionally — this is the route the whole owner-exclusive list is about. A uuid that is not a Fleetless user of this org answers `404 not_found`, the same as one that does not exist anywhere: the `409 target_state_conflict` documented here until the two-space cut had exactly one producer, the Org Admins membership check, and went with it. Demoting the last Owner is `409 last_owner`, decided by a row lock inside the writing transaction rather than by a read beforehand. Setting the tier already held changes nothing and writes no audit event. No session is revoked: a tier is re-read from the row on every request, so no issued token carries a stale copy of it.",
-        "requestBody": {
-          "required": true,
-          "content": {
-            "application/json": {
-              "schema": {
-                "$ref": "#/components/schemas/tier-change-request"
-              }
-            }
-          }
-        }
+        "description": "Owner tier: the door for a member who lost every second factor and every recovery code. Every session of the member ends, and when the organisation requires two-factor they set one up again at their next sign-in. **An owner cannot reset their own** — `409 target_state_conflict` naming `user_id` with rule `self`; Settings › Profile is where they change it. A member with no second factor answers `204` too. Audited as `developer.two_factor_reset`, naming the owner who did it."
       }
     },
     "/api/org": {
       "patch": {
         "operationId": "patch_api_org",
-        "summary": "Renames the org.",
+        "summary": "Renames the org, requires two-factor for its members, or both.",
         "tags": [
           "org"
         ],
@@ -3623,7 +3983,7 @@
             }
           }
         },
-        "description": "Answers `{ \"org\": org }`. Owner tier, and the gate runs before the body is looked at, so a malformed rename and a forbidden one answer the same way. Renaming to the name already held writes nothing and records no audit event.",
+        "description": "Answers `{ \"org\": org }`. Owner tier, and the gate runs before the body is looked at, so a malformed patch and a forbidden one answer the same way — `403 tier_required` for a developer, whichever field they sent. An empty body is `400 validation_error`. Writing the values already held writes nothing and records no audit event. \n\n`require_two_factor` on signs nobody out: each member without a passkey or authenticator sets one up at their next sign-in, before any session exists, on the console and the central MCP endpoint alike. Server keys and robot bridges are not people and are not affected. Audited as `org.two_factor_required_changed`.",
         "requestBody": {
           "required": true,
           "content": {
@@ -3841,7 +4201,7 @@
             }
           }
         },
-        "description": "**The query schema is what this endpoint accepts, not what it parses**: the handler reads it parameter by parameter because the answers differ, and one parse would collapse them. Client and `redirect_uri` are validated first and a failure there never redirects, the same open-redirect discipline the app flow applies; those refusals are `oauthError`. Exact `redirect_uri` matching for both client kinds — the loopback-port wildcard of RFC 8252 §7.3 belongs to the one central client alone, whose URIs are configured ahead of time and cannot name an ephemeral port. A client that registered itself seconds ago can name the port it bound, and widening the wildcard there would only widen where a stolen `client_id` may send a browser. Nothing about the person is decided here — the next card asks for an email address and the password step after it resolves the account; this route knows only the client."
+        "description": "**The query schema is what this endpoint accepts, not what it parses**: the handler reads it parameter by parameter because the answers differ, and one parse would collapse them. Client and `redirect_uri` are validated first and a failure there never redirects, the same open-redirect discipline the app flow applies; those refusals are `oauthError`. Exact `redirect_uri` matching for both client kinds — the loopback-port wildcard of RFC 8252 §7.3 belongs to the one central client alone, whose URIs are configured ahead of time and cannot name an ephemeral port. A client that registered itself seconds ago can name the port it bound, and widening the wildcard there would only widen where a stolen `client_id` may send a browser. Nothing about the person is decided here — the next card asks for an email address, or a passkey, and the steps after it resolve the account; this route knows only the client."
       }
     },
     "/mcp/oauth/token": {
@@ -4123,7 +4483,7 @@
             }
           }
         },
-        "description": "RFC 8414, for the issuer `<PUBLIC_API_BASE_URL>/mcp/<identifier>` — the same path rule as the document above, and the same `404` for a switched-off app. `registration_endpoint` is present for the reason the central document states: a client that finds it registers itself and never asks a person for a `client_id`. \n\n**`issuer`, `token_endpoint` and the resource identifier are minted from the canonical public base, never from the friendly `mcp.fleetless.dev` alias or the request's `Host`**, because a client checks a minted token's `iss` and `aud` against these exact strings. \n\n**Unlike the central document, `authorization_endpoint` does not move to an auth-portal origin**, and there is nothing here for one to serve: this authorization step renders no Fleetless page at all. It redirects to the app's own `mcp_login_url`, which is on the developer's origin already."
+        "description": "RFC 8414, for the issuer `<PUBLIC_API_BASE_URL>/mcp/<identifier>` — the same path rule as the document above, and the same `404` for a switched-off app. `registration_endpoint` is present for the reason the central document states: a client that finds it registers itself and never asks a person for a `client_id`. \n\n**`issuer`, `token_endpoint` and the resource identifier are minted from the canonical public base, never from the friendly `mcp.fleetless.dev` alias or the request's `Host`**, because a client checks a minted token's `iss` and `aud` against these exact strings. \n\n**Unlike the central document, `authorization_endpoint` does not move to an auth-portal origin**: the authorization step renders no page itself. It redirects to the app's own `mcp_login_url`, or to the hosted MCP sign-in on the auth portal when the app has configured none."
       }
     },
     "/mcp/{appIdentifier}/oauth/register": {
@@ -4183,7 +4543,7 @@
     "/mcp/{appIdentifier}/oauth/authorize": {
       "get": {
         "operationId": "get_mcp_appIdentifier_oauth_authorize",
-        "summary": "Starts an MCP sign-in and redirects the browser to the app's own login page.",
+        "summary": "Starts an MCP sign-in and redirects the browser to the app's own login page, or to the hosted one.",
         "tags": [
           "mcp"
         ],
@@ -4272,7 +4632,7 @@
             "description": "Success."
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `not_found`, `target_state_conflict`.",
+            "description": "An error envelope. Codes this route is known to answer: `not_found`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -4282,7 +4642,7 @@
             }
           }
         },
-        "description": "The same query as `GET /mcp/oauth/authorize`, read the same way — parameter by parameter, because the answers differ and one parse would collapse them. \n\n**Fleetless renders no page here**, and that is the whole of it. The route writes an interaction — ten minutes, as the OIDC ones live — and redirects to `appAuthConfig.mcp_login_url` with `{interaction}` filled in. The app then authenticates the person with its own UI, reads `GET /api/client/mcp/interactions/:id` to show the client's claimed name and the scopes it asked for, and calls approve or deny. \n\nClient and `redirect_uri` are validated first and a failure there never redirects — the open-redirect discipline `GET /mcp/oauth/authorize` and `GET /api/client/oidc/:slug/start` both keep — and those refusals are RFC 6749's flat `oauthError`, which is why none of them appear above. `redirect_uri` is matched **exactly** against the registration, with no loopback-port wildcard: every client here registered itself minutes ago and can name the port it bound, so a wildcard would only widen where a stolen `client_id` may send a browser. \n\nThe two codes above are the `apiError` envelope because they are refusals about the **app**, decided before an OAuth parameter is looked at. **`404 not_found` covers an identifier no app carries AND an app with MCP switched off** — the same single answer the two metadata documents, `register` and the transport give. An earlier draft answered `403 mcp_disabled` here, on the argument that a client which registered while the switch was on is owed the difference between \"turned off\" and \"mistyped\"; that argument does not survive the caller being anonymous. This route takes no credential, so the extra code was readable by anyone who could type an identifier, and it handed back precisely the existence distinction every neighbouring route collapses. `mcp_disabled` survives only where the caller has already proved they belong to the app — the two decision routes under `/api/client/mcp/interactions/:id`. `409 target_state_conflict` names `mcp_login_url` with rule `not_set`: MCP is enabled and no page is configured to send the person to. It is the same code and the same shape `send_mail` answers for an unconfigured `invite_url`, and the refusal is the honest one — Fleetless has nowhere to redirect, and rendering a page of its own would contradict the rule that Fleetless shows an app user no page."
+        "description": "The same query as `GET /mcp/oauth/authorize`, read the same way — parameter by parameter, because the answers differ and one parse would collapse them. \n\n**This route renders no page.** It writes an interaction — ten minutes, as the OIDC ones live — and redirects to `appAuthConfig.mcp_login_url` with `{interaction}` filled in. The app then authenticates the person with its own UI, reads `GET /api/client/mcp/interactions/:id` to show the client's claimed name and the scopes it asked for, and calls approve or deny. **An app with no `mcp_login_url` is redirected to the hosted MCP sign-in** (`GET /app/:appIdentifier/mcp/:interaction`), which runs the same steps on the auth portal; nothing is refused for a missing URL. \n\nClient and `redirect_uri` are validated first and a failure there never redirects — the open-redirect discipline `GET /mcp/oauth/authorize` and `GET /api/client/oidc/:slug/start` both keep — and those refusals are RFC 6749's flat `oauthError`, which is why none of them appear above. `redirect_uri` is matched **exactly** against the registration, with no loopback-port wildcard: every client here registered itself minutes ago and can name the port it bound, so a wildcard would only widen where a stolen `client_id` may send a browser. \n\nThe code above is the `apiError` envelope because it is a refusal about the **app**, decided before an OAuth parameter is looked at. **`404 not_found` covers an identifier no app carries AND an app with MCP switched off** — the same single answer the two metadata documents, `register` and the transport give. An earlier draft answered `403 mcp_disabled` here, on the argument that a client which registered while the switch was on is owed the difference between \"turned off\" and \"mistyped\"; that argument does not survive the caller being anonymous. This route takes no credential, so the extra code was readable by anyone who could type an identifier, and it handed back precisely the existence distinction every neighbouring route collapses. `mcp_disabled` survives only where the caller has already proved they belong to the app — the two decision routes under `/api/client/mcp/interactions/:id`."
       }
     },
     "/mcp/{appIdentifier}/oauth/token": {
@@ -4354,13 +4714,13 @@
             "content": {
               "application/json": {
                 "schema": {
-                  "$ref": "#/components/schemas/session-tokens"
+                  "$ref": "#/components/schemas/client-sign-in-result"
                 }
               }
             }
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `invalid_credentials`.",
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `invalid_credentials`, `method_not_allowed`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -4370,7 +4730,7 @@
             }
           }
         },
-        "description": "One refusal for every miss — unknown app, unknown address, wrong password, a `blocked` account and one still `pending_verification` — because the caller supplies the `app_identifier` unauthenticated, so \"this app knows this user\" is not a fact the answer may carry. The argon2 verify is paid unconditionally, including for an unknown app identifier, so response time is not an oracle either.",
+        "description": "One refusal for every miss — unknown app, unknown address, wrong password, a `blocked` account and one still `pending_verification` — because the caller supplies the `app_identifier` unauthenticated, so \"this app knows this user\" is not a fact the answer may carry. The argon2 verify is paid unconditionally, including for an unknown app identifier, so response time is not an oracle either. \n\n**The answer is a `clientSignInResult`**: session tokens, or a `twoFactorChallenge` when the person has a confirmed authenticator or the app requires one — then no session exists until `POST /api/client/two-factor/verify` or the setup is done. `403 method_not_allowed` when the app has the password method off; it names the app's policy, not a person.",
         "requestBody": {
           "required": true,
           "content": {
@@ -4383,6 +4743,87 @@
         }
       }
     },
+    "/api/client/login/code": {
+      "post": {
+        "operationId": "post_api_client_login_code",
+        "summary": "Mails a six-digit sign-in code, and answers the same whether or not the address exists.",
+        "tags": [
+          "client-auth"
+        ],
+        "security": [],
+        "parameters": [],
+        "responses": {
+          "202": {
+            "description": "Success."
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `not_found`, `method_not_allowed`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "**`202` and an empty body for every request the policy allows**, in status, body and timing, whether or not the address names an active account of this app — a decoy like `POST /api/client/resend-verification`, so this is no enumeration oracle. A mail goes out for an `active` account and for one still `pending_verification` — spending the code proves the address, as the verification link would — and never for a `blocked` one or an unknown address. The code is six digits, valid ten minutes, takes five wrong attempts, and a new request expires the previous one for the same address; a request within sixty seconds of the last sends no second mail. The address is trimmed and compared case-insensitively. `404 not_found` is the **app identifier**, never the address; `403 method_not_allowed` when the app has the email-code method off. Limited per app, address and IP, so it cannot be used to mail somebody repeatedly.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/client-login-code-request"
+              }
+            }
+          }
+        }
+      }
+    },
+    "/api/client/login/code/verify": {
+      "post": {
+        "operationId": "post_api_client_login_code_verify",
+        "summary": "Spends a mailed sign-in code and answers a session or a two-factor challenge.",
+        "tags": [
+          "client-auth"
+        ],
+        "security": [],
+        "parameters": [],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/client-sign-in-result"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `invalid_code`, `token_spent`, `method_not_allowed`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "A wrong code is `400 invalid_code` with `details.attempts_left` (`invalidCodeDetails`). A code that is spent, past its ten minutes, out of attempts, or was never mailed is `410 token_spent` — one answer, because telling them apart would say whether a code was ever sent to that address; the recovery is the same, ask for a new code. The address is trimmed and compared case-insensitively, so the address typed at the request and here need not match in case. \n\n**The answer is a `clientSignInResult`**, like the password login: tokens, or a `twoFactorChallenge` when the person has an authenticator or the app requires one. A pending-verification account that spends a code is activated — reading a mail at that address is the proof verification asks for.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/client-login-code-verify-request"
+              }
+            }
+          }
+        }
+      }
+    },
     "/api/client/register": {
       "post": {
         "operationId": "post_api_client_register",
@@ -4407,7 +4848,7 @@
             }
           }
         },
-        "description": "**`202` and an empty body for every request policy allows** — a new address, one this app already knows and one it does not answer identically, in status, body and timing. An answer that depended on existence would be the account-enumeration oracle the whole client family is built to avoid. The account cannot log in until the mailed link is spent; `POST /api/client/verify-email` is what does that. \n\n**An address on an account still `pending_verification` is re-registered, not ignored.** The password and display name from this call replace what is stored, every outstanding verification link for the address stops working, and a fresh one is mailed. Otherwise whoever typed an address first would own the password of the account its real owner later verifies. An address on an `active` account changes nothing and sends nothing — that account has already been proven, and its way back in is `POST /api/client/password/reset`. Neither case is visible in the answer. \n\nThe refusals it *does* make are about policy or about what the caller typed, never about a person. `403 registration_closed` when the app has self-registration off and `403 domain_not_allowed` when the address is outside `allowed_domains`: both are the developer's own configuration, and a stranger learns the app's policy rather than who is in it. **A password under twelve characters is part of that `400 validation_error`** and not a code of its own — the minimum is the `password` field's schema rule, and the error names the field, which is what a form needs to mark it. `404 not_found` names an **app identifier no app carries**, and never an address: an app identifier is already public (it is in the MCP metadata path and in the developer's own URLs), while collapsing it into `registration_closed` sent a developer who mistyped their own identifier hunting a configuration bug that was not there. `409 target_state_conflict` when the app has configured no `verify_url` or has no default role — there would be nowhere to send the person and no role to give them, and mailing a link that leads nowhere is worse than refusing. \n\n**`409 quota_exceeded` when the org is at its `max_end_users` limit**, counted across every app of the org. It is the one refusal here that is answered **before the address is looked at** — and that ordering is the point rather than an implementation detail: a quota checked after the existence branch would answer `202` for an address the app already knows and `409` for one it does not, which is precisely the enumeration oracle every other line of this route exists to close. At the quota, every registration is refused identically, including one that would only have re-mailed a pending account's link.",
+        "description": "**`202` and an empty body for every request policy allows** — a new address, one this app already knows and one it does not answer identically, in status, body and timing. An answer that depended on existence would be the account-enumeration oracle the whole client family is built to avoid. The account cannot log in until the mailed link is spent; `POST /api/client/verify-email` is what does that. \n\n**An address on an account still `pending_verification` is re-registered, not ignored.** The password and display name from this call replace what is stored, every outstanding verification link for the address stops working, and a fresh one is mailed. Otherwise whoever typed an address first would own the password of the account its real owner later verifies. An address on an `active` account changes nothing and sends nothing — that account has already been proven, and its way back in is `POST /api/client/password/reset`. Neither case is visible in the answer. \n\nThe refusals it *does* make are about policy or about what the caller typed, never about a person. `403 registration_closed` when the app has self-registration off and `403 domain_not_allowed` when the address is outside `allowed_domains`: both are the developer's own configuration, and a stranger learns the app's policy rather than who is in it. **A password under twelve characters is part of that `400 validation_error`** and not a code of its own — the minimum is the `password` field's schema rule, and the error names the field, which is what a form needs to mark it. The same `400` names `password` when one is missing while the app's password method is on, or sent while it is off: an email-code-only app registers people without one. `404 not_found` names an **app identifier no app carries**, and never an address: an app identifier is already public (it is in the MCP metadata path and in the developer's own URLs), while collapsing it into `registration_closed` sent a developer who mistyped their own identifier hunting a configuration bug that was not there. `409 target_state_conflict` when the app has no default role — there would be no role to give the person. An app with no `verify_url` is not refused: the mailed link points at the hosted confirmation page instead. \n\n**`409 quota_exceeded` when the org is at its `max_end_users` limit**, counted across every app of the org. It is the one refusal here that is answered **before the address is looked at** — and that ordering is the point rather than an implementation detail: a quota checked after the existence branch would answer `202` for an address the app already knows and `409` for one it does not, which is precisely the enumeration oracle every other line of this route exists to close. At the quota, every registration is refused identically, including one that would only have re-mailed a pending account's link.",
         "requestBody": {
           "required": true,
           "content": {
@@ -4435,7 +4876,7 @@
             "content": {
               "application/json": {
                 "schema": {
-                  "$ref": "#/components/schemas/session-tokens"
+                  "$ref": "#/components/schemas/client-sign-in-result"
                 }
               }
             }
@@ -4451,7 +4892,7 @@
             }
           }
         },
-        "description": "**The answer is a session, not a `204`.** Somebody who has just proved they can read the mail should not be asked to type their password again on the next screen, and the app has an access token to carry them into it. The token is spent first and the account is activated second, as **two writes**: the spend is the atomic one, so a link opened twice cannot mint two sessions, but a process that died between them would leave a spent token on an account still `pending_verification`, whose recovery is `POST /api/client/resend-verification`. Spending the token also proves the address, so a later `PATCH` may return the account to `active` after a block. \n\n**One refusal for every token that does not work: `410 token_spent`** — unknown, past its twenty-four hours, or already used. There is one code because distinguishing them would tell a stranger whether a token ever existed, and because the recovery is the same in all three cases: ask for a fresh link with `POST /api/client/resend-verification`. An app rendering this refusal should offer that and nothing conditional on which of the three it was.",
+        "description": "**The answer is a session, not a `204`** — or, as on every sign-in step, a `twoFactorChallenge` when the app requires two-factor (`clientSignInResult`). Somebody who has just proved they can read the mail should not be asked to type their password again on the next screen, and the app has an access token to carry them into it. The token is spent first and the account is activated second, as **two writes**: the spend is the atomic one, so a link opened twice cannot mint two sessions, but a process that died between them would leave a spent token on an account still `pending_verification`, whose recovery is `POST /api/client/resend-verification`. Spending the token also proves the address, so a later `PATCH` may return the account to `active` after a block. \n\n**One refusal for every token that does not work: `410 token_spent`** — unknown, past its twenty-four hours, or already used. There is one code because distinguishing them would tell a stranger whether a token ever existed, and because the recovery is the same in all three cases: ask for a fresh link with `POST /api/client/resend-verification`. An app rendering this refusal should offer that and nothing conditional on which of the three it was.",
         "requestBody": {
           "required": true,
           "content": {
@@ -4494,28 +4935,197 @@
           "content": {
             "application/json": {
               "schema": {
-                "$ref": "#/components/schemas/client-resend-verification-request"
+                "$ref": "#/components/schemas/client-resend-verification-request"
+              }
+            }
+          }
+        }
+      }
+    },
+    "/api/client/password/reset": {
+      "post": {
+        "operationId": "post_api_client_password_reset",
+        "summary": "Mails an app user a reset link, and answers the same either way.",
+        "tags": [
+          "client-auth"
+        ],
+        "security": [],
+        "parameters": [],
+        "responses": {
+          "202": {
+            "description": "Success."
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `not_found`, `method_not_allowed`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "The pair of app identifier and address is the identifier: an app user's address is unique only within their app. `403 method_not_allowed` when the app has the password method off — a reset link whose confirmation would be refused is not mailed; the code names the app's policy, not a person. Status, body and timing are identical for a known and an unknown address. An account with no password — one created through an identity provider — is mailed nothing and still answers `202`. `404 not_found` is the **app identifier**, never the address. The link points at the app's `reset_url`, or at the hosted reset page when the app has configured none.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/client-password-reset-request"
+              }
+            }
+          }
+        }
+      }
+    },
+    "/api/client/password/reset/confirm": {
+      "post": {
+        "operationId": "post_api_client_password_reset_confirm",
+        "summary": "Spends a reset token, sets the new password and answers a fresh session.",
+        "tags": [
+          "client-auth"
+        ],
+        "security": [],
+        "parameters": [],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/client-sign-in-result"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `token_spent`, `method_not_allowed`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "**A new password does not bypass the second factor**: a person with an authenticator, or in an app that requires one, gets a `twoFactorChallenge` instead of tokens (`clientSignInResult`), and the authenticator stays on. `403 method_not_allowed` when the app has the password method off. \n\n**Every refresh family of that account is revoked**, then a fresh pair is minted for the caller — a forgotten password is one of the two states where somebody else may be holding a live session, and the person completing the reset is the one who should keep theirs. The account is activated if it was still `pending_verification`: reading a mail at that address is the same proof verification asks for. \n\n**One refusal for every token that does not work: `410 token_spent`** — unknown, past its hour, or already used. There is one code because distinguishing them would tell a stranger whether a token ever existed, and the recovery is identical either way: ask for a new link. A replacement password under twelve characters is a `400 validation_error` naming the `new_password` field — the twelve-character minimum is that field's schema rule, and it is refused the way any other malformed field is.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/client-password-reset-confirm-request"
+              }
+            }
+          }
+        }
+      }
+    },
+    "/api/client/invitations/accept": {
+      "post": {
+        "operationId": "post_api_client_invitations_accept",
+        "summary": "Spends an invitation token, creates or activates the app user and answers a session.",
+        "tags": [
+          "client-auth"
+        ],
+        "security": [],
+        "parameters": [],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/client-sign-in-result"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `token_spent`, `email_taken`, `target_state_conflict`, `quota_exceeded`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "**An app invitation, not a team one.** `POST /api/org/invitations/accept` is the other space and answers `204`; this one answers a session, because the person is landing in the developer's app and there is no second door for them to sign in through. The role is the one the invitation fixed at creation, so a later change to the app's default role does not re-aim a link already in somebody's inbox, and the invitation **bypasses `allowed_domains`** — a developer inviting somebody by hand has already made the decision the whitelist automates. The answer is a `clientSignInResult`: a `twoFactorChallenge` instead of tokens when the app requires two-factor. `password` is required while the app's password method is on and refused while it is off, both as `400 validation_error` naming the field. \n\n**One refusal for every token that does not work: `410 token_spent`** — unknown, expired past the seven days, revoked by the developer, or already accepted. There is one code because telling them apart would say whether a token ever existed, and because the one thing the holder of a dead link can do is ask the developer for a new one, whichever of the four it was. A chosen password under twelve characters is part of the `400 validation_error`, naming the `password` field. `409 email_taken` is an address this app has acquired since the invitation was written **as an account that is already in use** — the invitation stays outstanding rather than being spent, so the developer can revoke it or point the person at the login. An address that registered itself and is still `pending_verification` is not that state: accepting sets the password the invitee just chose, activates the account and gives it the invitation's role, because reading the invitation mail proves the address the verification link was waiting on. \n\n`409 target_state_conflict` names `role_id` with rule `not_set` when the role the invitation was fixed to has since been deleted and the app has no default role to fall back on: there is no access to hand the acceptor, and creating an account with none would be worse than saying so. \n\n**`409 quota_exceeded` when accepting would CREATE an account and the org is at its `max_end_users` limit**, counted across every app of the org. An invitation that names a row the developer already created, and one whose address is held by an unfinished self-registration, both finish an account that already counts — those are not refused, because the org is not one account larger afterwards. The token is not spent by the refusal: the developer can raise the limit, or delete somebody, and the same link still works.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/client-accept-invitation-request"
+              }
+            }
+          }
+        }
+      }
+    },
+    "/api/client/refresh": {
+      "post": {
+        "operationId": "post_api_client_refresh",
+        "summary": "Rotates an app-user refresh token and mints a fresh access token.",
+        "tags": [
+          "client-auth"
+        ],
+        "security": [],
+        "parameters": [],
+        "responses": {
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/session-tokens"
+                }
+              }
+            }
+          },
+          "default": {
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `token_expired`, `token_revoked`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/api-error"
+                }
+              }
+            }
+          }
+        },
+        "description": "The account is re-proved here, not just the token: refresh is where every session eventually re-proves itself, so a user who was blocked or deleted loses the family here even if the proactive revoke had not landed. A family minted from a `resource`-carrying token exchange keeps its audience across every rotation.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/client-refresh-request"
               }
             }
           }
         }
       }
     },
-    "/api/client/password/reset": {
+    "/api/client/logout": {
       "post": {
-        "operationId": "post_api_client_password_reset",
-        "summary": "Mails an app user a reset link, and answers the same either way.",
+        "operationId": "post_api_client_logout",
+        "summary": "Revokes an app-user refresh family.",
         "tags": [
           "client-auth"
         ],
         "security": [],
         "parameters": [],
         "responses": {
-          "202": {
+          "204": {
             "description": "Success."
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `not_found`.",
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -4525,27 +5135,37 @@
             }
           }
         },
-        "description": "**The app-user twin of `POST /api/auth/password/reset`, and a different shape** because the two surfaces name a person differently: a Fleetless address is globally unique and resolves alone, an app user's is unique only within their app, so the pair is the identifier. Status, body and timing are identical for a known and an unknown address. An account with no Fleetless password — one created through an identity provider — is mailed nothing and still answers `202`. `404 not_found` is the **app identifier**, never the address. The link points at the app's `reset_url`; an app that has configured none can send no mail, which the `202` does not distinguish, because saying so would answer for the address as well.",
+        "description": "**`204`, and a token the server does not recognise gets it too** — the end state a caller asked for is the end state they get, and distinguishing the two would say whether a token ever existed. It answered a body until 2026-09-05, reporting what was left of the session at the identity provider; that belonged to the hosted login flow, where Fleetless owned the browser. The developer's app owns it now and redirects to its own provider itself, knowing which one it is. Open `/realtime` sockets for the session are closed.",
         "requestBody": {
           "required": true,
           "content": {
             "application/json": {
               "schema": {
-                "$ref": "#/components/schemas/client-password-reset-request"
+                "$ref": "#/components/schemas/client-logout-request"
               }
             }
           }
         }
       }
     },
-    "/api/client/password/reset/confirm": {
+    "/api/client/password/change": {
       "post": {
-        "operationId": "post_api_client_password_reset_confirm",
-        "summary": "Spends a reset token, sets the new password and answers a fresh session.",
+        "operationId": "post_api_client_password_change",
+        "summary": "Changes an app user's own password and answers a fresh session.",
         "tags": [
           "client-auth"
         ],
-        "security": [],
+        "security": [
+          {
+            "developerSession": []
+          },
+          {
+            "clientToken": []
+          },
+          {
+            "serverKey": []
+          }
+        ],
         "parameters": [],
         "responses": {
           "200": {
@@ -4559,7 +5179,7 @@
             }
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `token_spent`.",
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `forbidden`, `validation_error`, `invalid_credentials`, `target_state_conflict`, `method_not_allowed`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -4569,27 +5189,37 @@
             }
           }
         },
-        "description": "**Every refresh family of that account is revoked**, then a fresh pair is minted for the caller — a forgotten password is one of the two states where somebody else may be holding a live session, and the person completing the reset is the one who should keep theirs. The account is activated if it was still `pending_verification`: reading a mail at that address is the same proof verification asks for. \n\n**One refusal for every token that does not work: `410 token_spent`** — unknown, past its hour, or already used. There is one code because distinguishing them would tell a stranger whether a token ever existed, and the recovery is identical either way: ask for a new link. A replacement password under twelve characters is a `400 validation_error` naming the `new_password` field — the twelve-character minimum is that field's schema rule, and it is refused the way any other malformed field is.",
+        "description": "`403 method_not_allowed` when the app has the password method off: a stored password stays stored but is not in use, so it is not changed either. The guard admits all three caller kinds, but a password belongs to an app user specifically — a developer bearer or a server key reaching this is `401 unauthorized`. Every other session of the account ends; the answer is the replacement pair, so the tab that made the change stays signed in. An app user belongs to one app, so \"every session\" is this app's. An account that has **no password** — an OIDC-only app user, which the schema admits — answers `409 target_state_conflict` naming the `password` field with rule `not_set`, not `401`: the session is live and the token is fine, it is the account that has nothing to change, and telling such a caller to sign in again sends them round a loop that ends here.",
         "requestBody": {
           "required": true,
           "content": {
             "application/json": {
               "schema": {
-                "$ref": "#/components/schemas/client-password-reset-confirm-request"
+                "$ref": "#/components/schemas/password-change-request"
               }
             }
           }
         }
       }
     },
-    "/api/client/invitations/accept": {
-      "post": {
-        "operationId": "post_api_client_invitations_accept",
-        "summary": "Spends an invitation token, creates or activates the app user and answers a session.",
+    "/api/client/me": {
+      "get": {
+        "operationId": "get_api_client_me",
+        "summary": "Answers who the calling token is and what it is allowed to reach.",
         "tags": [
           "client-auth"
         ],
-        "security": [],
+        "security": [
+          {
+            "developerSession": []
+          },
+          {
+            "clientToken": []
+          },
+          {
+            "serverKey": []
+          }
+        ],
         "parameters": [],
         "responses": {
           "200": {
@@ -4597,13 +5227,13 @@
             "content": {
               "application/json": {
                 "schema": {
-                  "$ref": "#/components/schemas/session-tokens"
+                  "$ref": "#/components/schemas/client-identity"
                 }
               }
             }
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `token_spent`, `email_taken`, `target_state_conflict`, `quota_exceeded`.",
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `forbidden`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -4613,23 +5243,13 @@
             }
           }
         },
-        "description": "**An app invitation, not a team one.** `POST /api/org/invitations/accept` is the other space and answers `204`; this one answers a session, because the person is landing in the developer's app and there is no second door for them to sign in through. The role is the one the invitation fixed at creation, so a later change to the app's default role does not re-aim a link already in somebody's inbox, and the invitation **bypasses `allowed_domains`** — a developer inviting somebody by hand has already made the decision the whitelist automates. \n\n**One refusal for every token that does not work: `410 token_spent`** — unknown, expired past the seven days, revoked by the developer, or already accepted. There is one code because telling them apart would say whether a token ever existed, and because the one thing the holder of a dead link can do is ask the developer for a new one, whichever of the four it was. A chosen password under twelve characters is part of the `400 validation_error`, naming the `password` field. `409 email_taken` is an address this app has acquired since the invitation was written **as an account that is already in use** — the invitation stays outstanding rather than being spent, so the developer can revoke it or point the person at the login. An address that registered itself and is still `pending_verification` is not that state: accepting sets the password the invitee just chose, activates the account and gives it the invitation's role, because reading the invitation mail proves the address the verification link was waiting on. \n\n`409 target_state_conflict` names `role_id` with rule `not_set` when the role the invitation was fixed to has since been deleted and the app has no default role to fall back on: there is no access to hand the acceptor, and creating an account with none would be worse than saying so. \n\n**`409 quota_exceeded` when accepting would CREATE an account and the org is at its `max_end_users` limit**, counted across every app of the org. An invitation that names a row the developer already created, and one whose address is held by an unfinished self-registration, both finish an account that already counts — those are not refused, because the org is not one account larger afterwards. The token is not spent by the refusal: the developer can raise the limit, or delete somebody, and the same link still works.",
-        "requestBody": {
-          "required": true,
-          "content": {
-            "application/json": {
-              "schema": {
-                "$ref": "#/components/schemas/client-accept-invitation-request"
-              }
-            }
-          }
-        }
+        "description": "The one route that answers for all three caller kinds — a developer bearer, an app-user bearer and a server key — which is why the shape names each of `developer_id`, `app_user_id` and `server_key_id` and fills exactly one."
       }
     },
-    "/api/client/refresh": {
+    "/api/client/two-factor/verify": {
       "post": {
-        "operationId": "post_api_client_refresh",
-        "summary": "Rotates an app-user refresh token and mints a fresh access token.",
+        "operationId": "post_api_client_two_factor_verify",
+        "summary": "Answers a two-factor challenge with an authenticator or recovery code, and answers the session.",
         "tags": [
           "client-auth"
         ],
@@ -4647,7 +5267,7 @@
             }
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `token_expired`, `token_revoked`.",
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `invalid_code`, `token_spent`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -4657,34 +5277,46 @@
             }
           }
         },
-        "description": "The account is re-proved here, not just the token: refresh is where every session eventually re-proves itself, so a user who was blocked or deleted loses the family here even if the proactive revoke had not landed. A family minted from a `resource`-carrying token exchange keeps its audience across every rotation.",
+        "description": "The challenge is the one a sign-in step answered with `two_factor_required`; it lives five minutes and takes five wrong codes, after which it is `410 token_spent` and the sign-in starts over. A wrong code is `400 invalid_code` with `details.attempts_left`. **A code is accepted at most once**: the same authenticator code sent twice, even at the same moment, signs in exactly once. A recovery code is spent by its use and audited as `app_user.recovery_code_used`. Exactly one of `code` and `recovery_code`, or `400 validation_error`.",
         "requestBody": {
           "required": true,
           "content": {
             "application/json": {
               "schema": {
-                "$ref": "#/components/schemas/client-refresh-request"
+                "$ref": "#/components/schemas/client-two-factor-verify-request"
               }
             }
           }
         }
       }
     },
-    "/api/client/logout": {
+    "/api/client/two-factor/setup": {
       "post": {
-        "operationId": "post_api_client_logout",
-        "summary": "Revokes an app-user refresh family.",
+        "operationId": "post_api_client_two_factor_setup",
+        "summary": "Starts an authenticator setup and answers its secret and otpauth URL.",
         "tags": [
           "client-auth"
         ],
-        "security": [],
+        "security": [
+          {
+            "clientToken": []
+          },
+          {}
+        ],
         "parameters": [],
         "responses": {
-          "204": {
-            "description": "Success."
+          "200": {
+            "description": "Success.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/two-factor-setup-response"
+                }
+              }
+            }
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`.",
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `token_spent`, `unauthorized`, `target_state_conflict`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -4694,36 +5326,31 @@
             }
           }
         },
-        "description": "**`204`, and a token the server does not recognise gets it too** — the end state a caller asked for is the end state they get, and distinguishing the two would say whether a token ever existed. It answered a body until 2026-09-05, reporting what was left of the session at the identity provider; that belonged to the hosted login flow, where Fleetless owned the browser. The developer's app owns it now and redirects to its own provider itself, knowing which one it is. Open `/realtime` sockets for the session are closed.",
+        "description": "**Two ways in, decided in the handler.** During sign-in the body carries the `two_factor_setup_required` challenge, and that is the credential; from the app's own account settings the app user's bearer is, with no challenge and an empty or missing body. Neither is `401 unauthorized`, and a dead challenge is `410 token_spent`. `409 target_state_conflict` names `two_factor` with rule `off` when the app's policy is `off`. The secret is not in use until `POST /api/client/two-factor/setup/confirm` accepts a code from it; a second call replaces a pending secret, and an account that already has an authenticator keeps it until the new one is confirmed.",
         "requestBody": {
-          "required": true,
+          "required": false,
           "content": {
             "application/json": {
               "schema": {
-                "$ref": "#/components/schemas/client-logout-request"
+                "$ref": "#/components/schemas/client-two-factor-setup-request"
               }
             }
           }
         }
       }
     },
-    "/api/client/password/change": {
+    "/api/client/two-factor/setup/confirm": {
       "post": {
-        "operationId": "post_api_client_password_change",
-        "summary": "Changes an app user's own password and answers a fresh session.",
+        "operationId": "post_api_client_two_factor_setup_confirm",
+        "summary": "Confirms the new authenticator with a code and answers the recovery codes and a session.",
         "tags": [
           "client-auth"
         ],
         "security": [
-          {
-            "developerSession": []
-          },
           {
             "clientToken": []
           },
-          {
-            "serverKey": []
-          }
+          {}
         ],
         "parameters": [],
         "responses": {
@@ -4732,13 +5359,13 @@
             "content": {
               "application/json": {
                 "schema": {
-                  "$ref": "#/components/schemas/session-tokens"
+                  "$ref": "#/components/schemas/client-two-factor-setup-confirm-response"
                 }
               }
             }
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `forbidden`, `validation_error`, `invalid_credentials`, `target_state_conflict`.",
+            "description": "An error envelope. Codes this route is known to answer: `rate_limited`, `validation_error`, `invalid_code`, `token_spent`, `unauthorized`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -4748,23 +5375,23 @@
             }
           }
         },
-        "description": "The guard admits all three caller kinds, but a password belongs to an app user specifically — a developer bearer or a server key reaching this is `401 unauthorized`. Every other session of the account ends; the answer is the replacement pair, so the tab that made the change stays signed in. An app user belongs to one app, so \"every session\" is this app's. An account that has **no password** — an OIDC-only app user, which the schema admits — answers `409 target_state_conflict` naming the `password` field with rule `not_set`, not `401`: the session is live and the token is fine, it is the account that has nothing to change, and telling such a caller to sign in again sends them round a loop that ends here.",
+        "description": "The same two ways in as `setup`. A code that does not match the pending secret is `400 invalid_code`; no pending setup, or a dead challenge, is `410 token_spent`. On success the authenticator is on, ten recovery codes are issued — shown this once, any earlier set void — and the answer carries a session: the one the sign-in was waiting for, or, from account settings, a fresh one while every other session of the account ends. Audited as `app_user.two_factor_enabled`.",
         "requestBody": {
           "required": true,
           "content": {
             "application/json": {
               "schema": {
-                "$ref": "#/components/schemas/password-change-request"
+                "$ref": "#/components/schemas/client-two-factor-setup-confirm-request"
               }
             }
           }
         }
       }
     },
-    "/api/client/me": {
-      "get": {
-        "operationId": "get_api_client_me",
-        "summary": "Answers who the calling token is and what it is allowed to reach.",
+    "/api/client/two-factor": {
+      "delete": {
+        "operationId": "delete_api_client_two_factor",
+        "summary": "Turns the signed-in app user's authenticator off.",
         "tags": [
           "client-auth"
         ],
@@ -4781,18 +5408,11 @@
         ],
         "parameters": [],
         "responses": {
-          "200": {
-            "description": "Success.",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/client-identity"
-                }
-              }
-            }
+          "204": {
+            "description": "Success."
           },
           "default": {
-            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `forbidden`.",
+            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `forbidden`, `rate_limited`, `validation_error`, `invalid_code`, `target_state_conflict`.",
             "content": {
               "application/json": {
                 "schema": {
@@ -4802,7 +5422,17 @@
             }
           }
         },
-        "description": "The one route that answers for all three caller kinds — a developer bearer, an app-user bearer and a server key — which is why the shape names each of `developer_id`, `app_user_id` and `server_key_id` and fills exactly one."
+        "description": "The app user's own door; a developer bearer or a server key is `401 unauthorized`, because the factor is the person's. A current code proves they still hold the authenticator: a stolen session alone cannot remove it. The authenticator and every recovery code go. `409 target_state_conflict` names `two_factor` with rule `required` while the app requires two-factor, and with rule `off` when there is none to remove. Audited as `app_user.two_factor_disabled`. The developer's support door is `DELETE /api/apps/:id/users/:userId/two-factor`.",
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "$ref": "#/components/schemas/client-two-factor-disable-request"
+              }
+            }
+          }
+        }
       }
     },
     "/api/client/providers": {
@@ -4997,7 +5627,7 @@
             }
           }
         },
-        "description": "**One callback URL for every app and every provider**, and the value of `appAuthConfig.oidc_callback_url` — the string a developer registers at their IdP. `CLIENT_OIDC_CALLBACK_PATH` in `client-auth.ts` is the single spelling of this path; the URL is that path on the cloud's canonical public base, never a friendly alias, because the provider compares the redirect target against the one string it was given. \n\n**Rate limited per ip, generously.** The first draft left this route unlimited on the argument that the caller is an identity provider redirecting somebody's browser, so a limiter would drop real sign-ins on the strength of traffic none of those people sent. The cost of that argument is a `state` obtained from one `start` being replayable for the interaction's full ten minutes, unbounded and unauthenticated, with every replay driving a server-side POST to the developer's token endpoint and one audit row into their org — an amplifier against a third party. The interaction is now spent on **every** terminal outcome, refusals included, which closes the replay itself; the limiter is the ceiling on how fast the attempts may arrive at all. It is per ip and sized for a browser, so a person completing a sign-in never meets it. `429 rate_limited` is the one `apiError` this route can answer, and it is not a sign-in outcome — it is a refusal to begin the work, which is why it does not ride back to the app as an `?error=`. \n\nThe query is the **provider's** rather than a Fleetless shape, and `clientOidcCallbackQuery` describes it **without being strict**: `state` always, `code` on success, `error` and `error_description` on the provider's own refusal, and whatever else that provider adds — RFC 9207's `iss`, a `session_state`, a vendor field. Refusing those would refuse conforming providers, the trap `POST /mcp/oauth/register` documents avoiding. `state` is the required field because it is the only one Fleetless minted. \n\n**It lists `rate_limited` and no other code, because every sign-in outcome it has is a redirect.** Success and failure alike are a `302` to the app's own `redirect_uri`: `?code=…&state=…` when a session was resolved, `?error=<clientOidcErrorCode>&state=…` when it was not, so the app renders its own message and can bind either answer to the request it started. Fleetless shows an app user no page. \n\n**The one exception is a `state` that resolves to no interaction** — unknown, hand-edited, or past its ten minutes. Then there is no confirmed redirect target to carry the answer to, and bouncing a browser to an unvalidated one is the hole the whole flow is arranged to avoid, so the cloud renders an HTML problem page at `400`. That is the only Fleetless-rendered surface an app user can reach. It is HTML rather than an `apiError`, which is why no code is listed: a code here would document an envelope no caller receives, and this manifest's other HTML pages (`GET /mcp/oauth/interaction/:id`, `GET /console/oauth/interaction/:id`) say their status in prose for the same reason."
+        "description": "**One callback URL for every app and every provider**, and the value of `appAuthConfig.oidc_callback_url` — the string a developer registers at their IdP. `CLIENT_OIDC_CALLBACK_PATH` in `client-auth.ts` is the single spelling of this path; the URL is that path on the cloud's canonical public base, never a friendly alias, because the provider compares the redirect target against the one string it was given. \n\n**Rate limited per ip, generously.** The first draft left this route unlimited on the argument that the caller is an identity provider redirecting somebody's browser, so a limiter would drop real sign-ins on the strength of traffic none of those people sent. The cost of that argument is a `state` obtained from one `start` being replayable for the interaction's full ten minutes, unbounded and unauthenticated, with every replay driving a server-side POST to the developer's token endpoint and one audit row into their org — an amplifier against a third party. The interaction is now spent on **every** terminal outcome, refusals included, which closes the replay itself; the limiter is the ceiling on how fast the attempts may arrive at all. It is per ip and sized for a browser, so a person completing a sign-in never meets it. `429 rate_limited` is the one `apiError` this route can answer, and it is not a sign-in outcome — it is a refusal to begin the work, which is why it does not ride back to the app as an `?error=`. \n\nThe query is the **provider's** rather than a Fleetless shape, and `clientOidcCallbackQuery` describes it **without being strict**: `state` always, `code` on success, `error` and `error_description` on the provider's own refusal, and whatever else that provider adds — RFC 9207's `iss`, a `session_state`, a vendor field. Refusing those would refuse conforming providers, the trap `POST /mcp/oauth/register` documents avoiding. `state` is the required field because it is the only one Fleetless minted. \n\n**It lists `rate_limited` and no other code, because every sign-in outcome it has is a redirect.** Success and failure alike are a `302` to the app's own `redirect_uri`: `?code=…&state=…` when a session was resolved, `?error=<clientOidcErrorCode>&state=…` when it was not, so the app renders its own message and can bind either answer to the request it started. This route renders no page for an outcome. \n\n**The one exception is a `state` that resolves to no interaction** — unknown, hand-edited, or past its ten minutes. Then there is no confirmed redirect target to carry the answer to, and bouncing a browser to an unvalidated one is the hole the whole flow is arranged to avoid, so the cloud renders an HTML problem page at `400`. It is HTML rather than an `apiError`, which is why no code is listed: a code here would document an envelope no caller receives, and this manifest's other HTML pages (`GET /mcp/oauth/interaction/:id`, `GET /console/oauth/interaction/:id`) say their status in prose for the same reason."
       }
     },
     "/api/client/oidc/exchange": {
@@ -8624,54 +9254,6 @@
         },
         "description": "A window longer than `USAGE_WINDOW_MAX_DAYS` is refused naming the field, not silently capped: a caller who asked for more than the platform will answer is owed a refusal, not a shorter answer they will mistake for the whole picture. `from_day <= to_day` is a cross-field rule no JSON Schema can express and is enforced here. The window is echoed back."
       }
-    },
-    "/api/feedback": {
-      "post": {
-        "operationId": "post_api_feedback",
-        "summary": "Sends a message from a developer to the people who build Fleetless.",
-        "tags": [
-          "org"
-        ],
-        "security": [
-          {
-            "developerSession": []
-          }
-        ],
-        "parameters": [],
-        "responses": {
-          "202": {
-            "description": "Success.",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/feedback-response"
-                }
-              }
-            }
-          },
-          "default": {
-            "description": "An error envelope. Codes this route is known to answer: `unauthorized`, `token_expired`, `token_revoked`, `validation_error`, `rate_limited`.",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/api-error"
-                }
-              }
-            }
-          }
-        },
-        "description": "The message is stored before any mail is tried, so `202` means it is kept whatever `mail` says: `sent`, `failed`, or `not_configured` when this cloud has no feedback address. At most 10 messages per developer per hour; the 11th answers `429 rate_limited` with `retry_after_ms`. Replies come by mail, to the sender's address.",
-        "requestBody": {
-          "required": true,
-          "content": {
-            "application/json": {
-              "schema": {
-                "$ref": "#/components/schemas/feedback-request"
-              }
-            }
-          }
-        }
-      }
     }
   },
   "components": {
@@ -8701,16 +9283,22 @@
             "minLength": 1,
             "description": "The opaque invitation token from the link. Unknown, expired and already-accepted all collapse into `410 token_spent` — telling them apart would say whether a token ever existed."
           },
-          "password": {
-            "type": "string",
-            "minLength": 12,
-            "maxLength": 256,
-            "description": "The password the new Fleetless account will use. At least 12 characters."
+          "display_name": {
+            "description": "An optional name, overriding whatever the invitation pre-filled. Absent keeps it.",
+            "anyOf": [
+              {
+                "type": "string",
+                "minLength": 1,
+                "maxLength": 120
+              },
+              {
+                "type": "null"
+              }
+            ]
           }
         },
         "required": [
-          "token",
-          "password"
+          "token"
         ],
         "additionalProperties": false
       },
@@ -9013,7 +9601,7 @@
                 "type": "null"
               }
             ],
-            "description": "The page in the developer's app that accepts an invitation, with `{token}` where the token goes. `null` when unconfigured, and then an invitation still issues but `send_mail` is refused with `409 target_state_conflict` — there would be nowhere for the link to point."
+            "description": "The page in the developer's app that accepts an invitation, with `{token}` where the token goes. `null` means the hosted page in `hosted_pages` is used."
           },
           "verify_url": {
             "anyOf": [
@@ -9025,7 +9613,7 @@
                 "type": "null"
               }
             ],
-            "description": "The page that confirms a new address, with `{token}` where the token goes. Self-registration needs it: without a page to send people to, a registration would leave an account nobody can activate."
+            "description": "The page that confirms a new address, with `{token}` where the token goes. `null` means the hosted page in `hosted_pages` is used."
           },
           "reset_url": {
             "anyOf": [
@@ -9037,19 +9625,117 @@
                 "type": "null"
               }
             ],
-            "description": "The page that takes a new password, with `{token}` where the token goes."
+            "description": "The page that takes a new password, with `{token}` where the token goes. `null` means the hosted page in `hosted_pages` is used."
+          },
+          "mcp_login_url": {
+            "anyOf": [
+              {
+                "type": "string",
+                "maxLength": 500
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The page an MCP authorization redirects to, with `{interaction}` where the interaction id goes. Not a token: the id names a pending request the server already holds, and the app authenticates the user itself before approving it. `null` means the hosted MCP sign-in in `hosted_pages` is used."
+          },
+          "app_url": {
+            "anyOf": [
+              {
+                "type": "string",
+                "maxLength": 500,
+                "format": "uri"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The app's own home page, linked as `Open <app>` when a hosted flow is done. `null` makes the hosted done page say `You can close this tab`."
+          },
+          "sign_in_methods": {
+            "type": "object",
+            "properties": {
+              "password": {
+                "type": "boolean",
+                "description": "Whether app users may sign in with a password. Off refuses `POST /api/client/login` with `method_not_allowed`, and registration and invitations then take no password."
+              },
+              "email_code": {
+                "type": "boolean",
+                "description": "Whether app users may sign in with a six-digit code mailed to them, valid ten minutes. A code needs no URL, so it works in local development and in an app with no web UI."
+              }
+            },
+            "required": [
+              "password",
+              "email_code"
+            ],
+            "additionalProperties": false,
+            "description": "Which sign-in methods the app offers: password, emailed code, or both — at least one. Identity providers stay on top of either. The default is password only."
+          },
+          "two_factor": {
+            "type": "string",
+            "enum": [
+              "off",
+              "optional",
+              "required"
+            ],
+            "description": "Whether the app asks for an authenticator code: `off` (the default), `optional` or `required`. A person with a confirmed authenticator is asked at every sign-in whatever the policy; a sign-in through an identity provider is never asked."
+          },
+          "hosted_logo_url": {
+            "anyOf": [
+              {
+                "type": "string",
+                "format": "uri"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Where the hosted pages load the app's logo from, `<portal>/app/<identifier>/logo`, or `null` when no logo is stored. **Read-only** — the logo is written through `PUT /api/apps/:id/auth-config/logo`."
+          },
+          "hosted_accent": {
+            "anyOf": [
+              {
+                "type": "string",
+                "pattern": "^#[0-9a-f]{6}$"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The accent colour of the hosted pages, `#rrggbb` in lowercase, or `null` for the neutral shell's own."
           },
-          "mcp_login_url": {
-            "anyOf": [
-              {
+          "hosted_pages": {
+            "type": "object",
+            "properties": {
+              "invite_url": {
                 "type": "string",
-                "maxLength": 500
+                "format": "uri",
+                "description": "The hosted invitation page, `<portal>/app/<identifier>/invite/{token}`."
               },
-              {
-                "type": "null"
+              "verify_url": {
+                "type": "string",
+                "format": "uri",
+                "description": "The hosted email-confirmation page, `<portal>/app/<identifier>/verify/{token}`."
+              },
+              "reset_url": {
+                "type": "string",
+                "format": "uri",
+                "description": "The hosted new-password page, `<portal>/app/<identifier>/reset/{token}`."
+              },
+              "mcp_login_url": {
+                "type": "string",
+                "format": "uri",
+                "description": "The hosted MCP sign-in, `<portal>/app/<identifier>/mcp/{interaction}`."
               }
+            },
+            "required": [
+              "invite_url",
+              "verify_url",
+              "reset_url",
+              "mcp_login_url"
             ],
-            "description": "The page an MCP authorization redirects to, with `{interaction}` where the interaction id goes. Not a token: the id names a pending request the server already holds, and the app authenticates the user itself before approving it."
+            "additionalProperties": false,
+            "description": "The Fleetless-hosted pages an unset URL falls back to, as templates. **Read-only**: minted by the cloud from the auth portal and the app's identifier."
           },
           "oidc_callback_url": {
             "type": "string",
@@ -9072,6 +9758,12 @@
           "verify_url",
           "reset_url",
           "mcp_login_url",
+          "app_url",
+          "sign_in_methods",
+          "two_factor",
+          "hosted_logo_url",
+          "hosted_accent",
+          "hosted_pages",
           "oidc_callback_url",
           "updated_at"
         ],
@@ -9161,17 +9853,10 @@
             "description": "When the token stops working. Seven days from issue; an expired token answers exactly as an unknown one does."
           },
           "accept_url": {
-            "anyOf": [
-              {
-                "type": "string",
-                "maxLength": 500,
-                "format": "uri"
-              },
-              {
-                "type": "null"
-              }
-            ],
-            "description": "The link to give the invitee, built from the app's `invite_url` with the token substituted for `{token}`. **`null` when the app has configured no `invite_url`** — there is nowhere for the link to point, and Fleetless serves no page of its own for an app user. Bounded like every other URL that gets mailed, logged and rendered."
+            "type": "string",
+            "maxLength": 500,
+            "format": "uri",
+            "description": "The link to give the invitee: the app's `invite_url` with the token substituted for `{token}`, or the Fleetless-hosted invitation page when the app has configured none. Bounded like every other URL that gets mailed, logged and rendered."
           },
           "mail": {
             "type": "string",
@@ -9181,7 +9866,7 @@
               "not_configured",
               "failed"
             ],
-            "description": "What happened to the mail: `sent` means the SMTP server accepted it, not that it was delivered; `not_requested` means none was attempted — the caller asked for none, or the app has no `invite_url` for a link to point at; `not_configured` is an expected state and not a failure; `failed` is the one worth somebody's attention."
+            "description": "What happened to the mail: `sent` means the SMTP server accepted it, not that it was delivered; `not_requested` means none was attempted because the caller asked for none; `not_configured` is an expected state and not a failure; `failed` is the one worth somebody's attention."
           }
         },
         "required": [
@@ -9340,9 +10025,10 @@
             "enum": [
               "invite",
               "verify",
-              "reset"
+              "reset",
+              "login_code"
             ],
-            "description": "Which of the three mails this template replaces."
+            "description": "Which of the four mails this template replaces."
           },
           "subject": {
             "type": "string",
@@ -9389,7 +10075,7 @@
         "type": "object",
         "properties": {
           "templates": {
-            "maxItems": 3,
+            "maxItems": 4,
             "type": "array",
             "items": {
               "type": "object",
@@ -9399,9 +10085,10 @@
                   "enum": [
                     "invite",
                     "verify",
-                    "reset"
+                    "reset",
+                    "login_code"
                   ],
-                  "description": "Which of the three mails this template replaces."
+                  "description": "Which of the four mails this template replaces."
                 },
                 "subject": {
                   "type": "string",
@@ -9699,6 +10386,41 @@
             ],
             "description": "When this user last signed in, or `null` if they never have. Required and nullable rather than optional, so *never logged in* stays distinguishable from *this field was not loaded*."
           },
+          "two_factor": {
+            "type": "object",
+            "properties": {
+              "enabled": {
+                "type": "boolean",
+                "description": "Whether the account has a confirmed authenticator app (TOTP). When it has, every sign-in that yields a session asks for a code as well — whatever the app's policy — except a sign-in through an identity provider, which owns that sign-in."
+              },
+              "enabled_at": {
+                "anyOf": [
+                  {
+                    "type": "string",
+                    "format": "date-time",
+                    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "When the authenticator was confirmed, or `null` while `enabled` is `false`."
+              },
+              "recovery_codes_left": {
+                "type": "integer",
+                "minimum": 0,
+                "maximum": 10,
+                "description": "How many of the ten single-use recovery codes are still unspent. `0` while `enabled` is `false`."
+              }
+            },
+            "required": [
+              "enabled",
+              "enabled_at",
+              "recovery_codes_left"
+            ],
+            "additionalProperties": false,
+            "description": "The account's second factor, as a developer's user list shows it. No secret and no code travels here; resetting it is `DELETE /api/apps/:id/users/:userId/two-factor`."
+          },
           "created_at": {
             "type": "string",
             "format": "date-time",
@@ -9716,6 +10438,7 @@
           "has_password",
           "providers",
           "last_login_at",
+          "two_factor",
           "created_at"
         ],
         "additionalProperties": false
@@ -9801,6 +10524,41 @@
                   ],
                   "description": "When this user last signed in, or `null` if they never have. Required and nullable rather than optional, so *never logged in* stays distinguishable from *this field was not loaded*."
                 },
+                "two_factor": {
+                  "type": "object",
+                  "properties": {
+                    "enabled": {
+                      "type": "boolean",
+                      "description": "Whether the account has a confirmed authenticator app (TOTP). When it has, every sign-in that yields a session asks for a code as well — whatever the app's policy — except a sign-in through an identity provider, which owns that sign-in."
+                    },
+                    "enabled_at": {
+                      "anyOf": [
+                        {
+                          "type": "string",
+                          "format": "date-time",
+                          "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
+                        },
+                        {
+                          "type": "null"
+                        }
+                      ],
+                      "description": "When the authenticator was confirmed, or `null` while `enabled` is `false`."
+                    },
+                    "recovery_codes_left": {
+                      "type": "integer",
+                      "minimum": 0,
+                      "maximum": 10,
+                      "description": "How many of the ten single-use recovery codes are still unspent. `0` while `enabled` is `false`."
+                    }
+                  },
+                  "required": [
+                    "enabled",
+                    "enabled_at",
+                    "recovery_codes_left"
+                  ],
+                  "additionalProperties": false,
+                  "description": "The account's second factor, as a developer's user list shows it. No secret and no code travels here; resetting it is `DELETE /api/apps/:id/users/:userId/two-factor`."
+                },
                 "created_at": {
                   "type": "string",
                   "format": "date-time",
@@ -9818,6 +10576,7 @@
                 "has_password",
                 "providers",
                 "last_login_at",
+                "two_factor",
                 "created_at"
               ],
               "additionalProperties": false
@@ -10558,6 +11317,10 @@
                 "maxLength": 120,
                 "description": "The organisation's display name. Free text, changed through `PATCH /api/org`."
               },
+              "require_two_factor": {
+                "type": "boolean",
+                "description": "Whether every member must have a second factor — a passkey or an authenticator app. A member without one sets it up at their next sign-in, before any session exists; nobody is signed out when it is switched on. It covers the console and the central MCP endpoint; server keys and robot bridges are not people and are not affected. Owners change it through `PATCH /api/org`."
+              },
               "created_at": {
                 "type": "string",
                 "format": "date-time",
@@ -10568,6 +11331,7 @@
             "required": [
               "id",
               "name",
+              "require_two_factor",
               "created_at"
             ],
             "additionalProperties": false
@@ -10614,6 +11378,27 @@
                 ],
                 "description": "The console powers this person holds. **Required** — every Fleetless user has a tier; it was optional only while the org also held people with no console powers to grade, and that pool is gone."
               },
+              "two_factor": {
+                "type": "object",
+                "properties": {
+                  "passkeys": {
+                    "type": "integer",
+                    "minimum": 0,
+                    "maximum": 9007199254740991,
+                    "description": "How many passkeys the person has registered."
+                  },
+                  "authenticator": {
+                    "type": "boolean",
+                    "description": "Whether the person has a confirmed authenticator app."
+                  }
+                },
+                "required": [
+                  "passkeys",
+                  "authenticator"
+                ],
+                "additionalProperties": false,
+                "description": "The person's second factors, as the team list shows them: none, passkeys, an authenticator, or both. No credential travels here. An owner resets them through `DELETE /api/org/users/:id/two-factor`."
+              },
               "created_at": {
                 "type": "string",
                 "format": "date-time",
@@ -10627,6 +11412,7 @@
               "email",
               "display_name",
               "tier",
+              "two_factor",
               "created_at"
             ],
             "additionalProperties": false
@@ -10802,10 +11588,10 @@
             "description": "The opaque token from the invitation link, valid seven days. Unknown, expired, revoked and already-accepted all answer `410 token_spent`."
           },
           "password": {
+            "description": "The password the new account will use, at least 12 characters. **Required while the app's password method is on, refused while it is off** — both as `400 validation_error` naming `password`. An email-code-only app accepts invitations without one.",
             "type": "string",
             "minLength": 12,
-            "maxLength": 256,
-            "description": "The password the new account will use."
+            "maxLength": 256
           },
           "display_name": {
             "description": "An optional name, overriding whatever the invitation pre-filled.",
@@ -10822,8 +11608,7 @@
           }
         },
         "required": [
-          "token",
-          "password"
+          "token"
         ],
         "additionalProperties": false
       },
@@ -10916,6 +11701,17 @@
               }
             ],
             "description": "The address of the Fleetless user or app user behind this session, and `null` for a server key, which is not a person."
+          },
+          "two_factor_enabled": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Whether the app user has a confirmed authenticator, so the app's account settings can offer to turn it on or off. `null` unless `kind` is `app_user`."
           }
         },
         "required": [
@@ -10925,10 +11721,63 @@
           "server_key_id",
           "app_id",
           "role_id",
+          "email",
+          "two_factor_enabled"
+        ],
+        "additionalProperties": false
+      },
+      "client-login-code-request": {
+        "type": "object",
+        "properties": {
+          "app_identifier": {
+            "type": "string",
+            "minLength": 2,
+            "maxLength": 63,
+            "pattern": "^[a-z][a-z0-9]*(?:_[a-z0-9]+)*$",
+            "description": "The app to sign in to. An identifier no app carries is `404 not_found`; the address is never the subject of a refusal."
+          },
+          "email": {
+            "type": "string",
+            "format": "email",
+            "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+            "description": "The address to mail the code to, trimmed and compared case-insensitively. `202` whether or not it names an account of this app."
+          }
+        },
+        "required": [
+          "app_identifier",
           "email"
         ],
         "additionalProperties": false
       },
+      "client-login-code-verify-request": {
+        "type": "object",
+        "properties": {
+          "app_identifier": {
+            "type": "string",
+            "minLength": 2,
+            "maxLength": 63,
+            "pattern": "^[a-z][a-z0-9]*(?:_[a-z0-9]+)*$",
+            "description": "The app the code was requested for."
+          },
+          "email": {
+            "type": "string",
+            "format": "email",
+            "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+            "description": "The address the code was mailed to, as typed when it was requested; trimmed and compared case-insensitively."
+          },
+          "code": {
+            "type": "string",
+            "pattern": "^\\d{6}$",
+            "description": "The six digits from the mail, exactly — leading zeros included, no spaces."
+          }
+        },
+        "required": [
+          "app_identifier",
+          "email",
+          "code"
+        ],
+        "additionalProperties": false
+      },
       "client-login-request": {
         "type": "object",
         "properties": {
@@ -11131,11 +11980,31 @@
               ],
               "additionalProperties": false
             },
-            "description": "The app's **enabled** providers, slug and display name only. An app with none answers an empty array, which is the state of an app that offers password login alone."
+            "description": "The app's **enabled** providers, slug and display name only. An app with none answers an empty array, which is the state of an app that offers password or code sign-in alone."
+          },
+          "sign_in_methods": {
+            "type": "object",
+            "properties": {
+              "password": {
+                "type": "boolean",
+                "description": "Whether app users may sign in with a password. Off refuses `POST /api/client/login` with `method_not_allowed`, and registration and invitations then take no password."
+              },
+              "email_code": {
+                "type": "boolean",
+                "description": "Whether app users may sign in with a six-digit code mailed to them, valid ten minutes. A code needs no URL, so it works in local development and in an app with no web UI."
+              }
+            },
+            "required": [
+              "password",
+              "email_code"
+            ],
+            "additionalProperties": false,
+            "description": "Which of password and emailed code the app accepts, so its sign-in page draws the right fields without guessing. The same value the developer set; public, like the provider buttons."
           }
         },
         "required": [
-          "providers"
+          "providers",
+          "sign_in_methods"
         ],
         "additionalProperties": false
       },
@@ -11169,10 +12038,10 @@
             "description": "The address to register. Unique per app, case-insensitively. An address this app already knows still answers `202`, without a mail — the answer may not say whether an account exists."
           },
           "password": {
+            "description": "The password for the new account, at least 12 characters. **Required while the app's password method is on, refused while it is off** — both as `400 validation_error` naming `password`. An email-code-only app registers people without one.",
             "type": "string",
             "minLength": 12,
-            "maxLength": 256,
-            "description": "The password for the new account. At least 12 characters; length only, because a rule a user cannot predict is a rule they work around."
+            "maxLength": 256
           },
           "display_name": {
             "description": "An optional human name for the account. The developer's own UI decides whether to ask for it.",
@@ -11190,8 +12059,7 @@
         },
         "required": [
           "app_identifier",
-          "email",
-          "password"
+          "email"
         ],
         "additionalProperties": false
       },
@@ -11297,11 +12165,181 @@
               ],
               "additionalProperties": false
             },
-            "description": "Every robot the caller reaches, in name order with the id as the tiebreak. An app user reaches the robots their app attaches on which their role grants at least one slug or capability; a server key reaches every robot its app attaches; a developer reaches every robot of the organisation."
+            "description": "Every robot the caller reaches, in name order with the id as the tiebreak. An app user reaches the robots their app attaches on which their role grants at least one slug or capability; a server key reaches every robot its app attaches; a developer reaches every robot of the organisation."
+          }
+        },
+        "required": [
+          "robots"
+        ],
+        "additionalProperties": false
+      },
+      "client-sign-in-result": {
+        "anyOf": [
+          {
+            "type": "object",
+            "properties": {
+              "access_token": {
+                "type": "string",
+                "minLength": 1,
+                "description": "The token to send as `Authorization: Bearer <token>` on every call. Short-lived: read `expires_in` rather than assuming a lifetime."
+              },
+              "refresh_token": {
+                "type": "string",
+                "minLength": 1,
+                "description": "The token that buys the next access token. It rotates on every use, so a value presented twice is detectable theft and ends the whole family."
+              },
+              "expires_in": {
+                "type": "integer",
+                "exclusiveMinimum": 0,
+                "maximum": 9007199254740991,
+                "description": "How long the access token stays valid, in **seconds** from now. Not a timestamp, and not milliseconds."
+              }
+            },
+            "required": [
+              "access_token",
+              "refresh_token",
+              "expires_in"
+            ],
+            "additionalProperties": false
+          },
+          {
+            "type": "object",
+            "properties": {
+              "status": {
+                "type": "string",
+                "enum": [
+                  "two_factor_required",
+                  "two_factor_setup_required"
+                ],
+                "description": "`two_factor_required`: ask for the authenticator code. `two_factor_setup_required`: the app requires two-factor and the person has none yet, so set one up before any session exists."
+              },
+              "challenge": {
+                "type": "string",
+                "minLength": 1,
+                "description": "The handle the next step spends. Valid five minutes; afterwards it answers `410 token_spent` and the sign-in starts over."
+              }
+            },
+            "required": [
+              "status",
+              "challenge"
+            ],
+            "additionalProperties": false
+          }
+        ]
+      },
+      "client-two-factor-disable-request": {
+        "type": "object",
+        "properties": {
+          "code": {
+            "type": "string",
+            "pattern": "^\\d{6}$",
+            "description": "A code the authenticator shows now."
+          }
+        },
+        "required": [
+          "code"
+        ],
+        "additionalProperties": false
+      },
+      "client-two-factor-setup-confirm-request": {
+        "type": "object",
+        "properties": {
+          "challenge": {
+            "description": "The same challenge as at `setup`, during sign-in; absent with a bearer.",
+            "type": "string",
+            "minLength": 1
+          },
+          "code": {
+            "type": "string",
+            "pattern": "^\\d{6}$",
+            "description": "A code the new authenticator shows now. It proves the secret was copied correctly before anything depends on it."
+          }
+        },
+        "required": [
+          "code"
+        ],
+        "additionalProperties": false
+      },
+      "client-two-factor-setup-confirm-response": {
+        "type": "object",
+        "properties": {
+          "recovery_codes": {
+            "minItems": 10,
+            "maxItems": 10,
+            "type": "array",
+            "items": {
+              "type": "string",
+              "pattern": "^[a-z2-7]{5}-[a-z2-7]{5}$"
+            },
+            "description": "The ten single-use recovery codes, lowercase, shown once. Any earlier set is void."
+          },
+          "session": {
+            "type": "object",
+            "properties": {
+              "access_token": {
+                "type": "string",
+                "minLength": 1,
+                "description": "The token to send as `Authorization: Bearer <token>` on every call. Short-lived: read `expires_in` rather than assuming a lifetime."
+              },
+              "refresh_token": {
+                "type": "string",
+                "minLength": 1,
+                "description": "The token that buys the next access token. It rotates on every use, so a value presented twice is detectable theft and ends the whole family."
+              },
+              "expires_in": {
+                "type": "integer",
+                "exclusiveMinimum": 0,
+                "maximum": 9007199254740991,
+                "description": "How long the access token stays valid, in **seconds** from now. Not a timestamp, and not milliseconds."
+              }
+            },
+            "required": [
+              "access_token",
+              "refresh_token",
+              "expires_in"
+            ],
+            "additionalProperties": false,
+            "description": "The session the sign-in was waiting for, or a fresh one for the account settings."
           }
         },
         "required": [
-          "robots"
+          "recovery_codes",
+          "session"
+        ],
+        "additionalProperties": false
+      },
+      "client-two-factor-setup-request": {
+        "type": "object",
+        "properties": {
+          "challenge": {
+            "description": "The `two_factor_setup_required` challenge, during sign-in. Absent when the call carries the app user's bearer instead.",
+            "type": "string",
+            "minLength": 1
+          }
+        },
+        "additionalProperties": false
+      },
+      "client-two-factor-verify-request": {
+        "type": "object",
+        "properties": {
+          "challenge": {
+            "type": "string",
+            "minLength": 1,
+            "description": "The challenge the sign-in step answered."
+          },
+          "code": {
+            "description": "The six-digit code the authenticator shows now. A code already accepted once is refused, so a replay of a seen code does not sign anybody in.",
+            "type": "string",
+            "pattern": "^\\d{6}$"
+          },
+          "recovery_code": {
+            "description": "One of the ten recovery codes, `xxxxx-xxxxx`, in either case. Spent by its use.",
+            "type": "string",
+            "pattern": "^[a-zA-Z2-7]{5}-[a-zA-Z2-7]{5}$"
+          }
+        },
+        "required": [
+          "challenge"
         ],
         "additionalProperties": false
       },
@@ -13635,7 +14673,7 @@
           },
           "send_mail": {
             "type": "boolean",
-            "description": "Whether Fleetless mails the invitation. **Refused with `409 target_state_conflict` naming `invite_url` when the app has configured none** — there would be nowhere for the link to point, and a mail carrying a Fleetless-hosted page is a surface this product does not have."
+            "description": "Whether Fleetless mails the invitation. The link points at the app's `invite_url`, or at the Fleetless-hosted invitation page when the app has configured none — so the mail always leads somewhere, and nothing is refused for a missing URL."
           }
         },
         "required": [
@@ -13783,6 +14821,113 @@
         ],
         "additionalProperties": false
       },
+      "create-passkey-request": {
+        "type": "object",
+        "properties": {
+          "name": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 80,
+            "description": "What to call the passkey, such as the device it lives on."
+          },
+          "credential": {
+            "type": "object",
+            "propertyNames": {
+              "type": "string"
+            },
+            "additionalProperties": {},
+            "description": "The browser's `RegistrationResponseJSON` for the options `POST /api/auth/passkeys/options` answered."
+          }
+        },
+        "required": [
+          "name",
+          "credential"
+        ],
+        "additionalProperties": false
+      },
+      "create-passkey-response": {
+        "type": "object",
+        "properties": {
+          "passkey": {
+            "type": "object",
+            "properties": {
+              "id": {
+                "type": "string",
+                "format": "uuid",
+                "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+                "description": "The passkey in the API, as renamed and removed through `/api/auth/passkeys/:id`."
+              },
+              "name": {
+                "type": "string",
+                "minLength": 1,
+                "maxLength": 80,
+                "description": "What the person called it, such as the device it lives on."
+              },
+              "created_at": {
+                "type": "string",
+                "format": "date-time",
+                "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+                "description": "When it was registered."
+              },
+              "last_used_at": {
+                "anyOf": [
+                  {
+                    "type": "string",
+                    "format": "date-time",
+                    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "When it last signed the person in or confirmed a sign-in, or `null` if never."
+              },
+              "synced": {
+                "anyOf": [
+                  {
+                    "type": "boolean"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Whether the authenticator reported the passkey as syncable across the person's devices (the backup-eligible flag), or `null` when it said nothing."
+              }
+            },
+            "required": [
+              "id",
+              "name",
+              "created_at",
+              "last_used_at",
+              "synced"
+            ],
+            "additionalProperties": false,
+            "description": "The passkey as it is now stored."
+          },
+          "recovery_codes": {
+            "anyOf": [
+              {
+                "minItems": 10,
+                "maxItems": 10,
+                "type": "array",
+                "items": {
+                  "type": "string",
+                  "pattern": "^[a-z2-7]{5}-[a-z2-7]{5}$"
+                }
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The ten recovery codes, shown once, when this passkey is the account's first second factor; `null` when the account already had one and its codes stay valid."
+          }
+        },
+        "required": [
+          "passkey",
+          "recovery_codes"
+        ],
+        "additionalProperties": false
+      },
       "create-robot-request": {
         "type": "object",
         "properties": {
@@ -13939,96 +15084,255 @@
           }
         },
         "required": [
-          "email",
-          "tier",
-          "send_mail"
+          "email",
+          "tier",
+          "send_mail"
+        ],
+        "additionalProperties": false
+      },
+      "datapoint-list-response": {
+        "type": "object",
+        "properties": {
+          "datapoints": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "properties": {
+                "slug": {
+                  "type": "string",
+                  "minLength": 2,
+                  "maxLength": 63,
+                  "pattern": "^[a-z][a-z0-9]*(?:_[a-z0-9]+)*$",
+                  "description": "The name a client reads this datapoint by."
+                },
+                "builtin": {
+                  "type": "boolean",
+                  "description": "`true` for the datapoints every robot has — `bridge_state` and `robot_details` — and `false` for everything the published configuration adds."
+                },
+                "unit": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ],
+                  "description": "The unit the value carries **after** any scale and offset, shown beside the number so nobody has to guess whether `15` means percent, volts or minutes. `null` when the configuration names none."
+                },
+                "rate_throttle_hz": {
+                  "anyOf": [
+                    {
+                      "type": "number",
+                      "minimum": 0,
+                      "maximum": 20
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ],
+                  "description": "The ceiling on how often this datapoint is sent, in hertz. `null` means no ceiling is configured, which is also the answer for every built-in. A ceiling, not a clock: a slow topic stays slow and no value is repeated to manufacture a rate."
+                }
+              },
+              "required": [
+                "slug",
+                "builtin",
+                "unit",
+                "rate_throttle_hz"
+              ],
+              "additionalProperties": false
+            },
+            "description": "Everything a client may read on this robot: the two built-ins, plus every datapoint the published configuration exposes and the caller's role grants."
+          }
+        },
+        "required": [
+          "datapoints"
+        ],
+        "additionalProperties": false
+      },
+      "datapoint-value": {
+        "type": "object",
+        "properties": {
+          "slug": {
+            "type": "string",
+            "minLength": 2,
+            "maxLength": 63,
+            "pattern": "^[a-z][a-z0-9]*(?:_[a-z0-9]+)*$",
+            "description": "The datapoint this value belongs to."
+          },
+          "value": {
+            "description": "The value, shaped by the datapoint: a number, a boolean, a string, or the whole ROS message where the configuration names no field inside it. Any `scale` and `offset` the configuration declares have already been applied, at the robot."
+          },
+          "timestamp_ms": {
+            "type": "integer",
+            "minimum": 0,
+            "maximum": 9007199254740991,
+            "description": "When the value was captured, as a unix timestamp in milliseconds. The **bridge's capture time**, never the time the cloud received it — the one exception is the built-in `bridge_state`, which the cloud observes by construction."
+          }
+        },
+        "required": [
+          "slug",
+          "value",
+          "timestamp_ms"
+        ],
+        "additionalProperties": false
+      },
+      "developer-passkey": {
+        "type": "object",
+        "properties": {
+          "id": {
+            "type": "string",
+            "format": "uuid",
+            "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+            "description": "The passkey in the API, as renamed and removed through `/api/auth/passkeys/:id`."
+          },
+          "name": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 80,
+            "description": "What the person called it, such as the device it lives on."
+          },
+          "created_at": {
+            "type": "string",
+            "format": "date-time",
+            "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+            "description": "When it was registered."
+          },
+          "last_used_at": {
+            "anyOf": [
+              {
+                "type": "string",
+                "format": "date-time",
+                "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "When it last signed the person in or confirmed a sign-in, or `null` if never."
+          },
+          "synced": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Whether the authenticator reported the passkey as syncable across the person's devices (the backup-eligible flag), or `null` when it said nothing."
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "created_at",
+          "last_used_at",
+          "synced"
         ],
         "additionalProperties": false
       },
-      "datapoint-list-response": {
+      "developer-two-factor": {
         "type": "object",
         "properties": {
-          "datapoints": {
+          "passkeys": {
             "type": "array",
             "items": {
               "type": "object",
               "properties": {
-                "slug": {
+                "id": {
                   "type": "string",
-                  "minLength": 2,
-                  "maxLength": 63,
-                  "pattern": "^[a-z][a-z0-9]*(?:_[a-z0-9]+)*$",
-                  "description": "The name a client reads this datapoint by."
+                  "format": "uuid",
+                  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+                  "description": "The passkey in the API, as renamed and removed through `/api/auth/passkeys/:id`."
                 },
-                "builtin": {
-                  "type": "boolean",
-                  "description": "`true` for the datapoints every robot has — `bridge_state` and `robot_details` — and `false` for everything the published configuration adds."
+                "name": {
+                  "type": "string",
+                  "minLength": 1,
+                  "maxLength": 80,
+                  "description": "What the person called it, such as the device it lives on."
                 },
-                "unit": {
+                "created_at": {
+                  "type": "string",
+                  "format": "date-time",
+                  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+                  "description": "When it was registered."
+                },
+                "last_used_at": {
                   "anyOf": [
                     {
-                      "type": "string"
+                      "type": "string",
+                      "format": "date-time",
+                      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
                     },
                     {
                       "type": "null"
                     }
                   ],
-                  "description": "The unit the value carries **after** any scale and offset, shown beside the number so nobody has to guess whether `15` means percent, volts or minutes. `null` when the configuration names none."
+                  "description": "When it last signed the person in or confirmed a sign-in, or `null` if never."
                 },
-                "rate_throttle_hz": {
+                "synced": {
                   "anyOf": [
                     {
-                      "type": "number",
-                      "minimum": 0,
-                      "maximum": 20
+                      "type": "boolean"
                     },
                     {
                       "type": "null"
                     }
                   ],
-                  "description": "The ceiling on how often this datapoint is sent, in hertz. `null` means no ceiling is configured, which is also the answer for every built-in. A ceiling, not a clock: a slow topic stays slow and no value is repeated to manufacture a rate."
+                  "description": "Whether the authenticator reported the passkey as syncable across the person's devices (the backup-eligible flag), or `null` when it said nothing."
                 }
               },
               "required": [
-                "slug",
-                "builtin",
-                "unit",
-                "rate_throttle_hz"
+                "id",
+                "name",
+                "created_at",
+                "last_used_at",
+                "synced"
               ],
               "additionalProperties": false
             },
-            "description": "Everything a client may read on this robot: the two built-ins, plus every datapoint the published configuration exposes and the caller's role grants."
-          }
-        },
-        "required": [
-          "datapoints"
-        ],
-        "additionalProperties": false
-      },
-      "datapoint-value": {
-        "type": "object",
-        "properties": {
-          "slug": {
-            "type": "string",
-            "minLength": 2,
-            "maxLength": 63,
-            "pattern": "^[a-z][a-z0-9]*(?:_[a-z0-9]+)*$",
-            "description": "The datapoint this value belongs to."
+            "description": "Every passkey the caller has registered, oldest first. Empty when none."
           },
-          "value": {
-            "description": "The value, shaped by the datapoint: a number, a boolean, a string, or the whole ROS message where the configuration names no field inside it. Any `scale` and `offset` the configuration declares have already been applied, at the robot."
+          "authenticator": {
+            "anyOf": [
+              {
+                "type": "object",
+                "properties": {
+                  "created_at": {
+                    "type": "string",
+                    "format": "date-time",
+                    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+                    "description": "When the authenticator was confirmed."
+                  }
+                },
+                "required": [
+                  "created_at"
+                ],
+                "additionalProperties": false
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The confirmed authenticator app, or `null` when there is none. At most one."
           },
-          "timestamp_ms": {
+          "recovery_codes_left": {
             "type": "integer",
             "minimum": 0,
-            "maximum": 9007199254740991,
-            "description": "When the value was captured, as a unix timestamp in milliseconds. The **bridge's capture time**, never the time the cloud received it — the one exception is the built-in `bridge_state`, which the cloud observes by construction."
+            "maximum": 10,
+            "description": "How many of the ten recovery codes are unspent. `0` while the caller has no second factor."
+          },
+          "required_by_org": {
+            "type": "boolean",
+            "description": "Whether the organisation requires a second factor. While it does, the last one cannot be removed."
           }
         },
         "required": [
-          "slug",
-          "value",
-          "timestamp_ms"
+          "passkeys",
+          "authenticator",
+          "recovery_codes_left",
+          "required_by_org"
         ],
         "additionalProperties": false
       },
@@ -14200,65 +15504,6 @@
         ],
         "additionalProperties": false
       },
-      "feedback-request": {
-        "type": "object",
-        "properties": {
-          "kind": {
-            "type": "string",
-            "enum": [
-              "idea",
-              "problem",
-              "question",
-              "other"
-            ],
-            "description": "What the message is: an `idea`, a `problem`, a `question` or `other`. It only sorts the inbox; it changes nothing about how the message is handled."
-          },
-          "message": {
-            "type": "string",
-            "minLength": 1,
-            "maxLength": 5000,
-            "description": "What the developer wrote, trimmed. At most 5000 characters; a message that is only whitespace is refused."
-          },
-          "page": {
-            "type": "string",
-            "maxLength": 512,
-            "pattern": "^\\/.*",
-            "description": "The console path the message was sent from, e.g. `/robots/:id/jobs` with its real id. A path, never a full URL, so no host and no query string reach the inbox by accident."
-          }
-        },
-        "required": [
-          "kind",
-          "message",
-          "page"
-        ],
-        "additionalProperties": false
-      },
-      "feedback-response": {
-        "type": "object",
-        "properties": {
-          "id": {
-            "type": "string",
-            "format": "uuid",
-            "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-            "description": "The stored message. It exists whatever `mail` says."
-          },
-          "mail": {
-            "type": "string",
-            "enum": [
-              "sent",
-              "not_requested",
-              "not_configured",
-              "failed"
-            ],
-            "description": "What happened to the notification mail: `sent`, `failed`, or `not_configured` when this cloud has no feedback address. The message is stored in every case, so a client shows success for all three."
-          }
-        },
-        "required": [
-          "id",
-          "mail"
-        ],
-        "additionalProperties": false
-      },
       "fetch-types-request": {
         "type": "object",
         "properties": {
@@ -14479,6 +15724,27 @@
             ],
             "description": "The console powers this person holds. **Required** — every Fleetless user has a tier; it was optional only while the org also held people with no console powers to grade, and that pool is gone."
           },
+          "two_factor": {
+            "type": "object",
+            "properties": {
+              "passkeys": {
+                "type": "integer",
+                "minimum": 0,
+                "maximum": 9007199254740991,
+                "description": "How many passkeys the person has registered."
+              },
+              "authenticator": {
+                "type": "boolean",
+                "description": "Whether the person has a confirmed authenticator app."
+              }
+            },
+            "required": [
+              "passkeys",
+              "authenticator"
+            ],
+            "additionalProperties": false,
+            "description": "The person's second factors, as the team list shows them: none, passkeys, an authenticator, or both. No credential travels here. An owner resets them through `DELETE /api/org/users/:id/two-factor`."
+          },
           "created_at": {
             "type": "string",
             "format": "date-time",
@@ -14492,6 +15758,7 @@
           "email",
           "display_name",
           "tier",
+          "two_factor",
           "created_at"
         ],
         "additionalProperties": false
@@ -14543,6 +15810,27 @@
                   ],
                   "description": "The console powers this person holds. **Required** — every Fleetless user has a tier; it was optional only while the org also held people with no console powers to grade, and that pool is gone."
                 },
+                "two_factor": {
+                  "type": "object",
+                  "properties": {
+                    "passkeys": {
+                      "type": "integer",
+                      "minimum": 0,
+                      "maximum": 9007199254740991,
+                      "description": "How many passkeys the person has registered."
+                    },
+                    "authenticator": {
+                      "type": "boolean",
+                      "description": "Whether the person has a confirmed authenticator app."
+                    }
+                  },
+                  "required": [
+                    "passkeys",
+                    "authenticator"
+                  ],
+                  "additionalProperties": false,
+                  "description": "The person's second factors, as the team list shows them: none, passkeys, an authenticator, or both. No credential travels here. An owner resets them through `DELETE /api/org/users/:id/two-factor`."
+                },
                 "created_at": {
                   "type": "string",
                   "format": "date-time",
@@ -14556,6 +15844,7 @@
                 "email",
                 "display_name",
                 "tier",
+                "two_factor",
                 "created_at"
               ],
               "additionalProperties": false
@@ -15281,26 +16570,12 @@
                       "minLength": 1,
                       "maxLength": 200,
                       "description": "A display name taken at invoke time — the email for a Fleetless user or an app user, the key's own name for a server key. Storing it rather than joining is the point: renaming a key afterwards does not rewrite history."
-                    },
-                    "name": {
-                      "anyOf": [
-                        {
-                          "type": "string",
-                          "minLength": 1,
-                          "maxLength": 200
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "The person's display name when the job started: the Fleetless user's `display_name` for a developer, the app user's `display_name` for an app user. `null` for a server key, when the person had no name set, and for runs recorded before contracts 5.3.0. Show `label` when it is null."
                     }
                   },
                   "required": [
                     "kind",
                     "id",
-                    "label",
-                    "name"
+                    "label"
                   ],
                   "additionalProperties": false,
                   "description": "Who invoked the run, and what they were acting as at the time."
@@ -16479,37 +17754,6 @@
           "new_password"
         ]
       },
-      "password-reset-confirm": {
-        "type": "object",
-        "properties": {
-          "token": {
-            "type": "string",
-            "minLength": 1
-          },
-          "new_password": {
-            "type": "string",
-            "minLength": 12,
-            "maxLength": 256
-          }
-        },
-        "required": [
-          "token",
-          "new_password"
-        ]
-      },
-      "password-reset-request": {
-        "type": "object",
-        "properties": {
-          "email": {
-            "type": "string",
-            "format": "email",
-            "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
-          }
-        },
-        "required": [
-          "email"
-        ]
-      },
       "patch-app-oidc-provider-request": {
         "type": "object",
         "properties": {
@@ -16636,14 +17880,16 @@
         "type": "object",
         "properties": {
           "name": {
+            "description": "The organisation's new display name. Absent leaves it alone.",
             "type": "string",
             "minLength": 1,
             "maxLength": 120
+          },
+          "require_two_factor": {
+            "description": "Whether every member must have a second factor. Turning it on signs nobody out: each member without one sets it up at their next sign-in. Absent leaves it alone.",
+            "type": "boolean"
           }
         },
-        "required": [
-          "name"
-        ],
         "additionalProperties": false
       },
       "patch-org-response": {
@@ -16664,6 +17910,10 @@
                 "maxLength": 120,
                 "description": "The organisation's display name. Free text, changed through `PATCH /api/org`."
               },
+              "require_two_factor": {
+                "type": "boolean",
+                "description": "Whether every member must have a second factor — a passkey or an authenticator app. A member without one sets it up at their next sign-in, before any session exists; nobody is signed out when it is switched on. It covers the console and the central MCP endpoint; server keys and robot bridges are not people and are not affected. Owners change it through `PATCH /api/org`."
+              },
               "created_at": {
                 "type": "string",
                 "format": "date-time",
@@ -16674,6 +17924,7 @@
             "required": [
               "id",
               "name",
+              "require_two_factor",
               "created_at"
             ],
             "additionalProperties": false,
@@ -16865,29 +18116,37 @@
           "message"
         ]
       },
-      "put-app-auth-mcp-request": {
+      "put-app-auth-look-request": {
         "type": "object",
         "properties": {
-          "mcp_enabled": {
-            "type": "boolean",
-            "description": "Whether this app serves an MCP endpoint at `/mcp/<identifier>`. Off refuses the whole OAuth surface for the app, not merely the tool calls, and is re-read on every request rather than cached off a token."
-          },
-          "mcp_login_url": {
+          "hosted_accent": {
             "anyOf": [
               {
                 "type": "string",
-                "maxLength": 500
+                "pattern": "^#[0-9a-f]{6}$"
               },
               {
                 "type": "null"
               }
             ],
-            "description": "The page an MCP authorization redirects to, with `{interaction}` where the interaction id goes. Not a token: the id names a pending request the server already holds, and the app authenticates the user itself before approving it."
+            "description": "The accent colour of the hosted pages, `#rrggbb` in lowercase, or `null` for the neutral shell's own."
           }
         },
         "required": [
-          "mcp_enabled",
-          "mcp_login_url"
+          "hosted_accent"
+        ],
+        "additionalProperties": false
+      },
+      "put-app-auth-mcp-request": {
+        "type": "object",
+        "properties": {
+          "mcp_enabled": {
+            "type": "boolean",
+            "description": "Whether this app serves an MCP endpoint at `/mcp/<identifier>`. Off refuses the whole OAuth surface for the app, not merely the tool calls, and is re-read on every request rather than cached off a token."
+          }
+        },
+        "required": [
+          "mcp_enabled"
         ],
         "additionalProperties": false
       },
@@ -16926,9 +18185,60 @@
         ],
         "additionalProperties": false
       },
+      "put-app-auth-sign-in-request": {
+        "type": "object",
+        "properties": {
+          "sign_in_methods": {
+            "type": "object",
+            "properties": {
+              "password": {
+                "type": "boolean",
+                "description": "Whether app users may sign in with a password. Off refuses `POST /api/client/login` with `method_not_allowed`, and registration and invitations then take no password."
+              },
+              "email_code": {
+                "type": "boolean",
+                "description": "Whether app users may sign in with a six-digit code mailed to them, valid ten minutes. A code needs no URL, so it works in local development and in an app with no web UI."
+              }
+            },
+            "required": [
+              "password",
+              "email_code"
+            ],
+            "additionalProperties": false,
+            "description": "Which sign-in methods the app offers: password, emailed code, or both — at least one. Identity providers stay on top of either. The default is password only."
+          },
+          "two_factor": {
+            "type": "string",
+            "enum": [
+              "off",
+              "optional",
+              "required"
+            ],
+            "description": "Whether the app asks for an authenticator code: `off` (the default), `optional` or `required`. A person with a confirmed authenticator is asked at every sign-in whatever the policy; a sign-in through an identity provider is never asked."
+          }
+        },
+        "required": [
+          "sign_in_methods",
+          "two_factor"
+        ],
+        "additionalProperties": false
+      },
       "put-app-auth-urls-request": {
         "type": "object",
         "properties": {
+          "app_url": {
+            "anyOf": [
+              {
+                "type": "string",
+                "maxLength": 500,
+                "format": "uri"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The app's own home page, linked as `Open <app>` when a hosted flow is done. `null` makes the hosted done page say `You can close this tab`."
+          },
           "invite_url": {
             "anyOf": [
               {
@@ -16939,7 +18249,7 @@
                 "type": "null"
               }
             ],
-            "description": "The page in the developer's app that accepts an invitation, with `{token}` where the token goes. `null` when unconfigured, and then an invitation still issues but `send_mail` is refused with `409 target_state_conflict` — there would be nowhere for the link to point."
+            "description": "The page in the developer's app that accepts an invitation, with `{token}` where the token goes. `null` means the hosted page in `hosted_pages` is used."
           },
           "verify_url": {
             "anyOf": [
@@ -16951,7 +18261,7 @@
                 "type": "null"
               }
             ],
-            "description": "The page that confirms a new address, with `{token}` where the token goes. Self-registration needs it: without a page to send people to, a registration would leave an account nobody can activate."
+            "description": "The page that confirms a new address, with `{token}` where the token goes. `null` means the hosted page in `hosted_pages` is used."
           },
           "reset_url": {
             "anyOf": [
@@ -16963,13 +18273,27 @@
                 "type": "null"
               }
             ],
-            "description": "The page that takes a new password, with `{token}` where the token goes."
+            "description": "The page that takes a new password, with `{token}` where the token goes. `null` means the hosted page in `hosted_pages` is used."
+          },
+          "mcp_login_url": {
+            "anyOf": [
+              {
+                "type": "string",
+                "maxLength": 500
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The page an MCP authorization redirects to, with `{interaction}` where the interaction id goes. Not a token: the id names a pending request the server already holds, and the app authenticates the user itself before approving it. `null` means the hosted MCP sign-in in `hosted_pages` is used."
           }
         },
         "required": [
+          "app_url",
           "invite_url",
           "verify_url",
-          "reset_url"
+          "reset_url",
+          "mcp_login_url"
         ],
         "additionalProperties": false
       },
@@ -17101,6 +18425,25 @@
         ],
         "additionalProperties": false
       },
+      "recovery-codes-response": {
+        "type": "object",
+        "properties": {
+          "recovery_codes": {
+            "minItems": 10,
+            "maxItems": 10,
+            "type": "array",
+            "items": {
+              "type": "string",
+              "pattern": "^[a-z2-7]{5}-[a-z2-7]{5}$"
+            },
+            "description": "The ten new recovery codes, lowercase, shown once. Every earlier code is void."
+          }
+        },
+        "required": [
+          "recovery_codes"
+        ],
+        "additionalProperties": false
+      },
       "refresh-request": {
         "type": "object",
         "properties": {
@@ -17113,6 +18456,21 @@
           "refresh_token"
         ]
       },
+      "rename-passkey-request": {
+        "type": "object",
+        "properties": {
+          "name": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 80,
+            "description": "The new name."
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "additionalProperties": false
+      },
       "rename-slug-request": {
         "type": "object",
         "properties": {
@@ -17906,7 +19264,7 @@
           },
           "builtin": {
             "type": "boolean",
-            "description": "`true` for the two roles every app starts with. Their **rights may be re-scoped** exactly like a custom role's, through `PUT /api/apps/:id/roles/:roleId/permissions` — the flag exists so the console can explain where they came from, not to protect them. Built-in roles can be renamed and deleted like any other; the flag only records that the cloud seeded them."
+            "description": "`true` for the two roles every app starts with. Their **rights may be re-scoped** exactly like a custom role's, through `PUT /api/apps/:id/roles/:roleId/permissions` — the flag exists so the console can explain where they came from, not to protect them. It does not make them renamable or deletable — no route does that for any role."
           }
         },
         "required": [
@@ -17945,7 +19303,7 @@
                 },
                 "builtin": {
                   "type": "boolean",
-                  "description": "`true` for the two roles every app starts with. Their **rights may be re-scoped** exactly like a custom role's, through `PUT /api/apps/:id/roles/:roleId/permissions` — the flag exists so the console can explain where they came from, not to protect them. Built-in roles can be renamed and deleted like any other; the flag only records that the cloud seeded them."
+                  "description": "`true` for the two roles every app starts with. Their **rights may be re-scoped** exactly like a custom role's, through `PUT /api/apps/:id/roles/:roleId/permissions` — the flag exists so the console can explain where they came from, not to protect them. It does not make them renamable or deletable — no route does that for any role."
                 }
               },
               "required": [
@@ -18024,21 +19382,6 @@
           "capabilities"
         ]
       },
-      "role-rename-request": {
-        "type": "object",
-        "properties": {
-          "name": {
-            "type": "string",
-            "minLength": 1,
-            "maxLength": 60,
-            "description": "The new name, trimmed, 1 to 60 characters. Unique per app: another role of this app with the same name answers `409 role_name_taken`. The role's users keep it under its new name."
-          }
-        },
-        "required": [
-          "name"
-        ],
-        "additionalProperties": false
-      },
       "server-key-list-response": {
         "type": "object",
         "properties": {
@@ -18129,157 +19472,6 @@
         ],
         "additionalProperties": false
       },
-      "sign-up-request": {
-        "type": "object",
-        "properties": {
-          "org_name": {
-            "type": "string",
-            "minLength": 1,
-            "maxLength": 120
-          },
-          "email": {
-            "type": "string",
-            "format": "email",
-            "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
-          },
-          "password": {
-            "type": "string",
-            "minLength": 12,
-            "maxLength": 256
-          }
-        },
-        "required": [
-          "org_name",
-          "email",
-          "password"
-        ]
-      },
-      "sign-up-response": {
-        "type": "object",
-        "properties": {
-          "org": {
-            "type": "object",
-            "properties": {
-              "id": {
-                "type": "string",
-                "format": "uuid",
-                "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-                "description": "The organisation. Every developer route is scoped to the caller's org already, so a client rarely has to send this anywhere."
-              },
-              "name": {
-                "type": "string",
-                "minLength": 1,
-                "maxLength": 120,
-                "description": "The organisation's display name. Free text, changed through `PATCH /api/org`."
-              },
-              "created_at": {
-                "type": "string",
-                "format": "date-time",
-                "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-                "description": "When the organisation was created, as an ISO 8601 timestamp."
-              }
-            },
-            "required": [
-              "id",
-              "name",
-              "created_at"
-            ],
-            "additionalProperties": false
-          },
-          "user": {
-            "type": "object",
-            "properties": {
-              "id": {
-                "type": "string",
-                "format": "uuid",
-                "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-                "description": "The Fleetless user in the API, assigned by the cloud and stable for the life of the account."
-              },
-              "org_id": {
-                "type": "string",
-                "format": "uuid",
-                "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-                "description": "The organisation this person belongs to. Every developer route is already scoped to the caller's org, so this confirms what a client is looking at, not a filter it applies."
-              },
-              "email": {
-                "type": "string",
-                "format": "email",
-                "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-                "description": "The address the account is identified by, **globally unique** across every organisation. Immutable after creation: it is what every invitation, reset link and audit line names."
-              },
-              "display_name": {
-                "anyOf": [
-                  {
-                    "type": "string",
-                    "minLength": 1,
-                    "maxLength": 120
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Optional human name, shown by the console instead of the address where present. Self-service through `PATCH /api/auth/me`; never used for authentication. `null` when the person never supplied one."
-              },
-              "tier": {
-                "type": "string",
-                "enum": [
-                  "owner",
-                  "developer"
-                ],
-                "description": "The console powers this person holds. **Required** — every Fleetless user has a tier; it was optional only while the org also held people with no console powers to grade, and that pool is gone."
-              },
-              "created_at": {
-                "type": "string",
-                "format": "date-time",
-                "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-                "description": "When the account was created, as an ISO 8601 timestamp."
-              }
-            },
-            "required": [
-              "id",
-              "org_id",
-              "email",
-              "display_name",
-              "tier",
-              "created_at"
-            ],
-            "additionalProperties": false
-          },
-          "tokens": {
-            "type": "object",
-            "properties": {
-              "access_token": {
-                "type": "string",
-                "minLength": 1,
-                "description": "The token to send as `Authorization: Bearer <token>` on every call. Short-lived: read `expires_in` rather than assuming a lifetime."
-              },
-              "refresh_token": {
-                "type": "string",
-                "minLength": 1,
-                "description": "The token that buys the next access token. It rotates on every use, so a value presented twice is detectable theft and ends the whole family."
-              },
-              "expires_in": {
-                "type": "integer",
-                "exclusiveMinimum": 0,
-                "maximum": 9007199254740991,
-                "description": "How long the access token stays valid, in **seconds** from now. Not a timestamp, and not milliseconds."
-              }
-            },
-            "required": [
-              "access_token",
-              "refresh_token",
-              "expires_in"
-            ],
-            "additionalProperties": false
-          }
-        },
-        "required": [
-          "org",
-          "user",
-          "tokens"
-        ],
-        "additionalProperties": false
-      },
       "slug-usage-response": {
         "type": "object",
         "properties": {
@@ -18467,6 +19659,66 @@
         ],
         "additionalProperties": false
       },
+      "totp-confirm-request": {
+        "type": "object",
+        "properties": {
+          "code": {
+            "type": "string",
+            "pattern": "^\\d{6}$",
+            "description": "A code the new authenticator shows now. It proves the secret was copied correctly before anything depends on it."
+          }
+        },
+        "required": [
+          "code"
+        ],
+        "additionalProperties": false
+      },
+      "totp-confirm-response": {
+        "type": "object",
+        "properties": {
+          "recovery_codes": {
+            "anyOf": [
+              {
+                "minItems": 10,
+                "maxItems": 10,
+                "type": "array",
+                "items": {
+                  "type": "string",
+                  "pattern": "^[a-z2-7]{5}-[a-z2-7]{5}$"
+                }
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The ten recovery codes, shown once, when this is the account's first second factor; `null` otherwise."
+          }
+        },
+        "required": [
+          "recovery_codes"
+        ],
+        "additionalProperties": false
+      },
+      "two-factor-setup-response": {
+        "type": "object",
+        "properties": {
+          "secret": {
+            "type": "string",
+            "minLength": 1,
+            "description": "The shared secret, base32, for an authenticator app that cannot scan a QR code. Shown once; the cloud stores it encrypted."
+          },
+          "otpauth_url": {
+            "type": "string",
+            "pattern": "^otpauth:\\/\\/totp\\/.*",
+            "description": "The same secret as an `otpauth://totp/` URL, to render as a QR code. It carries the secret: never log it."
+          }
+        },
+        "required": [
+          "secret",
+          "otpauth_url"
+        ],
+        "additionalProperties": false
+      },
       "types-response": {
         "type": "object",
         "properties": {
@@ -18664,6 +19916,23 @@
         "required": [
           "email"
         ]
+      },
+      "webauthn-options-response": {
+        "type": "object",
+        "properties": {
+          "options": {
+            "type": "object",
+            "propertyNames": {
+              "type": "string"
+            },
+            "additionalProperties": {},
+            "description": "The `PublicKeyCredentialCreationOptionsJSON` or `PublicKeyCredentialRequestOptionsJSON` to pass to the browser. Its challenge is single-use and short-lived."
+          }
+        },
+        "required": [
+          "options"
+        ],
+        "additionalProperties": false
       }
     }
   }