@malloy-publisher/server 0.0.237 → 0.0.239

package/dist/app/api-doc.yaml

@@ -2,32 +2,43 @@ openapi: 3.1.0
 info:
   title: Malloy Publisher - Semantic Model Serving API
   description: |
-    The Malloy Publisher - Semantic Model Serving API provides comprehensive access to Malloy packages and their associated resources.
-    A Malloy package is a directory containing Malloy models (.malloy files), Malloy notebooks (.malloynb files), and embedded databases
-    (.parquet, .csv, and .xlsx files) with a malloy-publisher.json manifest at the package's root directory.
+    The Malloy Publisher - Semantic Model Serving API provides access to Malloy packages and everything they contain.
+    A Malloy package is a directory with a `publisher.json` manifest at its root, holding Malloy models (`.malloy` files),
+    notebooks (`.malloynb` files), embedded data (`.parquet`, `.csv`, and `.xlsx` files), and optionally an HTML data app
+    under `public/`.
 
     ## Key Features
 
-    - **Environment Management**: Create and manage environments with their associated packages and connections
-    - **Package Lifecycle**: Full CRUD operations for Malloy packages and their versions
-    - **Model & Notebook Access**: Retrieve and execute Malloy models and notebooks
-    - **Connection Management**: Secure database connection configuration and testing
-    - **Query Execution**: Execute queries against models and retrieve results
-    - **Watch Mode**: Real-time file watching for development workflows
+    - **Discovery**: List environments, packages, and the models, notebooks, pages, and data a package contains
+    - **Query Execution**: Run queries against models, execute notebooks a cell at a time, and compile-check Malloy without running it
+    - **Pages**: In-package HTML data apps served from a package's `public/` directory
+    - **Materializations**: Persist Malloy sources as tables, on a schedule or on demand
+    - **Connection Management**: Configure and test warehouse connections, and browse their schemas and tables
+    - **Watch Mode**: File watching, and a change-event stream for development workflows
 
     ## Resource Hierarchy
 
     The API follows a hierarchical resource structure:
     ```
-    Environments
-    ├── Connections
-    └── Packages
-        ├── Models
-        ├── Notebooks
-        └── Databases
+    Server
+    ├── /status, /theme               server state, and the UI theme
+    ├── /connections/test             validate a connection config
+    ├── /watch-mode/…                 development file watching
+    └── Environments
+        ├── Connections               schemas, tables, and ad-hoc SQL
+        └── Packages
+            ├── Models                query and compile
+            ├── Notebooks             execute a cell at a time
+            ├── Pages                 static HTML data apps from public/
+            ├── Databases             embedded data files
+            ├── Materializations      persisted sources
+            ├── Connections           package-scoped connection access
+            └── Events                SSE stream of file changes
     ```
 
