databricks-mason 0.1.1.dev0__tar.gz → 0.1.3.dev0__tar.gz

{databricks_mason-0.1.1.dev0 → databricks_mason-0.1.3.dev0}/PKG-INFO

@@ -1,12 +1,13 @@
 Metadata-Version: 2.5
 Name: databricks-mason
-Version: 0.1.1.dev0
+Version: 0.1.3.dev0
 Summary: Databricks integration for Mason
 Author-email: Databricks <agent-feedback@databricks.com>
 License-File: NOTICE
 Requires-Python: >=3.10
 Requires-Dist: click>=8.1
 Requires-Dist: databricks-sdk>=0.49
+Requires-Dist: psycopg[binary]>=3.1
 Requires-Dist: pyyaml>=6.0
 Requires-Dist: rich>=13.7
 Requires-Dist: tomli>=2.0
@@ -21,6 +22,14 @@ Requires-Dist: langgraph>=1.1.0; extra == 'runtime'
 Requires-Dist: mlflow>=3.10.1; extra == 'runtime'
 Requires-Dist: opentelemetry-exporter-otlp-proto-grpc>=1.25.0; extra == 'runtime'
 Requires-Dist: uuid-utils>=0.10.0; extra == 'runtime'
+Provides-Extra: runtime-openai
+Requires-Dist: databricks-agents>=1.9.3; extra == 'runtime-openai'
+Requires-Dist: databricks-openai>=0.13.0; extra == 'runtime-openai'
+Requires-Dist: fastapi>=0.129.0; extra == 'runtime-openai'
+Requires-Dist: mlflow>=3.10.1; extra == 'runtime-openai'
+Requires-Dist: openai-agents>=0.7.0; extra == 'runtime-openai'
+Requires-Dist: opentelemetry-exporter-otlp-proto-grpc>=1.25.0; extra == 'runtime-openai'
+Requires-Dist: uuid-utils>=0.10.0; extra == 'runtime-openai'
 Provides-Extra: tracing
 Requires-Dist: mlflow[databricks]>=3.9.0; extra == 'tracing'
 Description-Content-Type: text/markdown
@@ -53,23 +62,31 @@ For tracing commands, install Mason with tracing extras:
 pip install 'databricks-mason[tracing]'
 ```
 
+## Shell completion
+Add this to `~/.zshrc`:
+```sh
+eval "$(_MASON_COMPLETE=zsh_source mason)"
+```
+
 ## Authentication
 
 Mason uses [Databricks authentication](https://docs.databricks.com/aws/en/dev-tools/cli/authentication).
-If you do not already have credentials, authenticate a named profile first. You can
-then ask Mason to validate and remember that profile:
+Ask Mason to authenticate and remember a named profile:
 
 ```sh
