roomie 0.1.0__tar.gz

roomie-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+**/__pycache__
+**/.ruff_cache
+**/.pytest_cache
+**/.mypy_cache
+**/.venv
+.DS_Store
+.DS_Store?
+output/

roomie-0.1.0/LICENSE

@@ -0,0 +1,9 @@
+MIT License
+
+Copyright 2025 SQLRooms Contributors
+
+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.

roomie-0.1.0/PKG-INFO

@@ -0,0 +1,104 @@
+Metadata-Version: 2.5
+Name: roomie
+Version: 0.1.0
+Summary: Local DuckDB documents with external AI through MCP
+Project-URL: repository, https://github.com/sqlrooms/sqlrooms
+Author: SQLRooms Contributors
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.10
+Requires-Dist: sqlrooms<0.2,>=0.1.6
+Description-Content-Type: text/markdown
+
+# Roomie
+
+Roomie is a local DuckDB workspace for documents containing interactive Mosaic
+charts, table explorers, dashboards, and sandboxed HTML apps. AI runs in your
+external Claude Code or Codex host through MCP.
+
+This implementation is stacked on SQLRooms #928 (which depends on #927).
+Publication is blocked until a SQLRooms release containing the shared runtime and
+application adapters is available. The initial release requirement is
+`sqlrooms>=0.1.6,<0.2`; the stack is tested with a locally built prerequisite wheel.
+Do not publish Roomie against the existing 0.1.5 runtime.
+
+```sh
+roomie analysis.duckdb
+roomie --no-open-browser analysis.duckdb
+python -m roomie --version
+roomie agent setup --client claude-code
+roomie agent setup --client codex
+# Review the preview, then add --apply to install the scoped configuration.
+roomie agent status
+```
+
+Opening a bare URL does not authorize it. Use the temporary launch link printed
+in an interactive terminal, or open_workspace's launchUrl. Page sessions renew
+in the same tab; after a server restart, obtain a fresh link. Native credentials
+stay in owner-only temporary files and never enter HTML app code.
+
+Use New document and Insert to compose analyses. Add data using Import data or
+Upload file. Inspect a table from the sidebar. Edit text directly, configure
+charts and dashboards in their settings, and use Edit blocks for HTML source and
+advanced table preferences. Table filters persist as a saved baseline; use Reset
+to clear that baseline before choosing a replacement. Save status reports actual disk writes. Wait for Saved
+before manually closing a tab or stopping the terminal. Managed close waits for
+browser flush and database checkpoint. Browser-backed tools require the owning
+browser; uncertain mutations are never replayed automatically.
+
+Host setup preserves unrelated MCP entries and rejects conflicts at the `roomie`
+key. Claude Code setup returns a `claude --plugin-dir ...` launch command for the
+bundled plugin. Codex setup installs a skill under `~/.agents/skills/roomie` and
+adds its own MCP entry, using the installed Python interpreter. Re-run setup after
+moving/reinstalling the environment. [Codex MCP](https://learn.chatgpt.com/docs/extend/mcp?surface=cli)
+and [skills](https://learn.chatgpt.com/docs/build-skills) document these mechanisms.
+
+Roomie's catalog, logs, and managed workspaces live under `ROOMIE_HOME` (default
+`~/.roomie`); `ROOMIE_WORKSPACES_DIR` overrides the managed folder. Its database
+metadata lives in `__roomie.ui_state` with application `roomie`, schema version 1.
+Ordinary DuckDB files and SQLRooms metadata can coexist. Unsupported Roomie
+metadata disables startup/saving instead of overwriting it. Full SQLRooms project
+conversion is outside this product.
+
+Rendered charts use local physical tables. Arbitrary custom Mosaic specs are
+unsupported. HTML queries must be ordinary local reads; import or materialize
+external data through the approved database commands before rendering it. Views,
+attached databases, dynamic SQL and unverified functions are rejected in rendered
+queries.
+
+Roomie initializes no sync or embedded assistant. The SQLRooms dependency still
+installs Loro and SQLRooms assets; this is not a CRDT-free dependency tree. Native
+credential storage currently supports POSIX platforms; Windows ACLs are unverified.
+
+## Development and release
+
+Build workspace packages before the UI. Use `pnpm dev roomie` for authenticated
+API/Vite development, including `--no-open-browser`. `pnpm roomie:build` bundles
+assets and creates wheel/sdist; `pnpm roomie:publish:dry` verifies artifacts without
+uploading. Recheck the prerequisite release and PyPI name ownership separately.
+The dry-run does not upload packages or configure release credentials/Trusted
+Publishing.
+
+See [Publishing SQLRooms and Roomie](../PUBLISHING.md) for the release sequence,
+PyPI authentication, and installation checks against the published runtime.
+
+Development setup requires Node 24, pnpm 11 and uv. End users of the wheel do not
+need Node. `pnpm --filter roomie-python dev:setup` installs the paired checkout
+runtime and Roomie into `python/.venv`, explicitly bypassing Roomie dependency
+resolution only while the upstream release is pending. Published metadata never
+uses this development override. Version Roomie independently with
+`pnpm cli:version --target roomie --bump patch`; the build synchronizes plugin
+and bundled version metadata from `python/roomie/package.json`.
+
+If startup rejects a workspace envelope, keep the file and inspect its metadata;
+do not remove unknown fields to force it open. If the external host reports
+`waiting_for_browser`, open a fresh launch link for that exact instance. If saving
+fails, retain the browser, resolve the database error, then retry Save or managed
+close. A failed checkpoint keeps admission stopped and can be retried. A manual
+terminal process is never closed by the managed connector.
+
+The initial test platform is macOS arm64, Python 3.12. Python >=3.10 and POSIX are
+the declared support range; other Python/OS combinations still need release CI.
+The implementation and verification record is [VERIFICATION.md](VERIFICATION.md).

roomie-0.1.0/README.md

@@ -0,0 +1,90 @@
+# Roomie
+
+Roomie is a local DuckDB workspace for documents containing interactive Mosaic
+charts, table explorers, dashboards, and sandboxed HTML apps. AI runs in your
+external Claude Code or Codex host through MCP.
+
+This implementation is stacked on SQLRooms #928 (which depends on #927).
+Publication is blocked until a SQLRooms release containing the shared runtime and
+application adapters is available. The initial release requirement is
+`sqlrooms>=0.1.6,<0.2`; the stack is tested with a locally built prerequisite wheel.
+Do not publish Roomie against the existing 0.1.5 runtime.
+
+```sh
+roomie analysis.duckdb
+roomie --no-open-browser analysis.duckdb
+python -m roomie --version
+roomie agent setup --client claude-code
+roomie agent setup --client codex
+# Review the preview, then add --apply to install the scoped configuration.
+roomie agent status
+```
+
+Opening a bare URL does not authorize it. Use the temporary launch link printed
+in an interactive terminal, or open_workspace's launchUrl. Page sessions renew
+in the same tab; after a server restart, obtain a fresh link. Native credentials
+stay in owner-only temporary files and never enter HTML app code.
+
+Use New document and Insert to compose analyses. Add data using Import data or
+Upload file. Inspect a table from the sidebar. Edit text directly, configure
+charts and dashboards in their settings, and use Edit blocks for HTML source and
+advanced table preferences. Table filters persist as a saved baseline; use Reset
+to clear that baseline before choosing a replacement. Save status reports actual disk writes. Wait for Saved
+before manually closing a tab or stopping the terminal. Managed close waits for
+browser flush and database checkpoint. Browser-backed tools require the owning
+browser; uncertain mutations are never replayed automatically.
+
+Host setup preserves unrelated MCP entries and rejects conflicts at the `roomie`
+key. Claude Code setup returns a `claude --plugin-dir ...` launch command for the
+bundled plugin. Codex setup installs a skill under `~/.agents/skills/roomie` and
+adds its own MCP entry, using the installed Python interpreter. Re-run setup after
+moving/reinstalling the environment. [Codex MCP](https://learn.chatgpt.com/docs/extend/mcp?surface=cli)
+and [skills](https://learn.chatgpt.com/docs/build-skills) document these mechanisms.
+
+Roomie's catalog, logs, and managed workspaces live under `ROOMIE_HOME` (default
+`~/.roomie`); `ROOMIE_WORKSPACES_DIR` overrides the managed folder. Its database
+metadata lives in `__roomie.ui_state` with application `roomie`, schema version 1.
+Ordinary DuckDB files and SQLRooms metadata can coexist. Unsupported Roomie
+metadata disables startup/saving instead of overwriting it. Full SQLRooms project
+conversion is outside this product.
+
+Rendered charts use local physical tables. Arbitrary custom Mosaic specs are
+unsupported. HTML queries must be ordinary local reads; import or materialize
+external data through the approved database commands before rendering it. Views,
+attached databases, dynamic SQL and unverified functions are rejected in rendered
+queries.
+
+Roomie initializes no sync or embedded assistant. The SQLRooms dependency still
+installs Loro and SQLRooms assets; this is not a CRDT-free dependency tree. Native
+credential storage currently supports POSIX platforms; Windows ACLs are unverified.
+
+## Development and release
+
+Build workspace packages before the UI. Use `pnpm dev roomie` for authenticated
+API/Vite development, including `--no-open-browser`. `pnpm roomie:build` bundles
+assets and creates wheel/sdist; `pnpm roomie:publish:dry` verifies artifacts without
+uploading. Recheck the prerequisite release and PyPI name ownership separately.
+The dry-run does not upload packages or configure release credentials/Trusted
+Publishing.
+
+See [Publishing SQLRooms and Roomie](../PUBLISHING.md) for the release sequence,
+PyPI authentication, and installation checks against the published runtime.
+
+Development setup requires Node 24, pnpm 11 and uv. End users of the wheel do not
+need Node. `pnpm --filter roomie-python dev:setup` installs the paired checkout
+runtime and Roomie into `python/.venv`, explicitly bypassing Roomie dependency
+resolution only while the upstream release is pending. Published metadata never
+uses this development override. Version Roomie independently with
+`pnpm cli:version --target roomie --bump patch`; the build synchronizes plugin
+and bundled version metadata from `python/roomie/package.json`.
+
+If startup rejects a workspace envelope, keep the file and inspect its metadata;
+do not remove unknown fields to force it open. If the external host reports
+`waiting_for_browser`, open a fresh launch link for that exact instance. If saving
+fails, retain the browser, resolve the database error, then retry Save or managed
+close. A failed checkpoint keeps admission stopped and can be retried. A manual
+terminal process is never closed by the managed connector.
+
+The initial test platform is macOS arm64, Python 3.12. Python >=3.10 and POSIX are
+the declared support range; other Python/OS combinations still need release CI.
+The implementation and verification record is [VERIFICATION.md](VERIFICATION.md).

roomie-0.1.0/node_modules/roomie-cli-app/README.md

@@ -0,0 +1,33 @@
+# Roomie browser application
+
+A fixed, document-focused composition of SQLRooms packages, bundled by the
+`roomie` Python distribution. Its only top-level artifact is a Document. Each
+document can contain chart, data-table explorer, dashboard and HTML app blocks,
+plus ordinary editorial content. Arbitrary custom Mosaic specs are excluded;
+rendered charts and tables use physical local data. HTML query requests pass the
+host's local-read admission policy before reaching the shared query executor. Dashboard panels are limited to Mosaic charts
+and table explorers. Backing state is document-owned and is not exposed as extra
+artifacts. No assistant, provider configuration, profiles or CRDT slice is loaded.
+
+Run `pnpm dev roomie [database.duckdb]` from the repository root. It builds shared
+packages, installs the paired Python stack, starts API port 4274 and Vite port
+3200, waits for readiness, verifies the backend process and binding, and opens a
+one-use authorized page link. `--no-open-browser` retains the interactive launch
+link without opening a tab. These fixed development ports fail clearly on
+conflicts. Use the packaged CLI for an automatically assigned port.
+
+`src/capabilities.ts` is the fixed capability manifest; `src/model.ts` defines
+the persisted schema. Commands
+in `src/commands.ts` compose the package APIs used by both manual UI actions and
+MCP. `src/store.ts` wires only needed slices and validates persisted data before
+enabling writes to `__roomie.ui_state`. Table filters are saved as Mosaic-generated
+predicates, validated as ordinary local SELECT expressions before agent changes
+or hydration. Restored filters appear as a saved baseline; Reset clears them
+before choosing a replacement. Column selection, sorting and page size are
+editable through Edit blocks → data-table settings.
+
+`pnpm --filter roomie-cli-app test` runs schema, command-boundary and filter
+persistence regressions. `pnpm roomie:build` builds the dependency graph, browser
+bundle, tool contract, notices, wheel and sdist. See
+[Python usage and release instructions](../../python/roomie/README.md) and
+[verification evidence](../../python/roomie/VERIFICATION.md).

roomie-0.1.0/node_modules/roomie-cli-app/node_modules/@jest/globals/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) Meta Platforms, Inc. and affiliates.
+Copyright Contributors to the Jest project.
+
+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.

roomie-0.1.0/node_modules/roomie-cli-app/node_modules/@jest/globals/package.json

@@ -0,0 +1,32 @@
+{
+  "name": "@jest/globals",
+  "version": "30.4.1",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/jestjs/jest.git",
+    "directory": "packages/jest-globals"
+  },
+  "engines": {
+    "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0"
+  },
+  "license": "MIT",
+  "main": "./build/index.js",
+  "types": "./build/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./build/index.d.ts",
+      "default": "./build/index.js"
+    },
+    "./package.json": "./package.json"
+  },
+  "dependencies": {
+    "@jest/environment": "30.4.1",
+    "@jest/expect": "30.4.1",
+    "@jest/types": "30.4.1",
+    "jest-mock": "30.4.1"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "gitHead": "b3b4a09ed3005369dacc7466d1d2122797283785"
+}