-    For examples, see the Malloy samples packages (https://github.com/malloydata/malloy-samples) repository.
+    For worked examples, see the packages this server bundles
+    (https://github.com/malloydata/publisher/tree/main/examples); the package format is documented in
+    docs/packages.md (https://github.com/malloydata/publisher/blob/main/docs/packages.md).
   version: v0
 
 servers:
@@ -1861,7 +1872,12 @@ paths:
               - "false"
         - name: givens
           in: query
-          description: JSON-encoded given values keyed by given name
+          description:
+            A `GivenValues` object, JSON-encoded so it can travel in a query
+            string. Values are typed as `GivenValues` describes them, not
+            string-encoded as `EncodedGivenValues` would be. The parameter keeps
+            its name for compatibility; the schema it carries is the one named
+            here.
           required: false
           schema:
             type: string
@@ -2425,16 +2441,26 @@ components:
             $ref: "#/components/schemas/Error"
     PayloadTooLarge:
       description: |
-        The request was well-formed but the response exceeds a server-side
-        size cap. Two caps can fire:
-          * PUBLISHER_MAX_QUERY_ROWS (default 100000) — too many rows.
-          * PUBLISHER_MAX_RESPONSE_BYTES (default 50 MB) — JSON-serialized
-            response too large.
-        The error message identifies which cap fired. Refine the query (add
-        a LIMIT, more selective WHERE, project fewer columns) or raise the
-        relevant cap; retrying without changes will not succeed. The
-        per-cap rejection counter is exported as
-        publisher_query_cap_exceeded_total{cap_type, source}.
+        The request was well-formed but the response is too large to return.
+        Three cases, and the message says which:
+          * PUBLISHER_MAX_QUERY_ROWS (default 100000) exceeded: too many rows.
+          * PUBLISHER_MAX_RESPONSE_BYTES (default 50 MB) exceeded: the
+            JSON-serialized response measured over the cap. What is measured is
+            the shape the request asked for, so on the model-query endpoint two
+            requests differing only in compactJson reach this cap at different
+            result sizes.
+          * The response could not be serialized at all, past the JavaScript
+            engine's own limit (V8 refuses the string; JSC fails the
+            allocation). No cap was necessarily exceeded here, and raising one
+            does not help. This third case applies to the model-query and
+            notebook-cell endpoints; the connection SQL endpoints have no such
+            guard and answer 500.
+        In every case, refine the query (add a LIMIT, a more selective WHERE,
+        project fewer columns, or filter out wide values); retrying unchanged
+        will not succeed. Raising the relevant cap is an option for the first
+        two only. The rejection counter is exported as
+        publisher_query_cap_exceeded_total{cap_type, source}, where cap_type is
+        rows, bytes, or unserializable.
       content:
         application/json:
           schema:
@@ -2734,7 +2760,7 @@ components:
           default: package
           description: >-
             Package-level Malloy Persistence scope mode, declared once at the
-            malloy-publisher.json root and applied uniformly to every persist
+            publisher.json root and applied uniformly to every persist
             source and index in the package. `package` (the default) =
             persisted artifacts are package-scoped: reused across the package's
             published versions whenever they still satisfy freshness. `version`
@@ -2775,28 +2801,35 @@ components:
           type: array
           readOnly: true
           description: >-
-            Non-fatal render-tag findings collected when the package loaded: a
-            render annotation (e.g. `# big_value` or `# currency`) misconfigured
-            for the field it sits on, so it renders as "[object Object]" or an
-            inline error at query time but does not stop the model compiling or
-            the package loading. Server-computed and read-only: ignored on
-            create/update requests and only returned in responses. Present only
-            when there are such findings.
+            Non-fatal findings collected when the package loaded, none of which
+            stop the model compiling or the package loading. Render-tag
+            findings: a render annotation (e.g. `# big_value` or `# currency`)
+            misconfigured for the field it sits on, so it renders as
+            "[object Object]" or an inline error at query time. Materialization
+            findings: a `storage=` source not served from storage, a `#@ persist`
+            source that was not recognized as materializable, a persist-target
+            collision, and materialization-config problems that degrade
+            attribution. Server-computed and read-only: ignored on create/update
+            requests and only returned in responses. Present only when there are
+            such findings.
           items:
             type: object
             properties:
               model:
                 type: string
                 description: >-
-                  Package-relative path of the model the finding is on.
-              target:
+                  Package-relative path of the model the finding is on. Absent
+                  for a package-wide finding.
+              subject:
                 type: string
                 description: >-
-                  The query or view the finding sits on, e.g. `by_carrier` or
-                  `flights -> by_carrier`.
+                  What the finding is about: the query or view a render finding
+                  sits on (`by_carrier`, `flights -> by_carrier`), or the source
+                  a materialization finding belongs to. Absent when a finding
+                  spans several, in which case the message names them.
               message:
                 type: string
-                description: The render validator's description of the problem.
+                description: A description of the problem.
               severity:
                 type: string
                 enum:
@@ -2835,7 +2868,7 @@ components:
             - type: "null"
           description: |
             Package-level Malloy Persistence policy declared in
-            malloy-publisher.json. The control plane reads it to drive scheduled
+            publisher.json. The control plane reads it to drive scheduled
             re-materialization. The object is present whenever the package has
             loaded — with `schedule: null` when the manifest declares no
             schedule — so the caller can treat object-present as the
@@ -2921,7 +2954,7 @@ components:
     PackageMaterializationConfig:
       type: object
       description: >-
-        Package-level Malloy Persistence policy from malloy-publisher.json's
+        Package-level Malloy Persistence policy from publisher.json's
         `materialization` block. Surfaced verbatim so the control plane can drive
         scheduled version-level re-materialization without re-reading the package
         files. The object is emitted whenever the package is loaded, even when no
@@ -2967,7 +3000,7 @@ components:
     Freshness:
       type: object
       description: >-
-        Freshness policy declared in malloy-publisher.json's
+        Freshness policy declared in publisher.json's
         `materialization.freshness` block. Fields are surfaced verbatim;
         invalid values are dropped (reported as absent), never defaulted.
       properties:
@@ -3054,18 +3087,22 @@ components:
       type: object
       description: Raw Malloy notebook with unexecuted cell contents
       properties:
-        resource:
+        type:
           type: string
-          description: Resource path to the notebook
+          description: Always `notebook`. Distinguishes the payload from the
+            compiled-model shape returned by the model endpoint.
         packageName:
           type: string
           description: Name of the package containing this notebook
-        path:
+        modelPath:
           type: string
           description: Relative path to the notebook file within its package directory
         malloyVersion:
           type: string
           description: Version of the Malloy compiler used to generate the notebook data
+        modelInfo:
+          type: string
+          description: JSON string containing model metadata and structure information
         notebookCells:
           type: array
           description: Array of notebook cells containing raw markdown and code content
@@ -3076,11 +3113,23 @@ components:
           description: Array of file-level (##) annotations attached to the notebook
           items:
             type: string
+        startingGivens:
+          allOf:
+            - $ref: "#/components/schemas/EncodedGivenValues"
+          description:
+            Starting values for the notebook's controls, declared at its file
+            level. URL parameters override these, which is why the two share a
+            shape. Omitted when the notebook declares none.
         sources:
           type: array
           description: Sources defined in the notebook's model
           items:
             $ref: "#/components/schemas/Source"
+        queries:
+          type: array
+          description: Named queries defined in the notebook's model
+          items:
+            $ref: "#/components/schemas/Query"
 
     CompiledModel:
       type: object
@@ -3193,10 +3242,22 @@ components:
 
     Given:
       type: object
-      description:
+      description: |
         A given (runtime parameter) declared on a Malloy model via the
         `given:` keyword. Surfaced on `CompiledModel.givens` and `Source.givens`
         so callers can introspect what runtime values a model accepts.
+
+        `givens` always names a collection of these declarations. Values keyed
+        by given name are `GivenValues` (or `EncodedGivenValues` in the form
+        that survives a URL), and a bare list of names is spelled `givenNames`.
+
+        It also carries how the given should be presented as an input control
+        (`label`, `control`, `rangeMin`, `rangeMax`, `suggest`), derived from
+        the declaration's own tags. That contract belongs to the given rather
+        than to any one surface, which is what lets a notebook and an SDK host
+        render the same control without restating it. Those five fields describe
+        the contract a renderer implements; no endpoint populates them yet, so
+        they are absent from every response today.
       properties:
         name:
           type: string
@@ -3217,15 +3278,85 @@ components:
             the model. Omitted when the given declares no default. Consumers
             render or prefill it per the given's `type` (e.g. unquote a string
             literal for a text input).
+        label:
+          type: string
+          description: Display label from the declaration's `# label=` tag
+        control:
+          type: string
+          enum:
+            - select
+            - multiselect
+          description:
+            How the control renders when the choice is between a single-pick and
+            a multi-pick list. Omitted means infer from the given's type. A
+            slider is not one of these values; it is signalled by `rangeMin` and
+            `rangeMax` instead, per the rule on those fields.
+        rangeMin:
+          type: number
+          description:
+            Slider lower bound from `# range_min=`. The two bounds are what
+            signal a slider, so a `number` or `filter<number>` given renders as
+            one when BOTH are present and as a plain number input otherwise, so
+            a lone bound changes nothing about the control.
+        rangeMax:
+          type: number
+          description:
+            Slider upper bound from `# range_max=`. See `rangeMin` for the rule
+            that turns the pair into a slider.
+        suggest:
+          $ref: "#/components/schemas/GivenSuggest"
+
+    GivenSuggest:
+      type: object
+      description: |
+        Where a select or multiselect control gets its options: a named `query`,
+        a `source` + `dimension` pair, or a `query` with a `dimension` naming
+        which of its columns to read. All three run through the ordinary query
+        endpoint.
+
+        With `query` alone the first column of each row is used, so a
+        single-column `group_by` needs no `dimension`. Give `dimension`
+        alongside `query` when the query returns more than one column.
+      properties:
+        query:
+          type: string
+        source:
+          type: string
+        dimension:
+          type: string
 
-    Givens:
+    GivenValues:
       type: object
-      description: Per-query given values that override model defaults. Keys are
-        given names declared in the model's `given:` block. Values must match
-        the declared type (string, number, boolean, date, etc.). See Malloy
-        givens documentation for accepted value shapes.
+      description: |
+        Given *values* keyed by given name: what a caller sends, as distinct
+        from `Given`, which describes what the model *accepts*. A collection of
+        declarations is a plain array of `Given`, never this.
+
+        Values are decoded and must match the declared type: a `number` given
+        takes a JSON number, a `date` takes a bare `YYYY-MM-DD` string, a
+        `timestamp` an ISO string with no zone, a `timestamptz` a full ISO
+        string. `EncodedGivenValues` is the string-encoded counterpart.
       additionalProperties: true
 
+    EncodedGivenValues:
+      type: object
+      description: |
+        The same values as `GivenValues`, string-encoded: the form that survives
+        a URL. Every value is a string regardless of the given's declared type,
+        and a `filter<…>` value is the filter body rather than the `f'…'`
+        literal.
+
+        The role it names: a surface's URL parameters and the starting values a
+        document declares share this shape, so the two can merge and then be
+        decoded once against the declarations and sent as `GivenValues`. No
+        endpoint returns it yet. `RawNotebook.startingGivens` is the first field
+        typed as it, and nothing populates that field so far, so today this
+        schema documents the contract rather than describing live traffic. The
+        `givens` query parameter is not an instance of it: that carries a
+        JSON-encoded `GivenValues`, with values typed rather than stringified.
+      additionalProperties:
+        type: string
+
     Source:
       type: object
       description: A Malloy source defined in a model
@@ -3349,7 +3480,7 @@ components:
 
             When true, skip server-side `#(filter)` injection entirely.
         givens:
-          $ref: "#/components/schemas/Givens"
+          $ref: "#/components/schemas/GivenValues"
         queryMetadata:
           $ref: "#/components/schemas/QueryMetadata"
           description: >-
@@ -4305,7 +4436,7 @@ components:
             (only available when compilation succeeds and the source contains a
             runnable query).
         givens:
-          $ref: "#/components/schemas/Givens"
+          $ref: "#/components/schemas/GivenValues"
       required:
         - source
 
@@ -4379,7 +4510,36 @@ components:
         forceRefresh:
           type: boolean
           default: false
-          description: Build a new table even when a source's sourceEntityId is unchanged.
+          description: >-
+            Build a new table even when a source's sourceEntityId is unchanged —
+            that is, defeat skip-if-unchanged, which would otherwise carry the
+            existing table forward and run no SQL for that source.
+
+            It means ONLY that. It never re-seeds a source declaring
+            `refresh="incremental"`: such a source is exempt from
+            skip-if-unchanged anyway (its content address does not move when its
+            data does), so there is nothing here for the flag to change, and
+            reading it as "rebuild from scratch" would make a forced run — which
+            is every scheduled fire — a full rebuild that no delta could ever
+            follow. Ask for a rebuild with `reseed`.
+
+            Has no effect at all on an orchestrated build: the host decides what
+            gets built by instructing it, so no carry-forward runs.
+        reseed:
+          type: boolean
+          default: false
+          description: >-
+            Rebuild every in-scope source declaring `refresh="incremental"` from
+            scratch, ignoring its recorded `covered_through` boundary, and
+            re-derive the boundary from the table each rebuild writes. The escape
+            hatch for a boundary or a table that is no longer trusted. Narrow it
+            with `sourceNames`.
+
+            Unlike `forceRefresh` this is about HOW an incremental source is
+            built, not whether it is built at all, which is why the two are
+            separate flags rather than one. An orchestrated caller can instead
+            set `reseed` per source on each BuildInstruction, and the two are
+            OR-ed: either asks for that source to rebuild.
         sourceNames:
           type: array
           items:
@@ -4548,9 +4708,15 @@ components:
         refresh:
           type: ["string", "null"]
           description: >-
-            The source's declared `#@ persist ... refresh=...` value
-            ("full" | "incremental"), reported verbatim; null = unset.
-            Metadata pass-through — inert to the publisher today.
+            The source's declared `#@ persist ... refresh=...` value, reported
+            verbatim; null = unset (which means "full"). Read and VALIDATED by
+            the publisher, no longer an inert pass-through: a value outside
+            {"full", "incremental"} is a publish rejection, and
+            `refresh="incremental"` additionally requires a `watermark=` naming
+            one output dimension (see `annotationFields`). An incremental source
+            advances its serving table by a bounded delta in place instead of
+            being rebuilt, so the mode also governs the build path — which is why
+            it is validated rather than passed through.
         freshness:
           oneOf:
             - $ref: "#/components/schemas/Freshness"
@@ -4586,12 +4752,37 @@ components:
           type: object
           additionalProperties:
             type: string
-          description:
+          description: >-
             All key=value fields of the source's `#@ persist` annotation (e.g.
             `name`, `realization`). The control plane uses `name` as the
             materialized table name (it may carry a dialect container path like
             `dataset.table`). Returned as the full set so new persist directives
-            need no publisher change.
+            need no publisher change; an unrecognized key rides through here and
+            is reported as a package warning, never a rejection.
+
+
+            Recognized keys beyond `name`/`realization`/`storage`, both read from
+            the EFFECTIVE merged tag (a source extending a persisted parent
+            inherits the parent's keys, and its own keys merge over them per key):
+
+
+            * `watermark` — one output dimension name, monotone non-decreasing.
+            Required by `refresh="incremental"`; the platform derives each
+            refresh's half-open range from it. Must be a single quoted string
+            naming a column of `columns`.
+
+
+            * `merge_key` — comma-separated output dimension names, none of them
+            the watermark. Declares row identity for a source whose rows are
+            restated with a LATER watermark value, which selects a MERGE apply;
+            omitted, the delta replaces the range instead. Compound keys go in one
+            quoted string (`merge_key="order_id, region"`).
+
+
+            Both are validated at publish against the compiled output schema, so
+            a dangling or stale name is rejected rather than deferred to a build.
+            Neither participates in `sourceEntityId`: adding a watermark to an
+            existing source must not re-address its table.
         modelPath:
           type: string
           description:
@@ -4709,6 +4900,26 @@ components:
             The name resolves generically against registered connections; any
             managed-tier alias is resolved by the host upstream and never
             reaches the publisher.
+        reseed:
+          type: boolean
+          default: false
+          description: >-
+            Rebuild this source from scratch even if it declares
+            `refresh="incremental"` and has a recorded `covered_through`
+            boundary: the build runs the ordinary full CTAS and the boundary is
+            re-derived from the table it writes. The escape hatch for a boundary
+            or a table that is no longer trusted.
+
+            Per-source rather than only per-request because re-seeding is a
+            per-source decision: a host may want one source rebuilt while the
+            rest advance by delta in the same run. OR-ed with the request-level
+            `reseed`, so either asks for this source to rebuild. Ignored for a
+            source that is not incremental (such a source is always built in
+            full).
+
+            Note `forceRefresh` is NOT how you ask for this, in any mode: it
+            only defeats skip-if-unchanged, which does not even run for an
+            orchestrated build.
 
     BuildManifest:
       type: object
@@ -4794,6 +5005,26 @@ components:
           description: >-
             Per-version read-time policy when the entry is stale. Never combined
             across versions; each version's entries carry its own declared fallback.
+        coveredThrough:
+          type: string
+          description: >-
+            For a source declaring `refresh="incremental"`, the EXCLUSIVE upper
+            end of the watermark range this table is now known to contain — the
+            boundary the next refresh will start from. Canonical scalar text
+            (`2024-07-01`, `2024-07-01 12:00:00`, `41`), interpreted per
+            `coveredThroughType`.
+
+            Reported so a caller can observe and verify incremental progress
+            rather than infer it: a value that advanced between runs is a delta
+            that applied. Absent for a non-incremental source, and for an
+            incremental one whose source is empty (no boundary is derivable, so
+            none is recorded).
+        coveredThroughType:
+          type: string
+          description: >-
+            The Malloy type of `coveredThrough` (`date`, `timestamp`, `number`,
+            `string`), which decides how its text is compared and rendered.
+            Present exactly when `coveredThrough` is.
 
   parameters:
     environmentName:

package/dist/app/assets/{EnvironmentPage-DaP6CpgK.js → EnvironmentPage-2oMC3DUO.js}

@@ -1 +1 @@
-import{$ as r,F as t,j as e,a0 as i,a9 as o}from"./index-BRijWj6K.js";function m(){const s=r(),{environmentName:n}=t();if(n){const a=i({environmentName:n});return e.jsx(o,{onSelectPackage:s,resourceUri:a})}else return e.jsx("div",{children:e.jsx("h2",{children:"Missing environment name"})})}export{m as default};
+import{$ as r,F as t,j as e,a0 as i,a9 as o}from"./index-ByceOJbS.js";function m(){const s=r(),{environmentName:n}=t();if(n){const a=i({environmentName:n});return e.jsx(o,{onSelectPackage:s,resourceUri:a})}else return e.jsx("div",{children:e.jsx("h2",{children:"Missing environment name"})})}export{m as default};

package/dist/app/assets/{HomePage-C9yNw3iu.js → HomePage-DmgHdpH6.js}

@@ -1 +1 @@
-import{$ as t,j as o,J as a}from"./index-BRijWj6K.js";function s(){const n=t();return o.jsx(a,{onClickEnvironment:n})}export{s as default};
+import{$ as t,j as o,J as a}from"./index-ByceOJbS.js";function s(){const n=t();return o.jsx(a,{onClickEnvironment:n})}export{s as default};

package/dist/app/assets/{LightMode-Be4-G-dX.js → LightMode-BNaG4oAx.js}

@@ -1 +1 @@
-import{c,j as s}from"./index-BRijWj6K.js";const t=c(s.jsx("path",{d:"M12 3c-4.97 0-9 4.03-9 9s4.03 9 9 9 9-4.03 9-9c0-.46-.04-.92-.1-1.36-.98 1.37-2.58 2.26-4.4 2.26-2.98 0-5.4-2.42-5.4-5.4 0-1.81.89-3.42 2.26-4.4-.44-.06-.9-.1-1.36-.1"})),a=c(s.jsx("path",{d:"M12 7c-2.76 0-5 2.24-5 5s2.24 5 5 5 5-2.24 5-5-2.24-5-5-5M2 13h2c.55 0 1-.45 1-1s-.45-1-1-1H2c-.55 0-1 .45-1 1s.45 1 1 1m18 0h2c.55 0 1-.45 1-1s-.45-1-1-1h-2c-.55 0-1 .45-1 1s.45 1 1 1M11 2v2c0 .55.45 1 1 1s1-.45 1-1V2c0-.55-.45-1-1-1s-1 .45-1 1m0 18v2c0 .55.45 1 1 1s1-.45 1-1v-2c0-.55-.45-1-1-1s-1 .45-1 1M5.99 4.58c-.39-.39-1.03-.39-1.41 0-.39.39-.39 1.03 0 1.41l1.06 1.06c.39.39 1.03.39 1.41 0s.39-1.03 0-1.41zm12.37 12.37c-.39-.39-1.03-.39-1.41 0-.39.39-.39 1.03 0 1.41l1.06 1.06c.39.39 1.03.39 1.41 0 .39-.39.39-1.03 0-1.41zm1.06-10.96c.39-.39.39-1.03 0-1.41-.39-.39-1.03-.39-1.41 0l-1.06 1.06c-.39.39-.39 1.03 0 1.41s1.03.39 1.41 0zM7.05 18.36c.39-.39.39-1.03 0-1.41-.39-.39-1.03-.39-1.41 0l-1.06 1.06c-.39.39-.39 1.03 0 1.41s1.03.39 1.41 0z"}));export{t as D,a as L};
+import{c,j as s}from"./index-ByceOJbS.js";const t=c(s.jsx("path",{d:"M12 3c-4.97 0-9 4.03-9 9s4.03 9 9 9 9-4.03 9-9c0-.46-.04-.92-.1-1.36-.98 1.37-2.58 2.26-4.4 2.26-2.98 0-5.4-2.42-5.4-5.4 0-1.81.89-3.42 2.26-4.4-.44-.06-.9-.1-1.36-.1"})),a=c(s.jsx("path",{d:"M12 7c-2.76 0-5 2.24-5 5s2.24 5 5 5 5-2.24 5-5-2.24-5-5-5M2 13h2c.55 0 1-.45 1-1s-.45-1-1-1H2c-.55 0-1 .45-1 1s.45 1 1 1m18 0h2c.55 0 1-.45 1-1s-.45-1-1-1h-2c-.55 0-1 .45-1 1s.45 1 1 1M11 2v2c0 .55.45 1 1 1s1-.45 1-1V2c0-.55-.45-1-1-1s-1 .45-1 1m0 18v2c0 .55.45 1 1 1s1-.45 1-1v-2c0-.55-.45-1-1-1s-1 .45-1 1M5.99 4.58c-.39-.39-1.03-.39-1.41 0-.39.39-.39 1.03 0 1.41l1.06 1.06c.39.39 1.03.39 1.41 0s.39-1.03 0-1.41zm12.37 12.37c-.39-.39-1.03-.39-1.41 0-.39.39-.39 1.03 0 1.41l1.06 1.06c.39.39 1.03.39 1.41 0 .39-.39.39-1.03 0-1.41zm1.06-10.96c.39-.39.39-1.03 0-1.41-.39-.39-1.03-.39-1.41 0l-1.06 1.06c-.39.39-.39 1.03 0 1.41s1.03.39 1.41 0zM7.05 18.36c.39-.39.39-1.03 0-1.41-.39-.39-1.03-.39-1.41 0l-1.06 1.06c-.39.39-.39 1.03 0 1.41s1.03.39 1.41 0z"}));export{t as D,a as L};