sqlrooms 0.1.0__tar.gz → 0.1.2__tar.gz

{sqlrooms-0.1.0 → sqlrooms-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sqlrooms
-Version: 0.1.0
+Version: 0.1.2
 Summary: Local-first SQLRooms project launcher for DuckDB worksheets and Mosaic dashboards.
 Project-URL: homepage, https://sqlrooms.com
 Project-URL: repository, https://github.com/sqlrooms/sqlrooms
@@ -18,7 +18,7 @@ Requires-Dist: fastapi>=0.115.0
 Requires-Dist: jinja2>=3.1.0
 Requires-Dist: pyarrow>=17.0.0
 Requires-Dist: python-multipart>=0.0.27
-Requires-Dist: sqlrooms-server>=0.1.1
+Requires-Dist: sqlrooms-server>=0.1.2
 Requires-Dist: tomli>=2.0.0; python_version < '3.11'
 Requires-Dist: tomlkit>=0.13.0
 Requires-Dist: typer>=0.12.5
@@ -40,27 +40,27 @@ Launch a local SQLRooms DuckDB project for adding data, authoring worksheets, an
 ## Quick start
 
 ```bash
-# From the repo root
-uvx sqlrooms \
-  ./sqlrooms.db
+uvx sqlrooms ./sqlrooms.db
 ```
 
 What happens:
 
 - Starts the DuckDB websocket backend (from `sqlrooms-server`) on a free local port.
-- Serves the SQLRooms worksheet UI on `http://localhost:4173`, or the next free port, and opens your browser (disable with `--no-open-browser`).
+- Serves the SQLRooms worksheet UI on `http://localhost:3000`, or the next free port, and opens your browser (disable with `--no-open-browser`).
 - Drag-and-drop CSV, TSV, JSON, Parquet, and DuckDB files to load them into DuckDB; files are uploaded to a local `sqlrooms_uploads` folder and referenced by path.
 - UI state is stored in the SQLRooms meta namespace (default `__sqlrooms`) of the selected DuckDB file.
 
 ## CLI flags
 
 - `DB_PATH` (positional): DuckDB project file to load/create (e.g. `sqlrooms ./my.db`). Required unless `--db-path` is provided.
+- `--version`: Print the installed `sqlrooms` CLI version and exit.
 - `--db-path`: DuckDB database to use as a flag alternative. Pass a filepath to persist, or `:memory:` for an explicit temporary in-memory session.
-- `--host` / `--port`: HTTP host/port for the UI. The default bind address is `127.0.0.1`. If `--port` is omitted, `4173` or the next free port is chosen automatically.
+- `--host` / `--port`: HTTP host/port for the UI. The default bind address is `127.0.0.1`. If `--port` is omitted, `3000` or the next free port is chosen automatically.
 - `--ws-port`: WebSocket port for DuckDB queries. If omitted, a free port is chosen automatically.
 - `--experimental`: Enable experimental artifacts, blocks, commands, and agent tools.
 - `--experimental-sync`: Enable experimental sync (CRDT) over WebSocket (Loro). Requires `--experimental`.
 - `--ai-devtools`: Enable the AI session devtools button in the UI, including production-built UI bundles. Can also be set with `SQLROOMS_AI_DEVTOOLS=1`.
+- `--debug`: Enable verbose debug logging, including HTTP access logs and DuckDB query timing.
 - `--meta-db`: Optional path to a dedicated DuckDB file for SQLRooms meta tables (UI state + CRDT snapshots). If omitted, meta tables are stored in the main DB.
 - `--meta-namespace` (default `__sqlrooms`): Namespace for SQLRooms meta tables. If `--meta-db` is provided, used as ATTACH alias; otherwise used as a schema in the main DB.
 - `--no-open-browser`: Skip automatically opening the browser tab.
@@ -90,10 +90,10 @@ Uploads go to `/api/upload`. Runtime config for the UI is exposed at `/api/confi
 
 ## Manual smoke test
 
-Use this before release candidates to prove the first-launch path:
+Use this to prove the first-launch path:
 
 ```bash
-uv run --project python --package sqlrooms sqlrooms \
+uvx sqlrooms \
   --no-open-browser \
   ./smoke.duckdb
 ```
@@ -101,7 +101,7 @@ uv run --project python --package sqlrooms sqlrooms \
 Then open the printed UI URL and verify:
 
 - The app starts without a database connection error.
-- Dragging `python/sqlrooms/tests/fixtures/cars.csv` into the data panel creates a `cars` table.
+- Dragging a small CSV file into the data panel creates a table.
 - The uploaded CSV lands next to `smoke.duckdb` under `sqlrooms_uploads/`.
 - The data sidebar shows `main.cars` and does not show SQLRooms internal metadata.
 - A worksheet is created or selected automatically and contains a `cars` data-table explorer block.
@@ -198,11 +198,10 @@ results into core DuckDB for downstream notebook cells.
 Install optional connector dependencies first:
 
 ```bash
-# From python/sqlrooms
-uv sync --extra connectors
+uv tool install "sqlrooms[connectors]"
 # or install just one connector:
-uv sync --extra postgres
-uv sync --extra snowflake
+uv tool install "sqlrooms[postgres]"
+uv tool install "sqlrooms[snowflake]"
 ```
 
 ### Postgres
@@ -211,7 +210,7 @@ uv sync --extra snowflake
 uvx sqlrooms \
   ./sqlrooms.db \
   --ws-port 4000 \
-  --port 4173
+  --port 3000
 ```
 
 ### Snowflake
@@ -220,7 +219,7 @@ uvx sqlrooms \
 uvx sqlrooms \
   ./sqlrooms.db \
   --ws-port 4000 \
-  --port 4173
+  --port 3000
 ```
 
 What this enables:
@@ -234,41 +233,3 @@ Notes:
 
 - Configure connectors in `sqlrooms.toml` using `[[db.connectors]]` entries.
 - Connector libraries are optional extras (`postgres`, `snowflake`, or `connectors`).
-
-## Developer setup
-
-Local dev loop for the CLI and UI:
-
-1. Install deps and build the dedicated UI (from repo root):
-
-```bash
-pnpm install
-pnpm --filter sqlrooms-python build:ui
-# build outputs directly to python/sqlrooms/sqlrooms/web/static
-```
-
-2. Dev the Python CLI app from the repo root:
-
-```bash
-pnpm dev cli
-```
-
-This starts the Python API server on `http://127.0.0.1:4273` with `--no-ui`
-and the Vite UI on `http://localhost:4174`. If those ports are busy, the dev
-script selects the next free API and UI ports from separate ranges and points
-the Vite proxy at the selected API port. The auto-created dev database is named
-after the selected UI port, for example `sqlrooms-4174.db`.
-
-3. Run the Python API server on its own (optional):
-
-```bash
-cd python/sqlrooms
-pnpm dev
-```
-
-Tips:
-
-- Use `--no-open-browser` if you don’t want the static bundle auto-opened.
-- Use `--no-ui` when pairing the Python API server with the Vite UI dev server.
-- Rebuild the UI (`pnpm --filter sqlrooms-python build:ui`) when you want the Python server to serve new static assets.
-- `/api/config` reflects runtime config (AI providers/default model, DB bridge metadata, WS URL).

{sqlrooms-0.1.0 → sqlrooms-0.1.2}/README.md

@@ -5,27 +5,27 @@ Launch a local SQLRooms DuckDB project for adding data, authoring worksheets, an
 ## Quick start
 
 ```bash
-# From the repo root
-uvx sqlrooms \
-  ./sqlrooms.db
+uvx sqlrooms ./sqlrooms.db
 ```
 
 What happens:
 
 - Starts the DuckDB websocket backend (from `sqlrooms-server`) on a free local port.
-- Serves the SQLRooms worksheet UI on `http://localhost:4173`, or the next free port, and opens your browser (disable with `--no-open-browser`).
+- Serves the SQLRooms worksheet UI on `http://localhost:3000`, or the next free port, and opens your browser (disable with `--no-open-browser`).
 - Drag-and-drop CSV, TSV, JSON, Parquet, and DuckDB files to load them into DuckDB; files are uploaded to a local `sqlrooms_uploads` folder and referenced by path.
 - UI state is stored in the SQLRooms meta namespace (default `__sqlrooms`) of the selected DuckDB file.
 
 ## CLI flags
 
 - `DB_PATH` (positional): DuckDB project file to load/create (e.g. `sqlrooms ./my.db`). Required unless `--db-path` is provided.
+- `--version`: Print the installed `sqlrooms` CLI version and exit.
 - `--db-path`: DuckDB database to use as a flag alternative. Pass a filepath to persist, or `:memory:` for an explicit temporary in-memory session.
-- `--host` / `--port`: HTTP host/port for the UI. The default bind address is `127.0.0.1`. If `--port` is omitted, `4173` or the next free port is chosen automatically.
+- `--host` / `--port`: HTTP host/port for the UI. The default bind address is `127.0.0.1`. If `--port` is omitted, `3000` or the next free port is chosen automatically.
 - `--ws-port`: WebSocket port for DuckDB queries. If omitted, a free port is chosen automatically.
 - `--experimental`: Enable experimental artifacts, blocks, commands, and agent tools.
 - `--experimental-sync`: Enable experimental sync (CRDT) over WebSocket (Loro). Requires `--experimental`.
 - `--ai-devtools`: Enable the AI session devtools button in the UI, including production-built UI bundles. Can also be set with `SQLROOMS_AI_DEVTOOLS=1`.
+- `--debug`: Enable verbose debug logging, including HTTP access logs and DuckDB query timing.
 - `--meta-db`: Optional path to a dedicated DuckDB file for SQLRooms meta tables (UI state + CRDT snapshots). If omitted, meta tables are stored in the main DB.
 - `--meta-namespace` (default `__sqlrooms`): Namespace for SQLRooms meta tables. If `--meta-db` is provided, used as ATTACH alias; otherwise used as a schema in the main DB.
 - `--no-open-browser`: Skip automatically opening the browser tab.
@@ -55,10 +55,10 @@ Uploads go to `/api/upload`. Runtime config for the UI is exposed at `/api/confi
 
 ## Manual smoke test
 
-Use this before release candidates to prove the first-launch path:
+Use this to prove the first-launch path:
 
 ```bash
-uv run --project python --package sqlrooms sqlrooms \
+uvx sqlrooms \
   --no-open-browser \
   ./smoke.duckdb
 ```
@@ -66,7 +66,7 @@ uv run --project python --package sqlrooms sqlrooms \
 Then open the printed UI URL and verify:
 
 - The app starts without a database connection error.
-- Dragging `python/sqlrooms/tests/fixtures/cars.csv` into the data panel creates a `cars` table.
+- Dragging a small CSV file into the data panel creates a table.
 - The uploaded CSV lands next to `smoke.duckdb` under `sqlrooms_uploads/`.
 - The data sidebar shows `main.cars` and does not show SQLRooms internal metadata.
 - A worksheet is created or selected automatically and contains a `cars` data-table explorer block.
@@ -163,11 +163,10 @@ results into core DuckDB for downstream notebook cells.
 Install optional connector dependencies first:
 
 ```bash
-# From python/sqlrooms
-uv sync --extra connectors
+uv tool install "sqlrooms[connectors]"
 # or install just one connector:
-uv sync --extra postgres
-uv sync --extra snowflake
+uv tool install "sqlrooms[postgres]"
+uv tool install "sqlrooms[snowflake]"
 ```
 
 ### Postgres
@@ -176,7 +175,7 @@ uv sync --extra snowflake
 uvx sqlrooms \
   ./sqlrooms.db \
   --ws-port 4000 \
-  --port 4173
+  --port 3000
 ```
 
 ### Snowflake
@@ -185,7 +184,7 @@ uvx sqlrooms \
 uvx sqlrooms \
   ./sqlrooms.db \
   --ws-port 4000 \
-  --port 4173
+  --port 3000
 ```
 
 What this enables:
@@ -199,41 +198,3 @@ Notes:
 
 - Configure connectors in `sqlrooms.toml` using `[[db.connectors]]` entries.
 - Connector libraries are optional extras (`postgres`, `snowflake`, or `connectors`).
-
-## Developer setup
-
-Local dev loop for the CLI and UI:
-
-1. Install deps and build the dedicated UI (from repo root):
-
-```bash
-pnpm install
-pnpm --filter sqlrooms-python build:ui
-# build outputs directly to python/sqlrooms/sqlrooms/web/static
-```
-
-2. Dev the Python CLI app from the repo root:
-
-```bash
-pnpm dev cli
-```
-
-This starts the Python API server on `http://127.0.0.1:4273` with `--no-ui`
-and the Vite UI on `http://localhost:4174`. If those ports are busy, the dev
-script selects the next free API and UI ports from separate ranges and points
-the Vite proxy at the selected API port. The auto-created dev database is named
-after the selected UI port, for example `sqlrooms-4174.db`.
-
-3. Run the Python API server on its own (optional):
-
-```bash
-cd python/sqlrooms
-pnpm dev
-```
-
-Tips:
-
-- Use `--no-open-browser` if you don’t want the static bundle auto-opened.
-- Use `--no-ui` when pairing the Python API server with the Vite UI dev server.
-- Rebuild the UI (`pnpm --filter sqlrooms-python build:ui`) when you want the Python server to serve new static assets.
-- `/api/config` reflects runtime config (AI providers/default model, DB bridge metadata, WS URL).

{sqlrooms-0.1.0 → sqlrooms-0.1.2}/node_modules/sqlrooms-cli-app/README.md

@@ -2,7 +2,7 @@
 
 This package is the **Vite/React UI** that powers the Python `sqlrooms` CLI (`python/sqlrooms`).
 
-In development it runs as a separate dev server (default `http://localhost:4174`) and **proxies API calls** to the Python server.
+In development it runs as a separate dev server (default `http://localhost:3100`) and **proxies API calls** to the Python server.
 
 In production (published `sqlrooms` wheel), the UI is served as **static assets** bundled into the Python package at:
 
@@ -18,28 +18,28 @@ cd /Users/ilya/Workspace/sqlrooms
 
 pnpm --dir python/sqlrooms build
 
-uv run --project python --package sqlrooms sqlrooms \
-  ./smoke.duckdb \
-  --no-open-browser
+uv run --project python/sqlrooms sqlrooms \
+  --no-open-browser \
+  /tmp/sqlrooms-smoke.duckdb
 ```
 
 Open the UI URL printed in the terminal. It should be
-`http://127.0.0.1:4173` or the next free port.
+`http://127.0.0.1:3000` or the next free port.
 
 The bare CLI command works only after installing the CLI somewhere on your
 `PATH`:
 
 ```bash
 uv tool install /Users/ilya/Workspace/sqlrooms/python/sqlrooms
-sqlrooms ./smoke.duckdb --no-open-browser
+sqlrooms --no-open-browser /tmp/sqlrooms-smoke.duckdb
 ```
 
 For release smoke testing, verify both local execution paths:
 
 ```bash
-uv run --project python --package sqlrooms sqlrooms ./smoke.duckdb --no-open-browser
+uv run --project python/sqlrooms sqlrooms --no-open-browser /tmp/sqlrooms-smoke.duckdb
 uv tool install --reinstall /Users/ilya/Workspace/sqlrooms/python/sqlrooms
-sqlrooms ./smoke.duckdb --no-open-browser
+sqlrooms --no-open-browser /tmp/sqlrooms-smoke.duckdb
 ```
 
 In the UI, drag in:
@@ -51,6 +51,76 @@ In the UI, drag in:
 Verify `cars` appears, create a worksheet/Mosaic chart/dashboard, stop the
 server, restart the same command, and confirm the state comes back.
 
+## Python CLI release workflow
+
+The Python CLI release is split into an intentional version step and a publish
+step. Publishing never bumps versions automatically.
+
+Before versioning or publishing, test a production build locally:
+
+```bash
+pnpm --dir python/sqlrooms build
+
+# Source/workspace check. This should reflect python/sqlrooms/package.json.
+uv run --project python/sqlrooms sqlrooms \
+  --version
+
+uv run --project python/sqlrooms sqlrooms \
+  --no-open-browser \
+  /tmp/sqlrooms-smoke.duckdb
+```
+
+For the closest local install check, install the freshly built wheel from
+`python/dist` into a `uv tool` environment. Use the exact wheel for the current
+`python/sqlrooms/package.json` version so older files in `python/dist` are not
+selected accidentally:
+
+```bash
+SQLROOMS_VERSION=$(node -p "require('./python/sqlrooms/package.json').version")
+uv tool install --reinstall "python/dist/sqlrooms-${SQLROOMS_VERSION}-py3-none-any.whl"
+sqlrooms --version
+sqlrooms --no-open-browser /tmp/sqlrooms-smoke.duckdb
+```
+
+Open the printed UI URL, drag in the CSV fixture listed above, create a
+worksheet/chart/dashboard, then restart against the same `/tmp/sqlrooms-smoke.duckdb` and
+confirm the imported data and workspace state come back.
+
+1. Choose the package target:
+   - `sqlrooms` for the CLI package and bundled UI.
+   - `sqlrooms-server` for the DuckDB websocket server package.
+   - `all` when both packages should be released in dependency order.
+2. Version the selected package or packages explicitly:
+
+   ```bash
+   pnpm cli:version --target sqlrooms-server --bump patch
+   pnpm cli:version --target sqlrooms --set 0.2.0
+   pnpm cli:version --target all --bump minor
+   ```
+
+   Hatch reads package versions from each package's `package.json`. When
+   `sqlrooms-server` is versioned, the workflow also updates the
+   `sqlrooms-server>=...` dependency floor in `python/sqlrooms/pyproject.toml`.
+
+3. Run the dry publish workflow for the intended target:
+
+   ```bash
+   pnpm cli:publish:dry --target sqlrooms
+   ```
+
+   The dry workflow runs validation and builds the selected package or packages,
+   but it does not upload to PyPI.
+
+4. Publish the same target:
+
+   ```bash
+   pnpm cli:publish --target sqlrooms
+   ```
+
+   Publishing runs validation, builds the package, then uploads the built
+   distributions with Twine. Use `--target all` only when both packages are part
+   of the release.
+
 ## Dev mode (UI + Python server together)
 
 From the repo root:
@@ -61,14 +131,14 @@ pnpm dev cli
 
 This starts:
 
-- the Python API server on `http://127.0.0.1:4273` without serving static UI, or the next free port
-- the Vite UI on `http://localhost:4174`, or the next free port, proxying `/api` and `/config.json` to the selected Python API port
-- a per-session dev database named after the selected UI port, for example `sqlrooms-4174.db`
+- the Python API server on `http://127.0.0.1:4273` with `--experimental` and without serving static UI, or the next free port
+- the Vite UI on `http://localhost:3100`, or the next free port, proxying `/api` and `/config.json` to the selected Python API port
+- a per-session dev database named after the selected UI port, for example `sqlrooms-3100.db`
 
 If you want fixed ports, pass them to the Python server:
 
 ```bash
-pnpm dev cli -- --port 4176 --ws-port 4002
+pnpm dev cli -- --port 4274 --ws-port 4002
 ```
 
 ## Dev mode (separate terminals)
@@ -83,10 +153,10 @@ pnpm dev -- --no-ui
 Terminal B (UI):
 
 ```bash
-pnpm --filter sqlrooms-cli-app dev -- --host --port 4174
+pnpm --filter sqlrooms-cli-app dev -- --host --port 3100
 ```
 
-The Python package dev helper uses API port `4173` by default to match the
+The Python package dev helper uses API port `4273` by default to match the
 Vite proxy. If you pass a different Python API port, also set
 `SQLROOMS_CLI_API_PROXY_TARGET` when starting Vite.
 

{sqlrooms-0.1.0 → sqlrooms-0.1.2}/node_modules/sqlrooms-cli-app/node_modules/@sqlrooms/ai/node_modules/@sqlrooms/data-table/node_modules/@sqlrooms/duckdb/README.md

@@ -57,6 +57,33 @@ function UserList() {
 
 For more information and examples on using the `useSql` hook, see the [useSql API documentation](/api/duckdb/functions/useSql).
 
+### Monitoring WebSocket DuckDB Connections
+
+`createWebSocketDuckDbConnector()` exposes the persistent WebSocket lifecycle
+through `connectionStatus`, `subscribeConnectionStatus()`, and the optional
+`onConnectionStatusChange` callback. Use this for live UI affordances such as
+lost-connection dialogs. Call `reconnect()` to reopen the socket and rerun the
+connector initialization SQL without destroying the connector instance.
+
+```tsx
+import {createWebSocketDuckDbConnector} from '@sqlrooms/duckdb';
+
+const connector = createWebSocketDuckDbConnector({
+  wsUrl: 'ws://localhost:4000',
+  onConnectionStatusChange: (status) => {
+    console.log('DuckDB WebSocket status:', status);
+  },
+});
+
+const unsubscribe = connector.subscribeConnectionStatus((status) => {
+  if (status === 'disconnected') {
+    console.warn('DuckDB WebSocket disconnected');
+  }
+});
+
+await connector.reconnect();
+```
+
 ### Looking up Table Metadata
 
 Use `useDataTable()` in React components or `db.findTable()` from the room

{sqlrooms-0.1.0 → sqlrooms-0.1.2}/node_modules/sqlrooms-cli-app/node_modules/@sqlrooms/canvas/node_modules/@sqlrooms/cells/node_modules/@sqlrooms/vega/node_modules/@sqlrooms/documents/README.md

@@ -129,6 +129,8 @@ and provide block DTO helpers for command and AI authoring surfaces:
 ```tsx
 import {
   BlockDocumentsSliceConfig,
+  createAddBlockDocumentTextBlockTool,
+  createListBlockDocumentBlocksTool,
   createBlockDocumentsSlice,
 } from '@sqlrooms/documents';
 
@@ -147,6 +149,24 @@ const roomStore = createRoomStore(
 );
 ```
 
+Generic AI helpers use the same block DTOs as commands and the editor. Hosts
+provide a small `BlockDocumentAiAdapter` that ensures a document, lists its
+blocks, and appends new blocks; feature packages or apps can then compose these
+tools with their own stateful-block tools:
+
+```ts
+const tools = {
+  add_block_document_text_block: createAddBlockDocumentTextBlockTool({
+    blockDocumentAdapter,
+    blockDocumentId,
+  }),
+  list_block_document_blocks: createListBlockDocumentBlocksTool({
+    blockDocumentAdapter,
+    blockDocumentId,
+  }),
+};
+```
+
 The slice can create block documents, replace the Tiptap JSON body, and
 append/insert/update/remove/reorder top-level blocks. Supported block DTOs
 include headings, paragraphs, lists, todos, images, chart images,

{sqlrooms-0.1.0 → sqlrooms-0.1.2}/node_modules/sqlrooms-cli-app/node_modules/@sqlrooms/deck/README.md

@@ -196,6 +196,22 @@ dataset extent using the declared longitude/latitude columns and fits the
 initial map view once, instead of inferring bounds from the loaded Arrow
 payload in React.
 
+Use `createDeckMapPanelFromNativeConfig(...)` when a host surface already has a
+native Deck map config, for example from AI tooling, and needs the same
+dashboard-compatible `deck-json-map` panel shape that the dashboard map tool
+creates.
+
+## Embeddable Map Blocks
+
+Host applications that expose document-like block surfaces can render maps
+without first creating a visible dashboard. Use `ensureDeckMapBlockState(...)`
+to initialize persisted map state for a durable block id, then render it with
+`DeckMapBlockRenderer`.
+
+The block primitive reuses the dashboard map panel runtime internally, while
+leaving each host surface free to adapt its own block/document semantics around
+it.
+
 ## Core Concepts
 
 ### `DeckJsonMap`

{sqlrooms-0.1.0 → sqlrooms-0.1.2}/node_modules/sqlrooms-cli-app/node_modules/@sqlrooms/deck/node_modules/@sqlrooms/mosaic/README.md

@@ -172,12 +172,17 @@ renderer for `@sqlrooms/documents` block documents. Register it with a
 host-provided stateful block type such as `data-table` when a document or
 worksheet surface should embed an interactive Data Table Explorer directly.
 
-### Worksheet Agent HTML App Tools
+Use `DataTableSelector` or `DataTableSelectorEmptyState` when another host
+surface needs the same searchable table picker used by dashboards and data
+table blocks.
 
-`createWorksheetAgentTool` exposes worksheet HTML app block workflows by
-default. Hosts that gate or do not support HTML app blocks should pass
-`htmlAppBlocksEnabled: false` so the agent omits `add_html_app_block` and does
-not advertise HTML app block workflows in its instructions.
+### Block Document AI Integrations
+
+`createBlockDocumentChartTools`, `createAddMosaicDashboardBlockTool`, and
+`createBlockDocumentDataTableExplorerTool` expose Mosaic-owned capabilities for
+block-document hosts. The host provides a `BlockDocumentAiAdapter` from
+`@sqlrooms/documents` plus callbacks for creating host-specific stateful block
+state, then composes these tools with app-specific agent policy.
 
 ### Mosaic Dashboard Panels
 

sqlrooms-0.1.2/node_modules/sqlrooms-cli-app/node_modules/@sqlrooms/python/README.md

@@ -0,0 +1,87 @@
+Python runtime and block primitives for SQLRooms worksheets and block documents.
+
+This package provides:
+
+- persisted Python block state schemas for code, inputs, outputs, requirements,
+  execution policy, and bounded last-result summaries
+- `createPythonSlice()` for durable block state and runtime result updates
+- a Pyodide worker runtime adapter with SQLRooms host-query bridge support
+- `PythonBlock` and `createPythonBlockDefinition()` for embeddable
+  worksheet/document blocks
+- `createPythonBlockCommands()` for command-backed create, update, run, and
+  clear operations
+
+If no runtime adapter is configured, running a block records a bounded error
+result instead of executing hidden Python.
+
+## Store setup
+
+```tsx
+import {
+  createPythonSlice,
+  PythonSliceConfig,
+  type PythonSliceState,
+} from '@sqlrooms/python/block';
+
+type RoomState = PythonSliceState;
+
+const sliceConfigSchemas = {
+  python: PythonSliceConfig,
+};
+
+const storeSlices = {
+  ...createPythonSlice()(set, get, store),
+};
+```
+
+## Runtime adapters
+
+Adapters implement a small execution interface:
+
+```ts
+const adapter = {
+  id: 'pyodide',
+  status: async () => ({state: 'ready'}),
+  execute: async (request, host) => ({
+    executionId: request.executionId,
+    status: 'success',
+    stdout: '',
+    stderr: '',
+    outputs: [{type: 'json', name: 'result', value: 42}],
+    durationMs: 5,
+  }),
+};
+```
+
+Pass the adapter to `createPythonSlice({runtimeAdapter: adapter})`.
+
+The bundled Pyodide adapter captures the global `result` value, or the final
+expression value when no `result` global is assigned. It returns JSON, text,
+HTML, and Vega-Lite outputs when Python objects expose common rich-display
+methods such as `_repr_mimebundle_()`, `_repr_html_()`, or Altair `to_dict()`.
+HTML and Vega-Lite previews are rendered in sandboxed iframes by
+`PythonBlock`.
+
+When user code imports `altair`, the Pyodide worker installs Altair on demand
+through `micropip`. The SQLRooms bridge exposes `sqlrooms.query()` and
+`sqlrooms.query_df()` as pandas DataFrames, so query results can be passed
+directly to libraries such as Altair. Use `sqlrooms.query_records()` for plain
+row records and `sqlrooms.query_raw()` when column metadata or `rowCount` is
+needed.
+
+## Export paths
+
+- `@sqlrooms/python/runtime` exports runtime contracts and the Pyodide adapter.
+- `@sqlrooms/python/block` exports the React block, Zustand slice, commands,
+  and block-facing state schemas.
+- `@sqlrooms/python` is the curated root entrypoint.
+
+## Worksheet commands
+
+Use `createPythonBlockCommands({commandNamespace: 'worksheet'})` alongside the
+worksheet block-document commands to expose:
+
+- `worksheet.add-python-block`
+- `worksheet.update-python-block-code`
+- `worksheet.run-python-block`
+- `worksheet.clear-python-block-result`

sqlrooms-0.1.2/node_modules/sqlrooms-cli-app/node_modules/@sqlrooms/python/node_modules/@codemirror/lang-python/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (C) 2018-2021 by Marijn Haverbeke <marijn@haverbeke.berlin> and others
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.