-databricks auth login --profile <profile>
 mason login --profile <profile>
 mason sessions stores list
 ```
 
-`mason login` does not create credentials; it stores the selected profile in
-`~/.mason/config.json`. `mason logout` forgets that selection without revoking the
-underlying credentials. If Databricks SDK default authentication is already configured,
-you can skip `mason login`. You can also pass `--profile/-p` for an individual command.
-Use `--output json` for scripting.
+`mason login` validates existing credentials first. If credentials are missing or rejected in
+an interactive terminal, Mason runs `databricks auth login --profile <profile>`, revalidates the
+profile, and stores the selection in `~/.mason/config.json`. This browser-based setup requires
+the Databricks CLI. In non-interactive environments, authenticate the profile before running
+Mason. `mason logout` forgets the saved selection without revoking the underlying credentials.
+
+If Databricks SDK default authentication is already configured, you can skip `mason login`.
+You can also pass the global `--profile/-p` option before an individual command, for example
+`mason --profile <profile> mcp list`. Use `--output json` for scripting.
 
 ## Python SDK
 
@@ -102,8 +119,11 @@ accessors (`store.name`) while remaining plain dicts underneath — so `store["n
 mason [-p <profile>] [-o text|json]
   login        [--profile P]
   logout
-  init         [--framework openai|langgraph] [--enable-chat-app]
+  init         [--framework openai|langgraph] [--disable-chat-app]
                [--profile P] [--repo URL] [--ref REF] [directory]
+  dev          [--source PATH] [--prepare-environment] [--app-port PORT]
+               [--memory/-m N] [--session/-s N]
+               [--with-traces C.S] [--no-create-stores]
   memory
     stores     create | list | get | update | delete
     entries    create | get | list | search | update | delete
@@ -115,19 +135,39 @@ mason [-p <profile>] [-o text|json]
     list | get | instrument
   mcp
     list             [--schema CATALOG.SCHEMA]
-  init          [--framework openai|langgraph] [--profile P] [DIRECTORY]
   tools
     add sandbox      --scope SCOPE [--scope SCOPE ...] [--source PATH]
     add mcp          SERVICE [--name NAME] [--source PATH]
     add uc-function  FUNCTION [--name NAME] [--source PATH]
     add python       NAME [--source PATH]
     list             [--source PATH]
-  deploy       <name> --source PATH [--with-memory-store N]
-               [--with-session-store N] [--actor-id ID]
-               [--with-traces C.S] [--create-stores]
+  deploy       <name> --source PATH [--memory/-m N]
+               [--session/-s N] [--actor-id ID]
+               [--with-traces C.S] [--no-create-stores]
   deployments  list | get | logs | start | stop | delete
 ```
 
+## Command help
+
+Use the conventional help flag at any command level. Every command's help includes runnable
+examples:
+
+```sh
+mason --help
+mason deploy --help
+mason sessions items append --help
+```
+
+For the shortest path from a blank directory to a running and deployed agent:
+
+```sh
+mason login --profile <profile>
+mason init my-agent
+cd my-agent
+mason dev
+mason deploy my-agent
+```
+
 ## Agent tools
 
 `mason init` writes portable tool intent to `agent.toml` and template provenance to
@@ -144,9 +184,14 @@ mason tools add sandbox --scope table:samples.nyctaxi.trips
 mason tools add mcp system.ai.web_search
 mason tools add uc-function catalog.schema.lookup_ticket
 mason tools add python lookup-ticket
+mason tools remove mcp system.ai.web_search
 mason tools list
 ```
 
+For MCP services, the remove command accepts the same service name as the add command. You can also
+remove any binding by the ID shown in `mason tools list`, for example `mason tools remove
+web_search`. Removal updates only `agent.toml`; Python source and test files remain user-owned.
+
 Discover the MCP Services available to your user before adding one. By default Mason lists the
 Databricks-managed services in `system.ai`; pass `--schema catalog.schema` for another Unity Catalog
 schema. Text output includes a copyable add command, while `--output json` returns normalized service
@@ -168,49 +213,39 @@ arguments controlled by the model.
 
 ## Initialize the chat app demo
 
-The chat app is a LangGraph-specific init overlay, not a command that mutates an existing project:
+The chat app is a LangGraph-specific init overlay, not a command that mutates an existing project.
+It is included by default for `--framework langgraph`; pass `--disable-chat-app` to scaffold the
+API-only backend instead.
 
 ```sh
-mason init --framework langgraph --enable-chat-app \
+mason init --framework langgraph \
   --profile <profile> \
   ./my-agent
 cd ./my-agent
 uv run start-server
 ```
 
-`--enable-chat-app` always includes synchronous, SSE streaming, background polling, Session Store,
-Memory Store, HITL resume, Start App, Stop App, heartbeat, and recovery UI. There are no separate
-stop/crash flags. The base agent owns `agent/mason/durability.py`, `agent/mason/recovery.py`, and
-`agent/mason/long_running.py`; the framework-specific overlay only adds `ui/`, `runtime/ui.py`, the
-UI-enabled `runtime/main.py`, and UI tests.
+The chat app includes synchronous, SSE streaming, background polling, Session Store, Memory Store,
+and HITL resume UI. The framework-specific overlay adds `ui/`, `runtime/ui.py`, the UI-enabled
+`runtime/main.py`, and UI tests.
 
 For the full deployed demo, connect both managed stores:
 
 ```sh
 mason --profile <profile> deploy mason-agent-demo --source . \
-  --with-session-store mason-demo-sessions \
-  --with-memory-store mason-demo-memory \
-  --actor-id alice \
-  --create-stores
+  --session mason-demo-sessions \
+  --memory mason-demo-memory \
+  --actor-id alice
 ```
 
+(Missing stores are created automatically; pass `--no-create-stores` to require they already exist.)
+
 The Databricks Apps `__Host-databricks-app-router` cookie is both the sticky routing key and the
 application session id. The browser sends it automatically; API clients must reuse it as a cookie.
 Request bodies never carry `session_id`. A localhost-only `mason-local-session` cookie provides the
 same behavior outside Databricks Apps. TODO: move to `X-Routing-Key` when Apps supports it.
 
 The generated `README.md` documents every request the client makes: config discovery, sync and SSE
-invocations, background submission and polling, session transcript loading, HITL resume, memory
-entry operations, and stop/start recovery. Capability colors are automatic from `/api/demo/config`;
-only the sync/streaming/background transport selector is manual.
-
-Start App runs `tool_step_1` through `tool_step_4` in a checkpointed sequence. Each completed output
-is committed before the next node. Stop App schedules `os._exit(86)`; Databricks Apps restarts the
-process, the browser waits for a new instance and a stale heartbeat, and then starts a new attempt
-with the same routing cookie. Completed tools are restored and skipped; an interrupted tool whose
-output was not committed can run again.
-
-The ownership log is intentionally demo-grade: Session Store records append-only attempts and
-heartbeats, but the claim is last-writer-wins rather than atomic (`atomic_claim: false`). Production
-durability also needs transactional ownership, server-side stale scanning, idempotent side effects,
-and durable event replay.
+invocations, background submission and polling, session transcript loading, HITL resume, and memory
+entry operations. Capability colors are automatic from `/api/demo/config`; only the
+sync/streaming/background transport selector is manual.

{databricks_mason-0.1.1.dev0 → databricks_mason-0.1.3.dev0}/README.md

@@ -26,23 +26,31 @@ For tracing commands, install Mason with tracing extras:
 pip install 'databricks-mason[tracing]'
 ```
 
+## Shell completion
+Add this to `~/.zshrc`:
+```sh
+eval "$(_MASON_COMPLETE=zsh_source mason)"
+```
+
 ## Authentication
 
 Mason uses [Databricks authentication](https://docs.databricks.com/aws/en/dev-tools/cli/authentication).
-If you do not already have credentials, authenticate a named profile first. You can
-then ask Mason to validate and remember that profile:
+Ask Mason to authenticate and remember a named profile:
 
 ```sh
-databricks auth login --profile <profile>
 mason login --profile <profile>
 mason sessions stores list
 ```
 
-`mason login` does not create credentials; it stores the selected profile in
-`~/.mason/config.json`. `mason logout` forgets that selection without revoking the
-underlying credentials. If Databricks SDK default authentication is already configured,
-you can skip `mason login`. You can also pass `--profile/-p` for an individual command.
-Use `--output json` for scripting.
+`mason login` validates existing credentials first. If credentials are missing or rejected in
+an interactive terminal, Mason runs `databricks auth login --profile <profile>`, revalidates the
+profile, and stores the selection in `~/.mason/config.json`. This browser-based setup requires
+the Databricks CLI. In non-interactive environments, authenticate the profile before running
+Mason. `mason logout` forgets the saved selection without revoking the underlying credentials.
+
+If Databricks SDK default authentication is already configured, you can skip `mason login`.
+You can also pass the global `--profile/-p` option before an individual command, for example
+`mason --profile <profile> mcp list`. Use `--output json` for scripting.
 
 ## Python SDK
 
@@ -75,8 +83,11 @@ accessors (`store.name`) while remaining plain dicts underneath — so `store["n
 mason [-p <profile>] [-o text|json]
   login        [--profile P]
   logout
-  init         [--framework openai|langgraph] [--enable-chat-app]
+  init         [--framework openai|langgraph] [--disable-chat-app]
                [--profile P] [--repo URL] [--ref REF] [directory]
+  dev          [--source PATH] [--prepare-environment] [--app-port PORT]
+               [--memory/-m N] [--session/-s N]
+               [--with-traces C.S] [--no-create-stores]
   memory
     stores     create | list | get | update | delete
     entries    create | get | list | search | update | delete
@@ -88,19 +99,39 @@ mason [-p <profile>] [-o text|json]
     list | get | instrument
   mcp
     list             [--schema CATALOG.SCHEMA]
-  init          [--framework openai|langgraph] [--profile P] [DIRECTORY]
   tools
     add sandbox      --scope SCOPE [--scope SCOPE ...] [--source PATH]
     add mcp          SERVICE [--name NAME] [--source PATH]
     add uc-function  FUNCTION [--name NAME] [--source PATH]
     add python       NAME [--source PATH]
     list             [--source PATH]
-  deploy       <name> --source PATH [--with-memory-store N]
-               [--with-session-store N] [--actor-id ID]
-               [--with-traces C.S] [--create-stores]
+  deploy       <name> --source PATH [--memory/-m N]
+               [--session/-s N] [--actor-id ID]
+               [--with-traces C.S] [--no-create-stores]
   deployments  list | get | logs | start | stop | delete
 ```
 
+## Command help
+
+Use the conventional help flag at any command level. Every command's help includes runnable
+examples:
+
+```sh
+mason --help
+mason deploy --help
+mason sessions items append --help
+```
+
+For the shortest path from a blank directory to a running and deployed agent:
+
+```sh
+mason login --profile <profile>
+mason init my-agent
+cd my-agent
+mason dev
+mason deploy my-agent
+```
+
 ## Agent tools
 
 `mason init` writes portable tool intent to `agent.toml` and template provenance to
@@ -117,9 +148,14 @@ mason tools add sandbox --scope table:samples.nyctaxi.trips
 mason tools add mcp system.ai.web_search
 mason tools add uc-function catalog.schema.lookup_ticket
 mason tools add python lookup-ticket
+mason tools remove mcp system.ai.web_search
 mason tools list
 ```
 
+For MCP services, the remove command accepts the same service name as the add command. You can also
+remove any binding by the ID shown in `mason tools list`, for example `mason tools remove
+web_search`. Removal updates only `agent.toml`; Python source and test files remain user-owned.
+
 Discover the MCP Services available to your user before adding one. By default Mason lists the
 Databricks-managed services in `system.ai`; pass `--schema catalog.schema` for another Unity Catalog
 schema. Text output includes a copyable add command, while `--output json` returns normalized service
@@ -141,49 +177,39 @@ arguments controlled by the model.
 
 ## Initialize the chat app demo
 
-The chat app is a LangGraph-specific init overlay, not a command that mutates an existing project:
+The chat app is a LangGraph-specific init overlay, not a command that mutates an existing project.
+It is included by default for `--framework langgraph`; pass `--disable-chat-app` to scaffold the
+API-only backend instead.
 
 ```sh
-mason init --framework langgraph --enable-chat-app \
+mason init --framework langgraph \
   --profile <profile> \
   ./my-agent
 cd ./my-agent
 uv run start-server
 ```
 
-`--enable-chat-app` always includes synchronous, SSE streaming, background polling, Session Store,
-Memory Store, HITL resume, Start App, Stop App, heartbeat, and recovery UI. There are no separate
-stop/crash flags. The base agent owns `agent/mason/durability.py`, `agent/mason/recovery.py`, and
-`agent/mason/long_running.py`; the framework-specific overlay only adds `ui/`, `runtime/ui.py`, the
-UI-enabled `runtime/main.py`, and UI tests.
+The chat app includes synchronous, SSE streaming, background polling, Session Store, Memory Store,
+and HITL resume UI. The framework-specific overlay adds `ui/`, `runtime/ui.py`, the UI-enabled
+`runtime/main.py`, and UI tests.
 
 For the full deployed demo, connect both managed stores:
 
 ```sh
 mason --profile <profile> deploy mason-agent-demo --source . \
-  --with-session-store mason-demo-sessions \
-  --with-memory-store mason-demo-memory \
-  --actor-id alice \
-  --create-stores
+  --session mason-demo-sessions \
+  --memory mason-demo-memory \
+  --actor-id alice
 ```
 
+(Missing stores are created automatically; pass `--no-create-stores` to require they already exist.)
+
 The Databricks Apps `__Host-databricks-app-router` cookie is both the sticky routing key and the
 application session id. The browser sends it automatically; API clients must reuse it as a cookie.
 Request bodies never carry `session_id`. A localhost-only `mason-local-session` cookie provides the
 same behavior outside Databricks Apps. TODO: move to `X-Routing-Key` when Apps supports it.
 
 The generated `README.md` documents every request the client makes: config discovery, sync and SSE
-invocations, background submission and polling, session transcript loading, HITL resume, memory
-entry operations, and stop/start recovery. Capability colors are automatic from `/api/demo/config`;
-only the sync/streaming/background transport selector is manual.
-
-Start App runs `tool_step_1` through `tool_step_4` in a checkpointed sequence. Each completed output
-is committed before the next node. Stop App schedules `os._exit(86)`; Databricks Apps restarts the
-process, the browser waits for a new instance and a stale heartbeat, and then starts a new attempt
-with the same routing cookie. Completed tools are restored and skipped; an interrupted tool whose
-output was not committed can run again.
-
-The ownership log is intentionally demo-grade: Session Store records append-only attempts and
-heartbeats, but the claim is last-writer-wins rather than atomic (`atomic_claim: false`). Production
-durability also needs transactional ownership, server-side stale scanning, idempotent side effects,
-and durable event replay.
+invocations, background submission and polling, session transcript loading, HITL resume, and memory
+entry operations. Capability colors are automatic from `/api/demo/config`; only the
+sync/streaming/background transport selector is manual.

{databricks_mason-0.1.1.dev0 → databricks_mason-0.1.3.dev0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "databricks-mason"
-version = "0.1.1.dev0"
+version = "0.1.3.dev0"
 description = "Databricks integration for Mason"
 authors = [
     { name="Databricks", email="agent-feedback@databricks.com" },
@@ -10,6 +10,7 @@ requires-python = ">=3.10"
 dependencies = [
     "click>=8.1",
     "databricks-sdk>=0.49",
+    "psycopg[binary]>=3.1",
     "PyYAML>=6.0",
     "rich>=13.7",
     "tomli>=2.0",
@@ -20,9 +21,11 @@ dependencies = [
 tracing = [
     "mlflow[databricks]>=3.9.0",
 ]
-# The agent-side runtime helpers (databricks_mason.runtime) that a deployed agent imports. Kept as
-# an extra so a plain `pip install databricks-mason` (the CLI) stays light; the template depends on
-# `databricks-mason[runtime]`.
+# The agent-side runtime helpers a deployed agent imports. Kept as extras so a plain
+# `pip install databricks-mason` (the CLI) stays light; each template depends on the extra for its
+# framework. `runtime` = the LangGraph adapter (databricks_mason.langgraph); `runtime-openai` = the
+# OpenAI Agents SDK adapter (databricks_mason.openai). Both carry the shared framework-neutral stack
+# (databricks_mason.runtime); the framework SDKs differ, so an agent installs only the one it uses.
 runtime = [
     "databricks-langchain>=0.17.0",
     "langgraph>=1.1.0",
@@ -34,6 +37,15 @@ runtime = [
     "opentelemetry-exporter-otlp-proto-grpc>=1.25.0",
     "databricks-agents>=1.9.3",
 ]
+runtime-openai = [
+    "openai-agents>=0.7.0",
+    "databricks-openai>=0.13.0",
+    "fastapi>=0.129.0",
+    "mlflow>=3.10.1",
+    "uuid-utils>=0.10.0",
+    "opentelemetry-exporter-otlp-proto-grpc>=1.25.0",
+    "databricks-agents>=1.9.3",
+]
 
 [project.scripts]
 mason = "databricks_mason.cli:main"

{databricks_mason-0.1.1.dev0 → databricks_mason-0.1.3.dev0}/src/databricks_mason/agent_project.py

@@ -15,6 +15,7 @@ from tomlkit import TOMLDocument
 from tomlkit.exceptions import ParseError
 
 from databricks_mason.errors import AgentCliError
+from databricks_mason.runtime.tool_manifest import MEMORY_STORE_TABLE, SESSION_STORE_TABLE
 
 _SCHEMA_VERSION = 1
 _SUPPORTED_FRAMEWORKS = {"langgraph", "openai"}
@@ -191,6 +192,15 @@ def _required_string(value: object, description: str) -> str:
     return value
 
 
+def _store_name_from_manifest(value: object, table: str) -> str | None:
+    """Read the ``name`` from a ``[memory_store]`` / ``[session_store]`` table, or None if absent."""
+    if value is None:
+        return None
+    if not isinstance(value, Mapping):
+        raise AgentCliError(f"agent.toml [{table}] must be a table.")
+    return _required_string(cast(Mapping[str, Any], value).get("name"), f"[{table}] name")
+
+
 def _scope_from_manifest(value: object) -> Scope:
     if not isinstance(value, Mapping):
         raise AgentCliError("Sandbox downscope entries must be TOML tables.")
@@ -275,12 +285,17 @@ class AgentProject:
         document: TOMLDocument,
         framework: str,
         tools: list[ToolSpec],
+        memory_store: str | None = None,
+        session_store: str | None = None,
     ) -> None:
         self.root = root
         self.path = root / "agent.toml"
         self._document = document
         self.framework = framework
         self.tools = tools
+        # Managed store bindings declared in agent.toml; None = unbound.
+        self.memory_store = memory_store
+        self.session_store = session_store
 
     @classmethod
     def load(cls, root: pathlib.Path | str) -> "AgentProject":
@@ -291,7 +306,8 @@ class AgentProject:
         except FileNotFoundError as exc:
             raise AgentCliError(
                 f"Could not find agent.toml in {project_root}.",
-                hint="Run `mason init` or use a legacy compatibility command.",
+                hint="This command needs a Mason project. Run `mason init` to create one, "
+                "or point at an existing project with --source <dir>.",
             ) from exc
         except (OSError, ParseError) as exc:
             raise AgentCliError(f"Could not read agent manifest at {path}: {exc}.") from exc
@@ -313,7 +329,13 @@ class AgentProject:
         ids = [tool.id for tool in tools]
         if len(ids) != len(set(ids)):
             raise AgentCliError("agent.toml tool ids must be unique.")
-        return cls(project_root, document, framework, tools)
+        memory_store = _store_name_from_manifest(
+            document.get(MEMORY_STORE_TABLE), MEMORY_STORE_TABLE
+        )
+        session_store = _store_name_from_manifest(
+            document.get(SESSION_STORE_TABLE), SESSION_STORE_TABLE
+        )
+        return cls(project_root, document, framework, tools, memory_store, session_store)
 
     @classmethod
     def create(cls, root: pathlib.Path | str, *, framework: str) -> "AgentProject":
@@ -334,7 +356,17 @@ class AgentProject:
                 continue
             if existing == spec:
                 return False
-            raise AgentCliError(f"Tool id {spec.id!r} already exists with different configuration.")
+
+            def _summary(s: ToolSpec) -> str:
+                src = s.source
+                return src.service or src.function or src.entrypoint or src.kind
+
+            raise AgentCliError(
+                f"Tool id {spec.id!r} already exists with a different configuration "
+                f"(existing: {_summary(existing)}; requested: {_summary(spec)}).",
+                hint="Use --name to add it under a different id, or remove the existing "
+                "tool from agent.toml first.",
+            )
         raw_tools = self._document.get("tools")
         if raw_tools is None:
             raw_tools = tomlkit.aot()
@@ -356,6 +388,44 @@ class AgentProject:
         del self.tools[index]
         return True
 
+    def bind_memory_store(self, name: str) -> bool:
+        """Declare the memory store binding in agent.toml. Returns True if it changed."""
+        return self._set_store(MEMORY_STORE_TABLE, name)
+
+    def bind_session_store(self, name: str) -> bool:
+        """Declare the session store binding in agent.toml. Returns True if it changed."""
+        return self._set_store(SESSION_STORE_TABLE, name)
+
+    def unbind_memory_store(self) -> bool:
+        """Remove the memory store binding from agent.toml. Returns True if it was present."""
+        return self._clear_store(MEMORY_STORE_TABLE)
+
+    def unbind_session_store(self) -> bool:
+        """Remove the session store binding from agent.toml. Returns True if it was present."""
+        return self._clear_store(SESSION_STORE_TABLE)
+
+    def _set_store(self, table: str, name: str) -> bool:
+        name = _required_string(name, f"[{table}] name")
+        if getattr(self, table) == name:
+            return False
+        existing = self._document.get(table)
+        if isinstance(existing, Mapping):
+            existing["name"] = name
+        else:
+            store_table = tomlkit.table()
+            store_table.add("name", name)
+            self._document.append(table, store_table)
+        setattr(self, table, name)
+        return True
+
+    def _clear_store(self, table: str) -> bool:
+        if getattr(self, table) is None:
+            return False
+        if table in self._document:
+            del self._document[table]
+        setattr(self, table, None)
+        return True
+
     def write(self) -> pathlib.Path:
         self.path.parent.mkdir(parents=True, exist_ok=True)
         temporary: pathlib.Path | None = None