roomie-0.1.0/node_modules/roomie-cli-app/node_modules/@sqlrooms/app-runtime/README.md

@@ -0,0 +1,218 @@
+# @sqlrooms/app-runtime
+
+> **Experimental:** This package's API and behavior may change between releases.
+
+`@sqlrooms/app-runtime` defines the iframe runtime bridge used by generated
+HTML apps in SQLRooms. It owns the protocol between a sandboxed app iframe and
+the SQLRooms host; it does not own project authoring, bundling, or WebContainer
+startup.
+
+## Runtime Scope
+
+The first supported app surface is the `html-app` stateful block. The same
+bridge contract can also be reused by artifact shells and WebContainer previews,
+but the block remains the durable v1 state model.
+
+The app-facing API is intentionally small:
+
+```js
+const result = await window.sqlrooms.query(
+  'select region, sum(revenue) as revenue from sales group by region',
+);
+console.log(result.rows);
+```
+
+TypeScript apps may use the client entrypoint:
+
+```ts
+import {createAppClient} from '@sqlrooms/app-runtime/client';
+
+const app = createAppClient();
+const result = await app.query('select * from sales limit 100');
+```
+
+## Threat Model
+
+Generated apps are treated as untrusted code. They run in a sandboxed iframe and
+must not receive direct access to DuckDB connectors, the room store, filesystem
+APIs, host DOM nodes, command execution, or mutation-capable host services.
+
+The host grants explicit capabilities and handles every request. The initial
+capability set is deliberately narrow:
+
+- read-only `query`
+- optional table/schema discovery
+- optional initial data payloads
+
+The v1 runtime explicitly excludes:
+
+- write queries
+- filesystem access
+- host DOM access
+- room store mutation
+- command execution
+- network access as an app-runtime capability
+
+Read-only query handling starts with `state.db.sqlSelectToJson` as the SQL
+classification gate. Hosts should additionally enforce single-statement input,
+row limits, timeout handling, and JSON-serializable result bounds before data
+crosses into the iframe.
+
+## Relation To WebContainer
+
+`@sqlrooms/webcontainer` answers how a generated project is authored, edited,
+built, and served. `@sqlrooms/app-runtime` answers what a rendered app can ask
+the SQLRooms host to do.
+
+WebContainer previews can attach the same host bridge to their preview iframe,
+and generated Vite apps can import the client entrypoint or use an injected
+`window.sqlrooms` global. WebContainer should not grow its own separate data
+bridge.
+
+Revision history follows the same boundary. The v1 revision model belongs to
+persisted `html-app` runtime state and does not migrate or version legacy
+WebContainer app project records such as `appProject.config.appsByArtifactId`.
+Those projects can be migrated to `html-app` state later, but they should not
+drive the shared runtime history API.
+
+Hosts can expose revision controls through canonical room commands with
+`createHtmlAppRevisionCommands`. The runtime package owns the command IDs and
+revision operations; the host supplies callbacks for target resolution and state
+updates:
+
+```ts
+const commands = createHtmlAppRevisionCommands({
+  resolveCurrentAppId: (state, context) =>
+    context.invocation.target?.kind === 'artifact'
+      ? context.invocation.target.id
+      : state.currentHtmlAppId,
+  getHtmlAppIds: (state) => Object.keys(state.htmlApps.config.appsById),
+  getHtmlAppState: (state, appId) => state.htmlApps.getApp(appId),
+  renameHtmlApp: (state, appId, title) =>
+    state.htmlApps.renameApp(appId, title),
+  commitHtmlAppRevision: (state, appId, patch, metadata) =>
+    state.htmlApps.commitAppRevision(appId, patch, metadata),
+  restoreHtmlAppRevision: (state, appId, revisionId, metadata) =>
+    state.htmlApps.restoreAppRevision(appId, revisionId, metadata),
+  undoHtmlAppRevision: (state, appId) => state.htmlApps.undoAppRevision(appId),
+  redoHtmlAppRevision: (state, appId) => state.htmlApps.redoAppRevision(appId),
+});
+```
+
+## HTML App Blocks
+
+The `html-app` block stores a small source file map instead of one opaque HTML
+string:
+
+```ts
+{
+  "/index.html": "<!doctype html>...",
+  "/src/app.js": "..."
+}
+```
+
+`entryHtmlPath` points at the HTML file rendered through `iframe.srcdoc`; the
+default is `/index.html`. The host injects the app-runtime prelude before user
+scripts run, so generated apps can call:
+
+`HtmlAppState.intent` can store the durable natural-language objective for a
+generated or edited app. Prefer this over storing raw model input in app state.
+
+Block-document hosts can use `createHtmlAppBlockDocumentBlock` to create the
+stateful block DTO for an owned HTML app runtime without importing CLI app code.
+
+```js
+const {rows, columns, truncated} = await window.sqlrooms.query(
+  'select category, count(*) as n from events group by category',
+);
+```
+
+`queryRows(sql)` is available when an app only needs the plain object rows.
+
+Dependencies are persisted as structured package/version entries:
+
+```ts
+[
+  {
+    package: 'd3',
+    version: '7.9.0',
+    entry: 'dist/d3.min.js',
+    kind: 'script',
+    global: 'd3',
+  },
+];
+```
+
+The v1 resolver turns these into jsDelivr URLs at render time. Persisted state
+keeps the structured entries so a future resolver can use import maps, bundling,
+local caching, or another dependency policy without rewriting app state.
+
+## Revision History
+
+`html-app` state persists source revisions alongside the current source:
+
+```ts
+type HtmlAppRevision = {
+  id: string;
+  name: string;
+  description?: string;
+  sourcePrompt?: string;
+  source: 'assistant' | 'user' | 'restore' | 'system';
+  sessionId?: string;
+  toolCallId?: string;
+  commitGroupId?: string;
+  parentRevisionId?: string;
+  createdAt: number;
+  title: string;
+  intent?: string;
+  files: Record<string, string>;
+  entryHtmlPath: string;
+  requestedCapabilities?: AppCapability[];
+  grantedCapabilities?: AppCapability[];
+  dependencies: HtmlAppDependency[];
+};
+```
+
+Persisted `HtmlAppState` includes `revisions`, `activeRevisionId`, and
+`redoRevisionIds`. Older app states parse with empty history by default, so
+hosts can adopt revision-aware writes without a separate storage migration.
+Diagnostics are not stored in revisions because they describe current runtime
+observations and can be regenerated after restore or preview.
+
+Query results are JSON-serializable:
+
+```ts
+type QueryResult = {
+  rows: Record<string, unknown>[];
+  columns: {name: string; type?: string}[];
+  rowCount: number;
+  truncated: boolean;
+  executionMs?: number;
+};
+```
+
+The host enforces read-only `SELECT` parsing, a single statement, row limits,
+and request timeouts before returning data to the iframe.
+
+`HtmlAppBlock` and `executeReadonlyQuery` accept an optional
+`authorizeQuery(request)` callback. It runs after SELECT parsing and before query
+execution; reject by throwing, or await the host's approval policy. SELECT parsing
+alone does not restrict file readers, views or functions. Hosts requiring a local
+data boundary should supply this callback to validate sources. Existing callers
+without a callback retain the default read-only policy.
+
+## Later Capability Boundaries
+
+The v1 bridge intentionally stops at bounded JSON query results. The following
+capabilities should remain out of the runtime until the read-only query path has
+proven useful and each addition has an explicit capability contract:
+
+- `queryArrow()` or streaming query results
+- selected artifact or block context reads
+- command invocation through SQLRooms command registries
+- generated asset save/export
+- mutation or write queries with user confirmation
+- dependency bundling, import maps, or local dependency caching
+
+Those features should reuse the same request/response and diagnostic protocol
+rather than adding a second app-to-host channel.

