@runlot/api 0.1.0-rc.97 → 0.1.0-rc.98

package/dist/schema.d.ts

@@ -1262,8 +1262,10 @@ export interface paths {
         get: operations["getDatabase"];
         put?: never;
         /**
-         * Create a database (called by `runlot deploy` when it reads a `\"database\": true` declaration)
-         * @description Creates the project's database and returns its connection details. Shortly afterwards
+         * Creates a new database after the previous one was deleted
+         * @description Every project has a database from the start; this creates a new, empty one after a
+         *     delete, and clears the turn-off so later deploys keep it. It returns the connection
+         *     details. Shortly afterwards
          *     the running worker picks up a connected `env.db`. No redeploy is needed.
          *
          *     **It is idempotent and never rotates the password.** A second call returns the same
@@ -1849,7 +1851,7 @@ export interface paths {
         get: operations["getStorage"];
         put?: never;
         /**
-         * Grant storage (called by `runlot deploy` when it reads a `\"storage\": true` declaration)
+         * Turns storage back on after it was turned off
          * @description **This is idempotent** — calling it twice leaves the prefix unchanged, so a retry can
          *     never move objects out of view.
          *
@@ -2066,12 +2068,12 @@ export interface paths {
         get: operations["getAI"];
         put?: never;
         /**
-         * Turns on AI (a deployment calls this after reading `"ai": true`)
+         * Turns AI back on after it was turned off
          * @description **This is idempotent.** There is no request body — neither the limits nor the model list is a
          *     value you set.
          *
-         *     Once it is on, `env.ai` is connected to the worker shortly afterwards. **Your project must
-         *     also declare `"ai": true`** in `runlot.json`, which is what makes the binding appear.
+         *     Every project has AI from the start; this is the way back after `DELETE`, and it clears the
+         *     turn-off so later deploys keep it. `env.ai` is attached from the next deployment.
          *
          *     Requires member or higher. Audited as `ai.grant`.
          */
@@ -2229,7 +2231,7 @@ export interface paths {
         get: operations["getEmail"];
         put?: never;
         /**
-         * Turns on email (a deployment calls this after reading `"email": true`)
+         * Turns email back on after it was turned off
          * @description **This is idempotent.** There is no request body — the address is derived
          *     (`<project>.<org>.<mail-domain>`), and the plan determines the limit. The address is
          *     fixed to the project name at the time of the grant.
@@ -2460,14 +2462,13 @@ export interface paths {
         get: operations["getAuth"];
         put?: never;
         /**
-         * Turns on auth (`runlot deploy` calls this after reading the `"auth": true` declaration)
+         * Turns login back on after it was turned off
          * @description **This is idempotent** — calling it twice leaves the settings and login providers
          *     unchanged. Auth is either on or off; there is no "on but disabled" state.
          *
          *     **A database is required.** Without one this returns 409 `database_required`, because
-         *     the end-user tables live inside the project's database. Declaring `"auth": true` also
-         *     enables the database, and a deploy grants them in that order, so you will not normally
-         *     see this error.
+         *     the end-user tables live inside the project's database. Every project has one unless it
+         *     was deleted, so you will see this only after a database delete.
          *
          *     Once enabled, the built-in login endpoints start serving shortly afterwards. As with
          *     `env.db` and `env.storage`, no redeploy is needed. Table initialization is idempotent,
@@ -4851,7 +4852,7 @@ export interface components {
         /** @description A deployment in the overview. Same shape as `Deployment`, including `actor`. */
         OverviewDeployment: components["schemas"]["Deployment"];
         OverviewDatabase: {
-            /** @description Whether `"database": true` is set in `runlot.json` */
+            /** @description Whether the project has a database. Every project has one unless it was deleted. */
             granted: boolean;
             /**
              * Format: date-time
@@ -4871,7 +4872,7 @@ export interface components {
              */
             generations: number;
         };
-        /** @description Which resources declared in `runlot.json` are enabled for this project. */
+        /** @description Which of the project's resources are on. Every one is on unless somebody turned it off. */
         OverviewFeatures: {
             database: boolean;
             storage: boolean;
@@ -11125,8 +11126,8 @@ export interface operations {
             403: components["responses"]["Forbidden"];
             404: components["responses"]["NotFound"];
             /**
-             * @description `database_required` — this project has no database.
-             *     Set `"database": true` in runlot.json and deploy.
+             * @description `database_required` — this project's database was deleted.
+             *     Create a new one with `POST …/database` (`runlot pg on`).
              */
             409: {
                 headers: {