@malloy-publisher/server 0.9.6 → 0.9.8

package/dist/app/api-doc.yaml

@@ -65,12 +65,15 @@ tags:
       distribution
   - name: models
     description: Malloy model access and compilation operations
+  - name: reports
+    description:
+      Reports - any `.malloy` file in a package carrying an artifact tag,
+      wherever it lives, with a linear or grid layout - their listing,
+      manifests, and cells
   - name: notebooks
-    description: Malloy notebook access and execution operations
+    description: Deprecated aliases for the linear reports. Use the `reports` routes.
   - name: dashboards
-    description:
-      Discovery and manifests for `# artifact` dashboards - layout, tiles, and
-      the given specs behind their controls
+    description: Deprecated aliases for the grid reports. Use the `reports` routes.
   - name: data-apps
     description:
       In-package HTML data apps (static pages served from a package's public/
@@ -653,6 +656,10 @@ paths:
           $ref: "#/components/responses/NotFound"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -710,6 +717,10 @@ paths:
           $ref: "#/components/responses/NotFound"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -762,8 +773,12 @@ paths:
           $ref: "#/components/responses/Unauthorized"
         "404":
           $ref: "#/components/responses/NotFound"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -812,8 +827,12 @@ paths:
           $ref: "#/components/responses/Unauthorized"
         "404":
           $ref: "#/components/responses/NotFound"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -890,8 +909,12 @@ paths:
           $ref: "#/components/responses/NotFound"
         "413":
           $ref: "#/components/responses/PayloadTooLarge"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
         "504":
@@ -940,8 +963,12 @@ paths:
           $ref: "#/components/responses/Unauthorized"
         "404":
           $ref: "#/components/responses/NotFound"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -1008,6 +1035,10 @@ paths:
           $ref: "#/components/responses/NotFound"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -1070,6 +1101,10 @@ paths:
           $ref: "#/components/responses/NotFound"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -1126,8 +1161,12 @@ paths:
           $ref: "#/components/responses/Unauthorized"
         "404":
           $ref: "#/components/responses/NotFound"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -1182,8 +1221,12 @@ paths:
           $ref: "#/components/responses/Unauthorized"
         "404":
           $ref: "#/components/responses/NotFound"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -1262,8 +1305,12 @@ paths:
           $ref: "#/components/responses/NotFound"
         "413":
           $ref: "#/components/responses/PayloadTooLarge"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
         "504":
@@ -1318,8 +1365,12 @@ paths:
           $ref: "#/components/responses/Unauthorized"
         "404":
           $ref: "#/components/responses/NotFound"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
         "500":
           $ref: "#/components/responses/InternalServerError"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
@@ -1587,11 +1638,10 @@ paths:
 
         On a package with a surface (a root `index.malloy`, or a legacy `explores`), only the
         files on that surface are listed, unless `includeHiddenFilesAndSources` is true. With it, every
-        model file is listed, and `isHidden` marks the ones the package hides. Dashboard files
-        are listed by the dashboards route either way. Served notebooks (a `.malloy` at the top of
-        `notebooks/` or `dashboards/` whose model-level `## artifact` tag says `kind=notebook`, or
-        names no `kind` and sits under `notebooks/`) are not models here, with or without a
-        surface; they are listed by list-notebooks.
+        model file is listed, and `isHidden` marks the ones the package hides. Reports (any
+        `.malloy` outside `public/` carrying an artifact tag, other than the root `index.malloy`;
+        see list-reports) are listed by list-reports. A grid report is not a model here on a
+        package with a surface; a linear report is not a model here with or without one.
       parameters:
         - name: environmentName
           in: path
@@ -1646,15 +1696,14 @@ paths:
         On a package with a surface (a root `index.malloy`, or a legacy `explores`), a file off
         that surface answers 404 with the same message a query to it gets, unless
         `includeHiddenFilesAndSources` is true. With it, the file is returned with its `sourceText`, whatever
-        sources the text names. Dashboard files and served notebooks (a `.malloy` at the top of
-        `notebooks/` or `dashboards/` whose model-level `## artifact` tag says `kind=notebook`, or
-        names no `kind` and sits under `notebooks/`) are always returned. A package with no surface, or with
+        sources the text names. Reports (see list-reports), wherever they live in the package,
+        are always returned. A package with no surface, or with
         `queryableSources: "all"`, returns every file. For a file it returns, `modelDef.contents` and `modelDef.exports`,
         `modelInfo`, `sources` and `sourceInfos` are limited to the names the file publishes, so
         the surface file does not carry the hidden sources it imports. A join to a hidden source
         keeps only its name and the names and types of its fields. `sourceText` is left out
         when the text names a source the file does not publish, unless
-        `includeHiddenFilesAndSources` is true; the text of a dashboard is always returned.
+        `includeHiddenFilesAndSources` is true; the text of a report is always returned.
       parameters:
         - name: environmentName
           in: path
@@ -1702,15 +1751,29 @@ paths:
       tags:
         - models
       operationId: update-model-source
-      summary: Write a dashboard or notebook file into the package
+      summary: Write a report file into the package
       description: |
-        Writes the Malloy text of a dashboard file — `dashboards/<slug>.malloy` —
-        or a notebook file — `notebooks/<slug>.malloy`, which must carry an
-        `## artifact` tag (an untagged file there is a shared include and is
-        refused with 400, and so is a write over an existing file that is
-        not a notebook) — the only paths this endpoint accepts,
-        into the package, and reloads the package in place so it is served from
-        the new text. This is the dashboard and notebook builder's save.
+        Writes the Malloy text of a report into the package, and reloads the
+        package in place so it is served from the new text. This is the report
+        builder's save. A report is any `.malloy` file carrying an artifact tag
+        (see list-reports), of either layout, wherever it lives in the package.
+
+        What it accepts:
+
+        - CREATE (no `expectedHash`): any `.malloy` path in the package that
+          does not exist yet, outside `public/`, and never the root
+          `index.malloy`. Missing directories are created, inside the package
+          root only. The text must carry an artifact tag (`## artifact`, or the
+          deprecated query-level `# artifact`): an `artifact` property anywhere
+          on a tag line, outside a string. Text without one is refused with 400.
+        - REPLACE (with `expectedHash`): only a file the package currently reads
+          as an editable report: a tagged `.malloy` report of either layout,
+          including a tagged grid report that has no tiles yet. A model, an
+          untagged file, a `.malloynb`, the root `index.malloy` and anything in
+          `public/` cannot be overwritten, wherever they live, and answer 400.
+
+        Two reports may share a basename in different directories; a report is
+        identified by its path, so a taken basename is not refused.
 
         The text is compiled first, as the file, and refused with its problems
         when it does not compile; nothing is written. The write is atomic (a
@@ -1728,21 +1791,16 @@ paths:
         merged: the caller re-opens and reapplies its change. Omit it to CREATE
         the file: a file that already exists is then refused with 409 too, so
         an unconditional overwrite is not something a caller can ask for by
-        leaving a field out. A notebook path over an existing file the package
-        does not serve as a notebook answers 400 instead, with or without a
-        hash, because that check comes before the hash. The check, the write,
+        leaving a field out. A path over an existing file the package does not
+        read as a report answers 400 instead, with or without a hash, because
+        that check comes before the hash. The check, the write,
         the reload and the restore all happen under one hold of the package
         lock, so two saves racing on one file cannot both pass the check, and a
         rollback cannot revert the other writer's text instead of its own.
 
-        A dashboard whose name (the file's basename) another file already holds
-        is refused with 409 before anything is written, since the name is its
-        URL and its `# drill` target. A `dashboards/` file whose text has no
-        `# artifact` or `## artifact` tag (an `artifact` property anywhere on a
-        tag line, outside a string) is refused with 400 before anything is
-        written; a tag only inside a block comment passes that check but the
-        compiled model carries none, so it is rolled back and answers 500. A
-        tagged dashboard with no tiles saves but is not served until it has one.
+        A tag only inside a block comment passes the tag check but the compiled
+        model carries none, so it is rolled back and answers 500. A tagged grid
+        report with no tiles saves but is not served until it has one.
 
         A create answers 201 and an update 200; `created` in the body says the
         same thing.
@@ -1765,7 +1823,7 @@ paths:
             type: string
         - name: path
           in: path
-          description: The file, `dashboards/<slug>.malloy` or `notebooks/<slug>.malloy`
+          description: The report file's path in the package, such as `sales/q3.malloy`
           required: true
           schema:
             $ref: "#/components/schemas/PathPattern"
@@ -1804,9 +1862,8 @@ paths:
           $ref: "#/components/responses/NotFound"
         "409":
           description:
-            The file changed since the caller opened it, already exists and
-            no `expectedHash` was sent, or is a dashboard whose name another
-            file already holds
+            The file changed since the caller opened it, or already exists and
+            no `expectedHash` was sent
           content:
             application/json:
               schema:
@@ -1884,6 +1941,10 @@ paths:
           $ref: "#/components/responses/InternalServerError"
         "501":
           $ref: "#/components/responses/NotImplemented"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
         "504":
@@ -1925,9 +1986,11 @@ paths:
         that is both gated and hidden from the caller answers 404 for the whole
         request, as it does without a document. In a document, problem positions
         are lines of the submitted text, problems carry no `model` tag, and
-        `includeSql` returns no `sql`. A tag that names no `kind` is a dashboard
-        when it lists `tiles` or carries a `dashboard { … }` grid tag, and a
-        notebook otherwise, since submitted text has no folder to take a kind from.
+        `includeSql` returns no `sql`. The document's `layout` follows the one
+        rule every report follows (see list-reports): the tag's `layout=`, else
+        its deprecated `kind=` (`dashboard` is grid, `notebook` is linear), else
+        grid when the tag lists `tiles` or carries a `dashboard { … }` grid tag,
+        else linear. Where a file lives never decides it.
       parameters:
         - name: environmentName
           in: path
@@ -1975,20 +2038,165 @@ paths:
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
 
+  /environments/{environmentName}/packages/{packageName}/reports:
+    get:
+      tags:
+        - reports
+      operationId: list-reports
+      summary: List package reports
+      description: |
+        Lists every report in the package, in path order. A report is a
+        `.malloy` file anywhere in the package, outside `public/`, that carries
+        an artifact tag: a model-level `## artifact`, or the deprecated
+        query-level `# artifact` on a `query:`. The package's root
+        `index.malloy` is never a report (it is the surface). A legacy
+        `.malloynb` is also a report, linear and read-only. Where a file lives
+        carries no meaning: `dashboards/` and `notebooks/` are ordinary
+        directory names. Everything else is an ordinary model, which a report
+        may import.
+
+        A report's `layout` is decided by its tags, first match wins: the
+        tag's `layout=` (`grid` or `linear`); else the deprecated `kind=`
+        (`dashboard` is grid, `notebook` is linear); else grid for a
+        query-level `# artifact`; else grid for a model-level tag that lists
+        `tiles` or carries a `dashboard { … }` grid tag; else linear.
+
+        A report is identified by its `path`. `name`, its basename, is a
+        display label only: two reports may share one.
+
+        Every report is listed whatever the package's surface; the surface
+        limits what its tiles and cells may read, not whether it is listed. A
+        report that failed to compile is listed with its `error`. A tagged grid
+        report with no tiles yet is not served and not listed.
+      parameters:
+        - name: environmentName
+          in: path
+          description: Name of the environment
+          required: true
+          schema:
+            $ref: "#/components/schemas/IdentifierPattern"
+        - name: packageName
+          in: path
+          description: Name of the package
+          required: true
+          schema:
+            $ref: "#/components/schemas/IdentifierPattern"
+        - name: versionId
+          in: query
+          description: Version identifier for the package
+          required: false
+          schema:
+            $ref: "#/components/schemas/VersionIdPattern"
+      responses:
+        "200":
+          description: The reports in the package
+          content:
+            application/json:
+              schema:
+                type: array
+                items:
+                  $ref: "#/components/schemas/Report"
+        "401":
+          $ref: "#/components/responses/Unauthorized"
+        "404":
+          $ref: "#/components/responses/NotFound"
+        "500":
+          $ref: "#/components/responses/InternalServerError"
+        "501":
+          $ref: "#/components/responses/NotImplemented"
+        "503":
+          $ref: "#/components/responses/ServiceUnavailable"
+
+  /environments/{environmentName}/packages/{packageName}/reports/{path}:
+    get:
+      tags:
+        - reports
+      operationId: get-report
+      summary: Get a report manifest
+      description: |
+        Everything a viewer needs to render one report, addressed by its path in
+        the package, including its extension, exactly as list-reports gives
+        it (`sales/q3.malloy`). A report written as tiles, of either layout, carries the
+        manifest fields (`tiles` or `query`, `dashboardColumns`,
+        `startingGivens`, `autorun`, `givens`): its tiles run through the model
+        query endpoint with `givens`, using `path` as the model. A linear
+        report written as `run:` cells, or a `.malloynb`, carries `notebook`
+        instead: its cells as get-notebook returned them. A `.malloy` report's
+        cells run through the model query endpoint, each cell's `text` as
+        `query` and `path` as the model; a `.malloynb`'s through the
+        deprecated execute-notebook-cell.
+      parameters:
+        - name: environmentName
+          in: path
+          description: Name of the environment
+          required: true
+          schema:
+            $ref: "#/components/schemas/IdentifierPattern"
+        - name: packageName
+          in: path
+          description: Name of the package
+          required: true
+          schema:
+            $ref: "#/components/schemas/IdentifierPattern"
+        - name: path
+          in: path
+          description: >-
+            The report's path within the package, including `.malloy` (or
+            `.malloynb`): the `path` list-reports returns.
+          required: true
+          schema:
+            type: string
+        - name: versionId
+          in: query
+          description: Version identifier for the package
+          required: false
+          schema:
+            $ref: "#/components/schemas/VersionIdPattern"
+      responses:
+        "200":
+          description: The report manifest
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/ReportManifest"
+        "401":
+          $ref: "#/components/responses/Unauthorized"
+        "404":
+          $ref: "#/components/responses/NotFound"
+        "500":
+          $ref: "#/components/responses/InternalServerError"
+        "501":
+          $ref: "#/components/responses/NotImplemented"
+        "503":
+          $ref: "#/components/responses/ServiceUnavailable"
+
+  # ── DEPRECATED ──────────────────────────────────────────────────────────
+  # The `…/dashboards*` and `…/notebooks*` routes, kept for clients that still
+  # read them, until a later release removes them. Use `…/reports*` above.
+  # Their schemas (`Dashboard`, `DashboardManifest`, `DashboardTile`,
+  # `Notebook`, `RawNotebook`) are in the deprecated section of the schemas;
+  # no report schema references them.
   /environments/{environmentName}/packages/{packageName}/dashboards:
     get:
       tags:
         - dashboards
       operationId: list-dashboards
-      summary: List package dashboards
+      deprecated: true
+      summary: List package dashboards (deprecated; use list-reports)
       description: |
-        Lists the dashboards in the specified package — every tagged `.malloy`
-        file at the top of `dashboards/` or `notebooks/` carrying an
-        `# artifact` (or model-level `## artifact`) annotation whose `kind` is
-        `dashboard`, or names none under `dashboards/`. A `kind=notebook` file is
-        listed as a notebook instead, whichever folder it sits in. A file with
-        no artifact tag is a shared include and is not listed, whether or not it
-        compiles.
+        **DEPRECATED**: use list-reports, which lists every report of either
+        layout by path. This route lists the package's grid reports (see
+        list-reports for what makes a file a report and which layout it has),
+        wherever they live in the package. Two may share a `name`; their `path`
+        tells them apart. A file with no artifact tag is an ordinary model and is
+        not listed, whether or not it compiles.
+
+        **Contract change since reports.** This route used to list only
+        `.malloy` files directly under `dashboards/`, so every `name` was unique
+        and every `path` was `dashboards/<name>.malloy`. It now lists grid
+        reports from anywhere in the package (`sales/q3.malloy`,
+        `notebooks/x.malloy`, `a/b/c.malloy`), so `path` may have any depth and
+        `name` may repeat. Key on `path`.
 
         A tagged dashboard that failed to compile is listed carrying its
         `error` where that state can arise at all, so a broken dashboard is
@@ -2055,14 +2263,27 @@ paths:
       tags:
         - dashboards
       operationId: get-dashboard
-      summary: Get a dashboard manifest
+      deprecated: true
+      summary: Get a dashboard manifest (deprecated; use get-report)
       description: |
-        Retrieves everything a viewer needs to render one dashboard: the artifact
-        tag's declarations plus the control contract derived from the givens its
-        query references. Running the dashboard needs no further endpoint — its
+        **DEPRECATED**: use get-report, which addresses a report by its path.
+        Retrieves everything a viewer needs to render one grid report: the
+        artifact tag's declarations plus the control contract derived from the
+        givens its query references. Running it needs no further endpoint — its
         query, each tile, and each control's suggest query all run
         through the model query endpoint with `givens`, using the manifest's
         `path` as the model.
+
+        `dashboardName` is a basename, which is not an identity: it resolves
+        only when exactly one grid report in the package has it. When several
+        do, the answer is 409 naming every matching path; address the report
+        by path with get-report instead.
+
+        **Contract change since reports.** This route never answered 409
+        before: a dashboard lived directly under `dashboards/`, so its name was
+        unique. A grid report may now live anywhere, two may share a basename,
+        and a client of this route must handle 409. The match also covers grid
+        reports outside `dashboards/`.
       parameters:
         - name: environmentName
           in: path
@@ -2079,11 +2300,11 @@ paths:
         - name: dashboardName
           in: path
           description: >-
-            The dashboard's name: its filename basename. Conventionally letters,
+            The report's name: its filename basename. Conventionally letters,
             digits, "-" and "_", and a package is warned when one of its
-            dashboards falls outside that. It is NOT constrained to it, because
+            grid reports falls outside that. It is NOT constrained to it, because
             the name comes from a filename rather than being chosen: a file such
-            as `dashboards/v1.2.malloy` is served, and its published `resource`
+            as `v1.2.malloy` is served, and its published `resource`
             carries the name percent-encoded. Send it percent-encoded.
           required: true
           schema:
@@ -2106,6 +2327,14 @@ paths:
           $ref: "#/components/responses/Unauthorized"
         "404":
           $ref: "#/components/responses/NotFound"
+        "409":
+          description:
+            More than one grid report in the package has this basename. The
+            message names every matching path; use get-report with one.
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/Error"
         "500":
           $ref: "#/components/responses/InternalServerError"
         "501":
@@ -2118,14 +2347,20 @@ paths:
       tags:
         - notebooks
       operationId: list-notebooks
-      summary: List package notebooks
+      deprecated: true
+      summary: List package notebooks (deprecated; use list-reports)
       description: |
-        Retrieves a list of all Malloy notebooks within the specified package: every
-        `.malloynb` file, and every `.malloy` file at the top of `notebooks/` or `dashboards/`
-        whose model-level `## artifact` tag says `kind=notebook` (or names no `kind` and sits
-        under `notebooks/`). Each notebook entry includes the relative path,
-        package name, title, description, and any compilation or reading error. This endpoint
-        is useful for discovering available notebooks and checking their status.
+        **DEPRECATED**: use list-reports. Lists the package's linear reports (see
+        list-reports): every `.malloynb` file outside `public/`, and every tagged
+        `.malloy` report whose layout is linear, wherever it lives. Each entry
+        includes the relative path, package name, title, description, and any
+        compilation or reading error.
+
+        **Contract change since reports.** This route used to list `.malloy`
+        notebooks only directly under `notebooks/`. It now lists linear reports
+        from anywhere in the package, including `dashboards/` and nested
+        directories, and no longer lists a kindless tiled file in `notebooks/`,
+        which is now grid.
       parameters:
         - name: environmentName
           in: path