roomie-0.1.0/node_modules/roomie-cli-app/node_modules/@sqlrooms/app-runtime/node_modules/@sqlrooms/blocks/README.md

@@ -0,0 +1,53 @@
+# @sqlrooms/blocks
+
+Shared contracts and vocabulary for composable SQLRooms blocks.
+
+Blocks are reusable units of SQLRooms workspace state or behavior. A block can
+be small and local, like a text or chart block, or stateful, like a dashboard,
+pivot table, notebook, or app surface. This package defines the shared language
+for those block-shaped resources without owning their concrete runtime.
+
+This package intentionally contains no feature runtime, stores, or UI
+implementations. Feature packages own concrete block definitions:
+
+- `@sqlrooms/mosaic` owns dashboard/chart block implementations.
+- `@sqlrooms/pivot` owns pivot block implementations.
+- `@sqlrooms/documents` owns document and rich content block implementations.
+- Notebook/canvas/app packages own their own stateful block implementations.
+
+`@sqlrooms/blocks` provides the small shared contract layer that lets those
+implementations be hosted consistently in artifacts, documents, notebooks, or
+other block containers.
+
+## Concepts
+
+- `BlockInstance` identifies a block and stores portable block attributes.
+- `BlockReference` points at state managed elsewhere and records whether that
+  state is owned, shared, or external.
+- `StatefulBlockDefinition` describes how a feature package creates, ensures,
+  renames, deletes, closes, renders, and optionally exposes settings for its
+  block state.
+- `OrderedBlockContainer` and `GraphBlockContainer` describe common container
+  shapes: linear documents and DAG-like notebooks.
+
+Concrete packages should keep their own state slices and renderers close to
+their domain. For example, dashboard blocks remain owned by `@sqlrooms/mosaic`,
+pivot blocks remain owned by `@sqlrooms/pivot`, and Markdown document blocks
+remain owned by `@sqlrooms/documents`.
+
+## Block Documents
+
+The first rich ordered block container in SQLRooms is
+[`BlockDocument`](../documents/README.md#block-documents) from
+`@sqlrooms/documents`.
+`BlockDocument` uses these shared contracts to host text, images, charts, and
+stateful blocks while keeping the editor/document runtime in the documents
+package.
+
+Use `@sqlrooms/blocks` when defining cross-package contracts for block-shaped
+resources. Use `@sqlrooms/documents` when you need the Tiptap-backed
+`BlockDocument` editor, persistence slice, commands, or AI authoring tools.
+
+See the
+[Blocks and Block Documents developer guide](https://sqlrooms.org/blocks-and-documents)
+for the ownership model and an end-to-end host setup.

roomie-0.1.0/node_modules/roomie-cli-app/node_modules/@sqlrooms/app-runtime/node_modules/@sqlrooms/blocks/node_modules/@types/react/LICENSE

@@ -0,0 +1,21 @@
+    MIT License
+
+    Copyright (c) Microsoft Corporation.
+
+    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

roomie-0.1.0/node_modules/roomie-cli-app/node_modules/@sqlrooms/app-runtime/node_modules/@sqlrooms/blocks/node_modules/@types/react/README.md

@@ -0,0 +1,15 @@
+# Installation
+> `npm install --save @types/react`
+
+# Summary
+This package contains type definitions for react (https://react.dev/).
+
+# Details
+Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react.
+
+### Additional Details
+ * Last updated: Mon, 24 Nov 2025 09:38:12 GMT
+ * Dependencies: [csstype](https://npmjs.com/package/csstype)
+
+# Credits
+These definitions were written by [Asana](https://asana.com), [AssureSign](http://www.assuresign.com), [Microsoft](https://microsoft.com), [John Reilly](https://github.com/johnnyreilly), [Benoit Benezech](https://github.com/bbenezech), [Patricio Zavolinsky](https://github.com/pzavolinsky), [Eric Anderson](https://github.com/ericanderson), [Dovydas Navickas](https://github.com/DovydasNavickas), [Josh Rutherford](https://github.com/theruther4d), [Guilherme Hübner](https://github.com/guilhermehubner), [Ferdy Budhidharma](https://github.com/ferdaber), [Johann Rakotoharisoa](https://github.com/jrakotoharisoa), [Olivier Pascal](https://github.com/pascaloliv), [Martin Hochel](https://github.com/hotell), [Frank Li](https://github.com/franklixuefei), [Jessica Franco](https://github.com/Jessidhia), [Saransh Kataria](https://github.com/saranshkataria), [Kanitkorn Sujautra](https://github.com/lukyth), [Sebastian Silbermann](https://github.com/eps1lon), [Kyle Scully](https://github.com/zieka), [Cong Zhang](https://github.com/dancerphil), [Dimitri Mitropoulos](https://github.com/dimitropoulos), [JongChan Choi](https://github.com/disjukr), [Victor Magalhães](https://github.com/vhfmag), [Priyanshu Rav](https://github.com/priyanshurav), [Dmitry Semigradsky](https://github.com/Semigradsky), and [Matt Pocock](https://github.com/mattpocock).