@@ -2170,13 +2405,14 @@ paths:
       tags:
         - notebooks
       operationId: get-notebook
-      summary: Get Malloy notebook cells
+      deprecated: true
+      summary: Get Malloy notebook cells (deprecated; use get-report)
       description: |
-        Retrieves a Malloy notebook with its raw cell contents (markdown and code).
-        Cell execution should be done separately via the execute-notebook-cell endpoint.
-        A served notebook (a `.malloy` at the top of `notebooks/` or `dashboards/` whose
-        model-level `## artifact` tag says `kind=notebook`, or names no `kind` and sits under
-        `notebooks/`) answers here as well as a `.malloynb`.
+        **DEPRECATED**: use get-report. Retrieves a linear report with its raw
+        cell contents (markdown and code). A `.malloy` report's cells run
+        through the model query endpoint (each cell's `text` as the query); a
+        `.malloynb`'s through execute-notebook-cell. A linear `.malloy`
+        report, wherever it lives, answers here as well as a `.malloynb`.
         On a package with a surface, the response shows only the sources the notebook may read.
       parameters:
         - name: environmentName
@@ -2224,13 +2460,19 @@ paths:
       tags:
         - notebooks
       operationId: execute-notebook-cell
-      summary: Execute a specific notebook cell
+      deprecated: true
+      summary: Execute a specific notebook cell (deprecated)
       description: |
-        Executes a specific cell in a Malloy notebook by index. For code cells, this compiles
-        and runs the Malloy code, returning query results and any new sources defined.
-        For markdown cells, this simply returns the cell content. A served notebook
-        (tagged `kind=notebook`, or untagged-kind under `notebooks/`) answers here as well as a
-        `.malloynb`.
+        **DEPRECATED**: removed with the other notebook routes. For a `.malloy`
+        report, run a cell through the model query endpoint instead: the
+        report's path as the model, the cell's `text` (from get-report) as
+        `query`, and `givens` in the body, which applies the same surface,
+        `#(authorize)` and row-level gates. A `.malloynb` has no other route.
+        Executes a specific cell in a linear report by index.
+        For code cells, this compiles and runs the Malloy code, returning query
+        results and any new sources defined. For markdown cells, this simply
+        returns the cell content. A linear `.malloy` report, wherever it lives,
+        answers here as well as a `.malloynb`.
 
         On a package with a surface (a root `index.malloy`, or a legacy `explores`) with
         `queryableSources` left at `"declared"`, a code cell may read only sources the surface
@@ -2328,6 +2570,10 @@ paths:
           $ref: "#/components/responses/InternalServerError"
         "501":
           $ref: "#/components/responses/NotImplemented"
+        "424":
+          $ref: "#/components/responses/ConnectionUnavailable"
+        "502":
+          $ref: "#/components/responses/DatabaseUnreachable"
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
         "504":
@@ -2869,6 +3115,31 @@ components:
         application/json:
           schema:
             $ref: "#/components/schemas/Error"
+    ConnectionUnavailable:
+      description: |
+        The connection is misconfigured, so the query never ran. `reason`
+        says how: CONNECTION_AUTH_FAILED (the database rejected the
+        connection's credentials) or CONNECTION_NOT_FOUND (the model names a
+        connection the environment does not have). The query is fine, and a
+        retry fails the same way until the connection is fixed. For
+        CONNECTION_AUTH_FAILED the body carries a fixed message, because the
+        driver's text can name a user; it is logged.
+      content:
+        application/json:
+          schema:
+            $ref: "#/components/schemas/Error"
+    DatabaseUnreachable:
+      description: |
+        The database connection failed. With `reason: CONNECTION_FAILED` the
+        connection is down: the database could not be reached (refused, reset, timed out,
+        or closed by the server), so the query never ran and a retry can
+        succeed. That reason is what marks the customer's database being down
+        rather than this server failing. The body carries a fixed message,
+        because the driver's text can name an internal host; it is logged.
+      content:
+        application/json:
+          schema:
+            $ref: "#/components/schemas/Error"
     GatewayTimeout:
       description: |
         The query exceeded the per-request wall-clock budget
@@ -3313,11 +3584,11 @@ components:
             paths relative to the package root. Only these models are listed
             via `listModels()`, and the surface is the union of their
             `export {}` closures. Every other .malloy file still compiles for
-            import/join resolution but is hidden. Notebooks and dashboards are
-            always listed regardless of this field, and a dashboard entry
-            needs no listing: a tagged dashboard listed here reads the surface
-            and adds nothing to it. An untagged file under `dashboards/` that
-            is listed is an ordinary surface file.
+            import/join resolution but is hidden. Reports are always listed
+            regardless of this field, and a report needs no listing: a report
+            listed here reads the surface and adds nothing to it, and the
+            package warns about it (`report-on-surface`). An untagged file
+            that is listed is an ordinary surface file, wherever it lives.
             DEPRECATED, still honored. Every non-empty value gets a load
             warning naming the replacement: a root `index.malloy` that imports
             the listed files and exports what they publish. `[]` is deprecated
@@ -3376,23 +3647,28 @@ components:
             `queryableSources: "declared"`, and a root file such as
             `Index.malloy` that differs from `index.malloy` only in case and
             so is ignored. A root `index.malloy` with no manifest keys gets no
-            warning. Dashboard findings: a
-            `dashboards/` file whose `# artifact` tag does not parse or does not
-            describe a dashboard, a tile or suggest query that does not resolve,
-            a `# drill` naming a destination that is not a dashboard, and a
-            tile, single query or filter suggest that reads a source the
-            surface does not export, so it won't load. Two dashboard findings are about Publisher rather
-            than about the package: one when a file carrying an artifact tag
-            could not be read and so is not served at all, and one when the lint
-            stops early, in which case the list must be read as incomplete
-            rather than as a clean package. Notebook findings: a `notebooks/`
-            file with an `## artifact` note whose cells could not be read, which
-            names the line and the fix and is reported with severity `error`,
-            because the notebook is served with that error instead of opening.
-            The same family carries findings on files under `notebooks/` and
-            `dashboards/`, each naming its line and the fix; they are computed
-            at discovery and are also returned by `/compile` at file and
-            package scope. Eight codes are `error` and fail `/compile`:
+            warning. Report findings (one lint pass per report, of either
+            layout, wherever it lives): a file whose artifact tag does not
+            parse or does not describe a report, a tile or suggest query that
+            does not resolve, a `# drill` naming a destination that is not a
+            report, and a tile, single query or filter suggest that reads a
+            source the surface does not export, so it won't load. A `# drill`
+            destination is a path from the package root (a bare name is a file
+            at the root); one that names no report is unresolved (`error`).
+            Curation findings: a root `index.malloy` carrying an artifact tag,
+            which is ignored (`index-is-not-a-report`, `error`); and a report
+            that `index.malloy` imports or `explores` lists
+            (`report-on-surface`, `warn`). Two report findings are about
+            Publisher rather than about the package: one when a file carrying
+            an artifact tag could not be read and so is not served at all, and
+            one when the lint stops early, in which case the list must be read
+            as incomplete rather than as a clean package. A linear report whose
+            cells could not be read gets a finding that names the line and the
+            fix and is reported with severity `error`, because it is served
+            with that error instead of opening. The per-file report findings
+            each name their line and the fix and carry a `code`; they are
+            computed at discovery and are also returned by `/compile` at file
+            and package scope. Eight codes are `error` and fail `/compile`:
             `notebook-statement-above-artifact` and `notebook-tag-above-artifact`
             (a statement or a tag above a served notebook's `## artifact`),
             `notebook-markdown-above-artifact` (a `(markdown)` annotation above
@@ -3403,9 +3679,18 @@ components:
             `notebook-markdown-attached-nowhere` (a `#(markdown)` annotation
             with no statement to take it), `notebook-artifact-unparsed` (an
             `## artifact` tag does not parse), and `notebook-cells-unreadable`
-            (the reader could not read a served notebook's cells). The rest are
-            `warn` (a mistyped `(markdown)` opener, a missing `kind=notebook`, a
-            block that never closes, and similar).
+            (the reader could not read a linear report's cells), plus
+            `report-kind-removed` (a tag that sets `kind=`, which is no longer
+            read, so the file is not a report; the finding names the `layout=`
+            to write) and `report-layout-unknown` (a `layout=` other than
+            `grid` or `linear`). The rest are `warn` (a mistyped `(markdown)`
+            opener, `report-layout-implicit` for a tag that names no layout and lists
+            no tiles, a block that never closes, and similar).
+            Deprecated-format findings, all `warn`: each `.malloynb` notebook
+            (`model` is its path), and each source a file declares deprecated
+            `#(filter)` annotations on (`model` is that file, `subject` the
+            source; a source that only inherits or imports a filter is not
+            reported). Both still load and run.
             Server-computed and read-only:
             ignored on
             create/update requests and only returned in responses. Present only
@@ -3496,8 +3781,8 @@ components:
                 description: >-
                   What the finding is about: the query or view a render finding
                   sits on (`by_carrier`, `flights -> by_carrier`), the source a
-                  materialization finding belongs to, or, for a dashboard
-                  finding, the dashboard's name or the `source.dimension` a
+                  materialization finding belongs to, or, for a report
+                  finding, the report's name or the `source.dimension` a
                   `# drill` is declared on. Absent when a finding sits on none
                   of those, either because it spans several, in which case the
                   message names them, or because it is about the lint itself
@@ -3505,13 +3790,33 @@ components:
               message:
                 type: string
                 description: A description of the problem.
+              code:
+                type: string
+                description: >-
+                  A stable identifier for the finding's family, for a client that
+                  acts on it rather than only showing it; absent for a family that
+                  has none yet. `deprecated-malloynb-notebook`: a `.malloynb`
+                  notebook, the deprecated cell format (one per file, `model`
+                  naming it). `deprecated-filter-annotation`: a source declaring
+                  deprecated `#(filter)` annotations (one per declaring source,
+                  `model` naming its file and `subject` the source).
+                  `report-name-ambiguous`: two or more grid reports share a
+                  basename, so the deprecated `GET …/dashboards/{name}` route
+                  answers 409 for it (one per name, `subject` naming it and the
+                  message every path; `warn`). The per-file
+                  report findings (`notebook-…`, `report-…`) and the report
+                  curation findings (`report-on-surface`,
+                  `index-is-not-a-report`). The message wording may change; the
+                  code does not.
               severity:
                 type: string
                 enum:
                   - error
                   - warn
                 description: >-
-                  Finding severity. Render-tag findings use both: `error` for
+                  Finding severity, `error` or `warn` and nothing else; a
+                  deprecated form that still loads (such as
+                  `deprecated-malloynb-notebook`) is `warn`. Render-tag findings use both: `error` for
                   a tag malformed for the field it sits on, which renders as
                   "[object Object]" or an inline error at query time, and `warn`
                   for one that is well-formed but inert where it sits and so is
@@ -4110,240 +4415,155 @@ components:
           type: string
           description: Error message if the model failed to compile or load
 
-    Notebook:
-      type: object
-      description: Malloy notebook metadata and status information
-      properties:
-        environmentName:
-          type: string
-          description: Name of the environment containing this notebook
-        packageName:
-          type: string
-          description: Name of the package containing this notebook
-        path:
-          type: string
-          description: Relative path to the notebook file within its package directory
-        title:
-          type: string
-          description:
-            Human title. For a `.malloynb`, resolved from its own `## title="…"`,
-            then its `#"` doc comment, then its first markdown heading. For a
-            `.malloy` notebook, from the `title` in its `## artifact` tag, then
-            the first line of the `"` notes above that tag, then its first
-            markdown heading when no prose precedes it. Absent when none of
-            those resolve, leaving the caller to show the path.
-        description:
-          type: string
-          description:
-            The notebook's doc comment, when it has one. For a `.malloy`
-            notebook that is the `"` notes above the `## artifact` line; prose
-            below it is a `##(markdown)` or `##|(markdown)` cell.
-        error:
-          type: string
-          description: Error message if the notebook failed to compile or load
-
-    Dashboard:
+    Report:
       type: object
+      required: [resource, packageName, path, name, layout, title, editable]
       description: |
-        A dashboard within a Malloy package: a self-contained `.malloy` file at
-        the top of the package's `dashboards/` or `notebooks/` directory carrying an `# artifact` (or
-        model-level `## artifact`) annotation. The list entry; see
-        DashboardManifest for the detail a viewer needs to render one.
+        One report in a package, as list-reports lists it: a `.malloy` file
+        whose model-level `## artifact` tag makes it one, wherever it lives
+        outside `public/`, or a `.malloynb`. See ReportManifest for the detail a viewer needs to render
+        one.
       properties:
         resource:
           type: string
-          description: Resource path to the dashboard
+          description: Resource path to the report (get-report)
         packageName:
           type: string
-          description: Name of the package containing this dashboard
+          description: Name of the package containing this report
+        path:
+          type: string
+          description: >-
+            The report's path within its package, such as `sales/q3.malloy`.
+            Its identity, and the only thing that addresses it.
         name:
           type: string
-          description:
-            The dashboard's slug — its filename basename. Addresses it in a URL
-            and as a `# drill` target.
-        path:
+          description: >-
+            The file's basename without its extension. A display label only:
+            two reports in different directories may share it.
+        layout:
           type: string
-          description:
-            Relative path to the dashboard file within its package directory
-            (`dashboards/<name>.malloy`)
+          enum: [grid, linear]
+          description: >-
+            How its tiles are placed: `linear` top to bottom, one column, or
+            `grid` by `columns`, `colspan` and `break`. Decided by its tags (see
+            list-reports), never by where the file lives.
         title:
           type: string
-          description:
-            Human title from the artifact tag, falling back to the file's `#"`
-            doc comment and then to the slug
+          description: >-
+            Human title: the artifact tag's `title`, else the first line of the
+            `"` notes above the tag, else,
+            for a linear report, its first markdown heading, else `name`.
         description:
           type: string
+          description: The report's doc comment, when it has one.
+        editable:
+          type: boolean
           description: >-
-            The file's unnamed `"` notes above the `## artifact` tag; when it
-            has none there, the ones below it (a legacy spot the lint flags). For
-            a dashboard whose tag sits on one query, that query's `#"` notes.
+            Whether the builder opens it as it is: false for a `.malloynb` and
+            for a linear report written as `run:` cells.
         error:
           type: string
-          description: Error message if the dashboard file failed to compile
+          description: >-
+            Error message when the report failed to compile, or its cells could
+            not be read.
 
-    DashboardManifest:
-      type: object
+    ReportManifest:
       description: |
-        Everything a viewer needs to render one dashboard: the artifact tag's
-        declarations plus the control contract derived from the givens its query
-        references. Running needs no dashboard-specific endpoint — the query,
-        each tile, and each control's suggest query all run through
-        the ordinary model query endpoint with `givens`.
+        A `Report` plus what a viewer needs to draw it. A report written as
+        tiles, of either layout, carries `tiles`, `dashboardColumns`,
+        `startingGivens`, `autorun` and `givens`, whose tiles and suggest
+        queries run through `POST …/models/{path}/query` with `givens`. A
+        linear report written as `run:` cells, or a `.malloynb`, carries
+        `notebook` instead.
+      allOf:
+        - $ref: "#/components/schemas/Report"
+        - type: object
+          properties:
+            tiles:
+              type: array
+              description: >-
+                The report's tiles, each run as its own query (or shown as text),
+                in order. Absent on a `run:`-cell report.
+              items:
+                $ref: "#/components/schemas/ReportTile"
+            dashboardColumns:
+              type: integer
+              description: >-
+                Grid width, from the `# dashboard {columns=N}` tag beside the
+                artifact tag. 1 on a linear report. Absent means the viewer's
+                default.
+            startingGivens:
+              allOf:
+                - $ref: "#/components/schemas/EncodedGivenValues"
+              description: >-
+                Starting values for controls, from the artifact tag. URL
+                parameters override these.
+            autorun:
+              type: boolean
+              description: >-
+                False batches control changes behind an Apply button instead of
+                re-running on every change. Defaults to true.
+            givens:
+              type: array
+              description: >-
+                The control row: one entry per given the report's tiles run with
+                (less a given only a source's gate reads, which a host injects),
+                widened to every given the entry file surfaces when a tile cannot be
+                resolved (see `ReportTile.givenNames`). `default` is the value the
+                query endpoint takes, not the Malloy literal: a `filter<…>` given
+                declared `f'West'` publishes `West`.
+              items:
+                $ref: "#/components/schemas/Given"
+            notebook:
+              allOf:
+                - $ref: "#/components/schemas/ReportCells"
+              description: >-
+                For a linear report written as `run:` cells, or a `.malloynb`: its
+                cells and model. Run a `.malloy`
+                report's cell through the model query endpoint, its `text` as
+                `query`; a `.malloynb`'s with execute-notebook-cell. Absent on a
+                report written as tiles, and on a
+                report that failed to compile.
+
+    ReportTile:
+      type: object
+      description: >-
+        One tile of a report. A `query` tile (the default) runs a query; a
+        `text` tile shows markdown and runs nothing, so a caller that runs a
+        report's tiles skips the ones with `kind` `text`.
       properties:
-        resource:
-          type: string
-          description: Resource path to the dashboard
-        packageName:
+        kind:
           type: string
-          description: Name of the package containing this dashboard
+          enum: [query, text]
+          description: >-
+            `query` runs `query` through the model query endpoint; `text` shows
+            `markdown`. Absent means `query`.
         name:
-          type: string
-          description:
-            The dashboard's slug — its filename basename. Addresses it in a URL
-            and as a `# drill` target.
-        path:
-          type: string
-          description: |
-            Relative path to the dashboard file within its package directory
-            (`dashboards/<name>.malloy`). This is also the model to POST to:
-            `query`, each tile, and each control's suggest query all run through
-            `POST /environments/{environmentName}/packages/{packageName}/models/{path}/query`
-            with `givens`, which is why there is no dashboard-specific run
-            endpoint.
-        title:
-          type: string
-          description:
-            Human title from the artifact tag, falling back to the file's `#"`
-            doc comment and then to the slug
-        description:
           type: string
           description: >-
-            The file's unnamed `"` notes above the `## artifact` tag; when it
-            has none there, the ones below it (a legacy spot the lint flags). For
-            a dashboard whose tag sits on one query, that query's `#"` notes.
-        error:
-          type: string
-          description: Error message if the dashboard file failed to compile
-        kind:
+            A text tile's name: the bare word in `tiles=[…]` and on its
+            `##|(markdown) name` block. Absent on a query tile.
+        markdown:
           type: string
-          enum: [dashboard, notebook]
           description: >-
-            What the document is, from the `kind` property of its artifact tag
-            (the folder only decides the default when the tag says nothing). A
-            `notebook` is laid out as one column: `dashboardColumns` is 1
-            whatever the file says. Always `dashboard` on
-            `GET …/dashboards/{dashboardName}`; a notebook's manifest is the
-            `dashboard` field of `GET …/notebooks/{path}`.
+            A text tile's body, the text of its `##|(markdown) name` block
+            without the opener. Empty when the file has no such block. Absent on
+            a query tile.
         query:
           type: string
           description: >-
-            Name of the tagged query whose single result IS the page. Set when the
-            `# artifact` tag sits on a `query:`; a dashboard authored the ordinary
-            way carries `tiles` instead and leaves this absent. A NAME rather than
-            an expression, so it goes in the `queryName` field of a
-            `POST …/models/{path}/query` body. A tile's `query` is the other shape
-            and is not interchangeable with this one; see `DashboardTile.query`.
-        tiles:
-          type: array
+            Absent on a text tile. The run expression exactly as written in `tiles=[…]`, for example
+            "orders -> by_month". An EXPRESSION rather than a name, so it goes in
+            the `query` field of a `POST …/models/{path}/query` body, prefixed
+            with `run:`.
+        restricted:
+          type: boolean
           description: >-
-            The dashboard's tiles, each run as its own query and combined into one
-            grid. This is how a dashboard is normally authored, and the only form
-            that can span sources. Absent when the `# artifact` tag sits on a
-            `query:` instead, in which case `query` is set.
-          items:
-            $ref: "#/components/schemas/DashboardTile"
-        dashboardColumns:
-          type: integer
-          description: >-
-            Grid width, from the `# dashboard {columns=N}` render tag beside the
-            artifact tag. One spelling wherever the artifact tag sits: Publisher
-            reads it at model level to lay out `tiles`, and `@malloydata/render`
-            reads the same tag off a tagged `query:`. Absent means the viewer's
-            default.
-        startingGivens:
-          allOf:
-            - $ref: "#/components/schemas/EncodedGivenValues"
-          description:
-            Per-dashboard starting values for controls, from the artifact tag.
-            URL parameters override these, which is why the two share a shape.
-        autorun:
-          type: boolean
-          description:
-            False batches control changes behind an Apply button instead of
-            re-running on every change. Defaults to true.
-        givens:
-          type: array
-          description: |
-            The control row. Normally one entry per given the dashboard runs
-            with: the union over `tiles` (less a given only a source's gate
-            reads, which a host injects rather than a viewer sets), or what `query` references when the tag
-            sits on a query, and which the entry file
-            can bind. The row widens to
-            every given the entry file surfaces when any tile is one discovery
-            cannot resolve, because that tile's givens are otherwise absent from
-            the row it filters by; see `DashboardTile.givenNames`. So an entry
-            here is always bindable, but on a widened row it is not necessarily
-            referenced by any tile. A given reachable only
-            through an import chain the entry file does not import itself
-            cannot be bound at query time, so no control is offered for it and
-            it stays at its default; that case is reported in the package's
-            `warnings` rather than represented here by an unusable entry. Plain
-            `Given`s, because the presentation a control takes is declared on
-            the given itself, so a dashboard and a notebook render the same
-            control for the same given, `#(description=…)` helper text
-            included.
-
-            ONE DELIBERATE DIVERGENCE from `Given` as the model surface sends
-            it: `default` here is the value the QUERY ENDPOINT takes, not the
-            Malloy source literal. A `filter<…>` given declared `f'West'`
-            publishes `West`. As the literal it could not be used as a default
-            at all, since sending it back verbatim matches zero rows silently,
-            with no error to search for. Only filter-typed givens are unwrapped,
-            so a plain string default that merely reads like `f'x'` is
-            untouched. `startingGivens` uses the same shape for the same reason.
-          items:
-            $ref: "#/components/schemas/Given"
-
-    DashboardTile:
-      type: object
-      description: >-
-        One tile of a dashboard. A `query` tile (the default) runs a query; a
-        `text` tile shows markdown and runs nothing, so a caller that runs a
-        dashboard's tiles skips the ones with `kind` `text`.
-      properties:
-        kind:
-          type: string
-          enum: [query, text]
-          description: >-
-            `query` runs `query` through the model query endpoint; `text` shows
-            `markdown`. Absent means `query`.
-        name:
-          type: string
-          description: >-
-            A text tile's name: the bare word in `tiles=[…]` and on its
-            `##|(markdown) name` block. Absent on a query tile.
-        markdown:
-          type: string
-          description: >-
-            A text tile's body, the text of its `##|(markdown) name` block
-            without the opener. Empty when the file has no such block. Absent on
-            a query tile.
-        query:
-          type: string
-          description: >-
-            Absent on a text tile. The run expression exactly as written in `tiles=[…]`, for example
-            "orders -> by_month". An EXPRESSION rather than a name, so it goes in
-            the `query` field of a `POST …/models/{path}/query` body, prefixed
-            with `run:`. Sending it in `queryName`, the field
-            `DashboardManifest.query` takes, is rejected.
-        restricted:
-          type: boolean
-          description: >-
-            Set on a tile of a compiled document (`CompileResult.document`) whose
-            source the caller may not read. The tile carries its `query` and
-            nothing derived from the source: no `givenNames`, no layout tags.
-        givenNames:
-          type: array
+            Set on a tile of a compiled document (`CompileResult.document`) whose
+            source the caller may not read. The tile carries its `query` and
+            nothing derived from the source: no `givenNames`, no layout tags.
+        givenNames:
+          type: array
           items:
             type: string
           description: |
@@ -4358,7 +4578,7 @@ components:
             could not resolve the tile (its expression neither compiles nor is
             a plain `source -> view` or named query the static walk reads), in
             which case send the whole control row. One such tile
-            widens `DashboardManifest.givens` to every given the entry file
+            widens `ReportManifest.givens` to every given the entry file
             surfaces, rather than the union over the resolvable tiles, so that
             the row actually contains the givens that tile filters by.
         label:
@@ -4397,43 +4617,11 @@ components:
             resolves for a `# dashboard` nest child, read the same way here so one
             view presents identically as a tile and as a nest.
 
-    DataApp:
-      type: object
-      description:
-        An in-package HTML data app within a Malloy package - a static page
-        served from the package's public/ directory
-      properties:
-        resource:
-          type: string
-          description:
-            Canonical URL to the served data app. Root-relative and does
-            NOT carry the /api/v0 prefix, because a data app is a static asset
-            served off the server root rather than an API resource.
-        packageName:
-          type: string
-          description: Name of the package containing this data app
-        path:
-          type: string
-          description: Relative path to the HTML file within its package directory
-        title:
-          type: string
-          description:
-            Title extracted from the file's <title> tag, or the path if
-            not present
-        fit:
-          type: string
-          enum:
-            - viewport
-          description:
-            Layout hint read from a <meta name="publisher:fit"> tag in the
-            page <head>. "viewport" tells the embedded viewer to fill the
-            available height instead of auto-sizing to the content height, for
-            full-screen apps like slide decks. Omitted for an ordinary
-            content-driven app, which keeps content-height auto-sizing.
-
-    RawNotebook:
+    ReportCells:
       type: object
-      description: Raw Malloy notebook with unexecuted cell contents
+      description: >-
+        A linear report written as cells, or a `.malloynb`: its cells, unexecuted,
+        and its model.
       properties:
         type:
           type: string
@@ -4450,9 +4638,8 @@ components:
           enum: ["malloynb", "malloy"]
           description:
             The file format the notebook is written in. `malloynb` is the
-            cell-separated format; `malloy` is a `.malloy` at the top of `notebooks/` or
-            `dashboards/` whose model-level `## artifact` tag says `kind=notebook` (or names no
-            `kind` and sits under `notebooks/`), whose cells are
+            cell-separated format; `malloy` is a linear `.malloy` report (see
+            list-reports), wherever it lives, whose cells are
             its statements and its floating `(markdown)` notes in file order.
         malloyVersion:
           type: string
@@ -4465,16 +4652,6 @@ components:
           description: Array of notebook cells containing raw markdown and code content
           items:
             $ref: "#/components/schemas/NotebookCell"
-        dashboard:
-          allOf:
-            - $ref: "#/components/schemas/DashboardManifest"
-          description: >-
-            The tile layout of a notebook written as one (`## artifact {
-            kind=notebook tiles=[…] }`), in the shape a dashboard has, with
-            `kind` `notebook` and one column. Absent on a notebook written as
-            cells. Its tiles run through the model query endpoint at
-            `modelPath`; `notebookCells` carries the same content as cells for
-            readers that do not draw a layout.
         annotations:
           type: array
           description:
@@ -4513,6 +4690,271 @@ components:
           items:
             $ref: "#/components/schemas/Query"
 
+    DataApp:
+      type: object
+      description:
+        An in-package HTML data app within a Malloy package - a static page
+        served from the package's public/ directory
+      properties:
+        resource:
+          type: string
+          description:
+            Canonical URL to the served data app. Root-relative and does
+            NOT carry the /api/v0 prefix, because a data app is a static asset
+            served off the server root rather than an API resource.
+        packageName:
+          type: string
+          description: Name of the package containing this data app
+        path:
+          type: string
+          description: Relative path to the HTML file within its package directory
+        title:
+          type: string
+          description:
+            Title extracted from the file's <title> tag, or the path if
+            not present
+        fit:
+          type: string
+          enum:
+            - viewport
+          description:
+            Layout hint read from a <meta name="publisher:fit"> tag in the
+            page <head>. "viewport" tells the embedded viewer to fill the
+            available height instead of auto-sizing to the content height, for
+            full-screen apps like slide decks. Omitted for an ordinary
+            content-driven app, which keeps content-height auto-sizing.
+
+    # ── DEPRECATED ────────────────────────────────────────────────────────
+    # The shapes of the deprecated `…/dashboards*` and `…/notebooks*` routes.
+    # No report schema references them; each removal deletes its block here.
+
+    Notebook:
+      type: object
+      deprecated: true
+      description: DEPRECATED, use `Report`. A linear report as the deprecated
+        list-notebooks route lists it.
+      properties:
+        environmentName:
+          type: string
+          description: Name of the environment containing this notebook
+        packageName:
+          type: string
+          description: Name of the package containing this notebook
+        path:
+          type: string
+          description: Relative path to the notebook file within its package directory
+        title:
+          type: string
+          description:
+            Human title. For a `.malloynb`, resolved from its own `## title="…"`,
+            then its `#"` doc comment, then its first markdown heading. For a
+            `.malloy` notebook, from the `title` in its `## artifact` tag, then
+            the first line of the `"` notes above that tag, then its first
+            markdown heading when no prose precedes it. Absent when none of
+            those resolve, leaving the caller to show the path.
+        description:
+          type: string
+          description:
+            The notebook's doc comment, when it has one. For a `.malloy`
+            notebook that is the `"` notes above the `## artifact` line; prose
+            below it is a `##(markdown)` or `##|(markdown)` cell.
+        error:
+          type: string
+          description: Error message if the notebook failed to compile or load
+
+    Dashboard:
+      type: object
+      deprecated: true
+      description: |
+        DEPRECATED: use `Report`. A grid report (see list-reports), as the
+        deprecated list-dashboards route lists it. The list entry; see
+        DashboardManifest for the detail a viewer needs to render one.
+      properties:
+        resource:
+          type: string
+          description: Resource path to the dashboard
+        packageName:
+          type: string
+          description: Name of the package containing this dashboard
+        name:
+          type: string
+          description: >-
+            The report's filename basename: a display label, and the segment of
+            the deprecated get-dashboard URL. Not an identity: two reports may
+            share it. A change since reports: it used to be unique within the
+            package (every dashboard was directly under `dashboards/`), and a
+            client that keyed a map on it must key on `path` instead.
+        path:
+          type: string
+          description:
+            Relative path to the report file within its package directory,
+            which is its identity
+        title:
+          type: string
+          description:
+            Human title from the artifact tag, falling back to the file's `#"`
+            doc comment and then to the slug
+        description:
+          type: string
+          description: >-
+            The file's unnamed `"` notes above the `## artifact` tag; when it
+            has none there, the ones below it (a legacy spot the lint flags). For
+            a dashboard whose tag sits on one query, that query's `#"` notes.
+        error:
+          type: string
+          description: Error message if the dashboard file failed to compile
+
+    DashboardManifest:
+      type: object
+      deprecated: true
+      description: |
+        DEPRECATED: use `ReportManifest`.
+        Everything a viewer needs to render one dashboard: the artifact tag's
+        declarations plus the control contract derived from the givens its query
+        references. Running needs no dashboard-specific endpoint — the query,
+        each tile, and each control's suggest query all run through
+        the ordinary model query endpoint with `givens`.
+      properties:
+        resource:
+          type: string
+          description: Resource path to the dashboard
+        packageName:
+          type: string
+          description: Name of the package containing this dashboard
+        name:
+          type: string
+          description: >-
+            The report's filename basename: a display label, and the segment of
+            the deprecated get-dashboard URL. Not an identity: two reports may
+            share it. A change since reports: it used to be unique within the
+            package (every dashboard was directly under `dashboards/`), and a
+            client that keyed a map on it must key on `path` instead.
+        path:
+          type: string
+          description: |
+            Relative path to the report file within its package directory,
+            which is its identity. This is also the model to POST to:
+            `query`, each tile, and each control's suggest query all run through
+            `POST /environments/{environmentName}/packages/{packageName}/models/{path}/query`
+            with `givens`, which is why there is no dashboard-specific run
+            endpoint.
+        title:
+          type: string
+          description:
+            Human title from the artifact tag, falling back to the file's `#"`
+            doc comment and then to the slug
+        description:
+          type: string
+          description: >-
+            The file's unnamed `"` notes above the `## artifact` tag; when it
+            has none there, the ones below it (a legacy spot the lint flags). For
+            a dashboard whose tag sits on one query, that query's `#"` notes.
+        error:
+          type: string
+          description: Error message if the dashboard file failed to compile
+        layout:
+          type: string
+          enum: [grid, linear]
+          description: >-
+            The report's layout (see list-reports). A `linear` report is laid
+            out as one column: `dashboardColumns` is 1 whatever the file says.
+        kind:
+          type: string
+          enum: [dashboard, notebook]
+          deprecated: true
+          description: >-
+            DEPRECATED: read `layout`. The same thing in the old vocabulary:
+            `dashboard` for a grid report, `notebook` for a linear one. Always
+            `dashboard` on `GET …/dashboards/{dashboardName}`; a linear
+            report's manifest is the `dashboard` field of
+            `GET …/notebooks/{path}`.
+        tiles:
+          type: array
+          description: >-
+            The dashboard's tiles, each run as its own query and combined into one
+            grid. Absent on a dashboard listed with its compile `error`.
+          items:
+            $ref: "#/components/schemas/DashboardTile"
+        dashboardColumns:
+          type: integer
+          description: >-
+            Grid width, from the `# dashboard {columns=N}` render tag beside the
+            artifact tag. One spelling wherever the artifact tag sits: Publisher
+            reads it at model level to lay out `tiles`, and `@malloydata/render`
+            reads the same tag off a tagged `query:`. Absent means the viewer's
+            default.
+        startingGivens:
+          allOf:
+            - $ref: "#/components/schemas/EncodedGivenValues"
+          description:
+            Per-dashboard starting values for controls, from the artifact tag.
+            URL parameters override these, which is why the two share a shape.
+        autorun:
+          type: boolean
+          description:
+            False batches control changes behind an Apply button instead of
+            re-running on every change. Defaults to true.
+        givens:
+          type: array
+          description: |
+            The control row. Normally one entry per given the dashboard runs
+            with: the union over `tiles` (less a given only a source's gate
+            reads, which a host injects rather than a viewer sets), or what `query` references when the tag
+            sits on a query, and which the entry file
+            can bind. The row widens to
+            every given the entry file surfaces when any tile is one discovery
+            cannot resolve, because that tile's givens are otherwise absent from
+            the row it filters by; see `DashboardTile.givenNames`. So an entry
+            here is always bindable, but on a widened row it is not necessarily
+            referenced by any tile. A given reachable only
+            through an import chain the entry file does not import itself
+            cannot be bound at query time, so no control is offered for it and
+            it stays at its default; that case is reported in the package's
+            `warnings` rather than represented here by an unusable entry. Plain
+            `Given`s, because the presentation a control takes is declared on
+            the given itself, so a dashboard and a notebook render the same
+            control for the same given, `#(description=…)` helper text
+            included.
+
+            ONE DELIBERATE DIVERGENCE from `Given` as the model surface sends
+            it: `default` here is the value the QUERY ENDPOINT takes, not the
+            Malloy source literal. A `filter<…>` given declared `f'West'`
+            publishes `West`. As the literal it could not be used as a default
+            at all, since sending it back verbatim matches zero rows silently,
+            with no error to search for. Only filter-typed givens are unwrapped,
+            so a plain string default that merely reads like `f'x'` is
+            untouched. `startingGivens` uses the same shape for the same reason.
+          items:
+            $ref: "#/components/schemas/Given"
+
+    DashboardTile:
+      deprecated: true
+      description: >-
+        DEPRECATED: `ReportTile`, under the name the deprecated dashboard
+        routes gave it.
+      allOf:
+        - $ref: "#/components/schemas/ReportTile"
+
+    RawNotebook:
+      deprecated: true
+      description: >-
+        DEPRECATED: `ReportCells`, as get-notebook answers them, plus the tile
+        layout of a linear report written as tiles.
+      allOf:
+        - $ref: "#/components/schemas/ReportCells"
+        - type: object
+          properties:
+            dashboard:
+              allOf:
+                - $ref: "#/components/schemas/DashboardManifest"
+              description: >-
+                The tile layout of a linear report written as one (`## artifact {
+                layout=linear tiles=[…] }`), in the shape a dashboard has, with
+                `layout` `linear` and one column. Absent on a notebook written as
+                cells. Its tiles run through the model query endpoint at
+                `modelPath`; `notebookCells` carries the same content as cells for
+                readers that do not draw a layout.
+
     CompiledModel:
       type: object
       description: Compiled Malloy model with sources, queries, and metadata
@@ -4890,7 +5332,9 @@ components:
           type: string
           description:
             Query string to execute on the model. If the query parameter is
-            set, the queryName parameter must be empty.
+            set, the queryName parameter must be empty. It may hold one run
+            statement, after any source or query definitions; text with more
+            than one run statement is a 400, since only the last would run.
         sourceName:
           type: string
           description: |
@@ -5704,8 +6148,7 @@ components:
           type: integer
           minimum: 1
           maximum: 2147483647
-          description:
-            Maximum run time of each statement on the database, in
+          description: Maximum run time of each statement on the database, in
             milliseconds. The database cancels a statement that exceeds it.
             When omitted, the database's own statement_timeout applies. Not
             applied to a DuckLake catalog connection.
@@ -5911,6 +6354,7 @@ components:
       required:
         - storage
         - catalog
+
     BigqueryConnection:
       type: object
       description: Google BigQuery database connection configuration
@@ -6077,11 +6521,13 @@ components:
     DuckdbConnection:
       type: object
       description: >
-        DuckDB database connection configuration. Exposes data-source intent,
-        attached foreign databases, and optional setup SQL for initialization
-        (e.g. ATTACH commands for external lakehouses), subject to Publisher policy
-        (setup SQL must be enabled with PUBLISHER_ALLOW_DUCKDB_SETUP_SQL=true and
-        is refused under EXTENSION_FETCH_POLICY=local-only).
+        DuckDB database connection configuration: attached foreign databases,
+        and optional setup SQL for anything they do not cover (e.g. ATTACH
+        commands for external lakehouses). Setup SQL must be enabled with
+        PUBLISHER_ALLOW_DUCKDB_SETUP_SQL=true and is refused under
+        EXTENSION_FETCH_POLICY=local-only. Database files, working directories,
+        filesystem/network policy, extension loading, temp directories, and
+        resource knobs remain owned by Publisher.
       properties:
         setupSQL:
           type: string
@@ -6089,7 +6535,11 @@ components:
             Optional initialization SQL script executed against the DuckDB
             session upon connection (e.g. ATTACH commands for external lakehouses).
             Multiple statements must be separated by a semicolon and newline (;\n).
-            Refused unless the deployment sets PUBLISHER_ALLOW_DUCKDB_SETUP_SQL=true.
+            Use absolute paths: a relative path resolves against the server's
+            working directory. Withheld from responses like a credential; an
+            update that omits it keeps the stored script, and an empty string
+            removes it. Refused unless the deployment sets
+            PUBLISHER_ALLOW_DUCKDB_SETUP_SQL=true.
         attachedDatabases:
           type: array
           items:
@@ -6122,6 +6572,7 @@ components:
         azureConnection:
           $ref: "#/components/schemas/AzureConnection"
     # TODO: What is this?  Can we remove it?
+
     SqlSource:
       type: object
       properties:
@@ -6199,12 +6650,28 @@ components:
             says nothing about whether the caller reached the right server; the
             latter is a routing problem worth retrying elsewhere.
 
+            CONNECTION_FAILED, on a 502, means the database could not be
+            reached (the connection was refused, reset or timed out, or the
+            server closed it), so the query never ran. The query and the model
+            are fine; retrying elsewhere will not help, and neither will
+            rewriting the query.
+
+            CONNECTION_AUTH_FAILED, on a 424, means the database rejected the
+            connection's credentials (a wrong password, an invalid key, an
+            expired token), so the query never ran. Whoever configures the
+            connection has to fix it; retrying fails the same way.
+
+            CONNECTION_NOT_FOUND, on a 424, means the model names a connection
+            the environment does not have, usually one deleted after the
+            package was loaded.
+
             Deliberately an open string rather than an enum. Generators render
             an enum closed, so adding a second value here would break every
             client generated before it -- on the one field whose purpose is to
             grow. Callers must treat an unrecognized value as absent.
 
-            Known values: TABLE_NOT_FOUND.
+            Known values: TABLE_NOT_FOUND, CONNECTION_FAILED,
+            CONNECTION_AUTH_FAILED, CONNECTION_NOT_FOUND.
         problems:
           type: array
           description: |
@@ -6314,10 +6781,16 @@ components:
             "package" runs the same worker compiler and file selection as
             reload over every .malloy and .malloynb file, without swapping the
             result into the served package; with a source, importers compile
-            against the replacement. Package diagnostics can name files hidden
-            from discovery. No rows or SQL are returned, and caller-provided
-            source remains subject to authorize gates. includeSql is not
-            available at "package".
+            against the replacement. It also reports the render-tag findings
+            (code "render-tag") and the dashboard, given and drill findings
+            (code "dashboard-lint") a reload would put on the package's
+            warnings, at their own severity and with no position. The
+            package's other warnings (storage, persist, materialization,
+            explores, surface and discovery warnings, among others) are not
+            reported. Package diagnostics can name
+            files hidden from discovery. No rows or SQL are returned, and
+            caller-provided source remains subject to authorize gates.
+            includeSql is not available at "package".
 
             "append" text is checked against the model's PUBLISHED surface, so
             it may not declare its own data roots: import, connection.table(…),
@@ -6422,13 +6895,20 @@ components:
         serves once saved. Present only when the source carries a model-level
         `## artifact` tag and compiled far enough to read.
       properties:
+        layout:
+          type: string
+          enum: [grid, linear]
+          description: >-
+            The report's layout, by the one rule every report follows: the
+            tag's `layout=`, else grid when it lists `tiles` or carries a
+            `dashboard { … }` grid tag, else linear.
         kind:
           type: string
           enum: [dashboard, notebook]
+          deprecated: true
           description: >-
-            From the tag's `kind`. When it names none, a document that lists
-            `tiles` or carries a `dashboard { … }` grid tag is a dashboard and
-            any other is a notebook: submitted text has no folder to decide.
+            DEPRECATED: read `layout`. The same thing in the old vocabulary:
+            `dashboard` for grid, `notebook` for linear.
         manifest:
           allOf:
             - $ref: "#/components/schemas/DashboardManifest"
@@ -6816,6 +7296,7 @@ components:
             The given names this term reads, in first-seen order. A reader must
             bind these for the term to apply; binding none applies each given's
             declared default, as a live query would.
+
     JoinedTerms:
       type: object
       required: [alias, source, terms]
@@ -6838,6 +7319,7 @@ components:
           description: >-
             The joined source's own stripped terms, which its binding re-applies
             with the caller's values.
+
     PersistSourcePlan:
       type: object
       required: [name, sourceID, connectionName, sourceEntityId, sql, columns]
@@ -7783,14 +8265,22 @@ components:
         file does not publish. That text can include `#(authorize)`
         expressions, `given:` defaults, connection names and raw SQL.
 
-        Only the models list, the model GET and the query route read it. The
-        notebook-cell route, the dashboards route, the MCP tools, and the legacy
-        `/projects/...` aliases of these routes ignore it.
+        Only the models list, the model GET and the query route read it, plus
+        the MCP `execute_query` tool's argument of the same name, which runs a
+        query the way this route does. MCP offers that argument only when
+        `publisher.config.json` sets `"mcp": { "includeHiddenFilesAndSources":
+        true }`, which is for authoring servers. Without it the argument is not
+        in the tool's schema and is ignored if sent, so an agent answering
+        questions stays on the curated surface.
+        This route is not affected by that setting. The notebook-cell route, the dashboards
+        route, the other MCP tools, and the legacy `/projects/...` aliases of
+        these routes ignore it.
 
         Like every route on this server, it is unauthenticated. A deployment
         that authenticates in front of Publisher decides who may send it, and
         should pass it only for callers allowed to work with a package's hidden
-        files, such as its authors.
+        files, such as its authors. A deployment that exposes the MCP port has
+        to make the same decision for the `execute_query` argument.
 
         Only `true` and `false` are accepted. Any other value is refused with
         400.