deepcell-cli 0.6.3__tar.gz → 0.7.0__tar.gz

{deepcell_cli-0.6.3 → deepcell_cli-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deepcell-cli
-Version: 0.6.3
+Version: 0.7.0
 Summary: Build and revise .deepcell documents from a terminal — the reasoning, the calculations, the document and the deck, with the links between them
 Author-email: DeepCell <hello@deepcell.net>
 License-Expression: MIT
@@ -71,6 +71,30 @@ landed in a directory that is off `PATH` — not that the install failed. Re-run
 the installer above, which fixes exactly that; or use `python3 -m deepcell_cli`
 (`python -m` on Windows), which is the same CLI with no `PATH` involved.
 
+More generally, a bare `deepcell` failing is not "not installed". It means one
+of four things, and only one is fixed by installing: nothing is installed; a
+copy exists in a directory that is off `PATH`; a copy exists and the host — a
+sandbox, a policy — refuses to execute it; a copy exists, runs, and is behind.
+The installer tells them apart: it looks on `PATH` *and* where an install
+lands, runs what it finds by absolute path, keeps a current copy, upgrades an
+outdated one, puts an off-`PATH` one on `PATH`, and refuses to reinstall one
+the host will not run (reinstalling would not change that). Its last line on
+stderr is one a script reads —
+`deepcell-install: state=<state> version=<version> dir=<directory>` — where
+`state` is `installed`, `upgraded`, `reinstalled`, `installed-current`,
+`installed-unknown` (it runs; the package index could not be reached),
+`installed-blocked` (exit 3) or `failed`. An upgrade goes through the tool
+that owns the copy — uv when `uv tool list` names it, else pip. stdout is
+still just the directory.
+`DEEPCELL_FORCE=1` is the repair path: reinstall even when current. On Windows,
+a `PATH` the installer writes reaches new sessions only; a host that is already
+running keeps its environment, so use the directory the installer returns:
+
+```powershell
+$bin = irm https://deepcell.net/install.ps1 | iex
+& (Join-Path $bin 'deepcell.exe') --version
+```
+
 ## Designed for agents
 
 The CLI is built to be driven programmatically:

{deepcell_cli-0.6.3 → deepcell_cli-0.7.0}/README.md

@@ -39,6 +39,30 @@ landed in a directory that is off `PATH` — not that the install failed. Re-run
 the installer above, which fixes exactly that; or use `python3 -m deepcell_cli`
 (`python -m` on Windows), which is the same CLI with no `PATH` involved.
 
+More generally, a bare `deepcell` failing is not "not installed". It means one
+of four things, and only one is fixed by installing: nothing is installed; a
+copy exists in a directory that is off `PATH`; a copy exists and the host — a
+sandbox, a policy — refuses to execute it; a copy exists, runs, and is behind.
+The installer tells them apart: it looks on `PATH` *and* where an install
+lands, runs what it finds by absolute path, keeps a current copy, upgrades an
+outdated one, puts an off-`PATH` one on `PATH`, and refuses to reinstall one
+the host will not run (reinstalling would not change that). Its last line on
+stderr is one a script reads —
+`deepcell-install: state=<state> version=<version> dir=<directory>` — where
+`state` is `installed`, `upgraded`, `reinstalled`, `installed-current`,
+`installed-unknown` (it runs; the package index could not be reached),
+`installed-blocked` (exit 3) or `failed`. An upgrade goes through the tool
+that owns the copy — uv when `uv tool list` names it, else pip. stdout is
+still just the directory.
+`DEEPCELL_FORCE=1` is the repair path: reinstall even when current. On Windows,
+a `PATH` the installer writes reaches new sessions only; a host that is already
+running keeps its environment, so use the directory the installer returns:
+
+```powershell
+$bin = irm https://deepcell.net/install.ps1 | iex
+& (Join-Path $bin 'deepcell.exe') --version
+```
+
 ## Designed for agents
 
 The CLI is built to be driven programmatically:

{deepcell_cli-0.6.3 → deepcell_cli-0.7.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "deepcell-cli"
-version = "0.6.3"
+version = "0.7.0"
 description = "Build and revise .deepcell documents from a terminal — the reasoning, the calculations, the document and the deck, with the links between them"
 readme = "README.md"
 license = "MIT"

{deepcell_cli-0.6.3 → deepcell_cli-0.7.0}/src/deepcell_cli/__init__.py

@@ -9,4 +9,4 @@ same thing, and a third is stamped into ``docs/cli-surface.json`` by
 reports a version it is not, and skipping the regen lands a red build.
 """
 
-__version__ = "0.6.3"
+__version__ = "0.7.0"

{deepcell_cli-0.6.3 → deepcell_cli-0.7.0}/src/deepcell_cli/capabilities.py

@@ -62,6 +62,7 @@ MCP_ALLOWED_COMMANDS = frozenset(
         "rm",
         "rules",
         "share",
+        "verify-import",
         "viewer",
         "whoami",
         # `workspace` is the pre-rename spelling of `project` — a hidden alias
@@ -109,7 +110,7 @@ MCP_BLOCKED_COMMANDS: dict[str, dict[str, str]] = {
     },
     "push": {
         "reason": "local_checkout",
-        "detail": "reads and uploads files from a local Git working copy",
+        "detail": "reads and sends files from a local Git working copy",
     },
     "register": {
         "reason": "interactive_auth",
@@ -160,16 +161,34 @@ MCP_BLOCKED_COMMANDS: dict[str, dict[str, str]] = {
 # ``deepcell_tool._COMMANDS`` remains the parser/dispatcher implementation.
 IN_PROCESS_COMMANDS = frozenset(
     {
+        "assumption impact",
         "cat",
+        "claim falsified",
+        "claim variant",
         "defs apply",
+        "defs list",
+        "defs show",
         "describe",
+        # The read-only checks and analyses the guides name (#2083): the
+        # hosted agent could read the guide and not run them. Writes stay
+        # `defs apply` ops; history stays the `git` tool.
+        "doc backlinks",
+        "doc blocks",
+        "doc links",
+        "doc lint",
         "example",
         "guide",
         "help",
+        "import",
         "ls",
         "query",
+        "reasoning graph",
+        "reasoning impact",
+        "reasoning lint",
         "ref",
+        "relationships",
         "rules",
+        "verify-import",
     }
 )
 
@@ -238,6 +257,7 @@ ENDPOINT_COMMANDS: dict[str, tuple[str, ...]] = {
     "query_deepcell_query_post": ("query",),
     "get_relationships_relationships_post": ("relationships",),
     "document_backlinks_document_backlinks_post": ("doc backlinks",),
+    "document_render_block_document_render_block_post": ("doc render-block",),
     "impact_impact_post": ("impact show",),
     "review_impact_review_post": ("impact review",),
     "apply_impact_apply_post": ("impact apply",),
@@ -281,6 +301,7 @@ ENDPOINT_COMMANDS: dict[str, tuple[str, ...]] = {
 
     # Import, ingestion, and export.
     "import_file_import_post": ("import",),
+    "verify_import_file_import_verify_post": ("verify-import",),
     "cn_extract_ingest_cn_extract_get": ("ingest cn extract",),
     "cn_filings_ingest_cn_filings_get": ("ingest cn filings",),
     "cn_search_ingest_cn_search_get": ("ingest cn search",),
@@ -396,6 +417,7 @@ ENDPOINT_EXCEPTIONS: dict[str, tuple[str, str]] = {
     "version_info_version_get": ("service_metadata", "frontend/service version probe; CLI reports its installed version locally"),
     "clear_cache_cache_clear_post": ("internal_ops", "operator-only cache maintenance"),
     "get_cache_stats_cache_stats_get": ("internal_ops", "operator-only cache diagnostics"),
+    "build_queue_health_health_build_queue_get": ("internal_ops", "build-queue lane depths and counters, for the load harness and a dashboard"),
     "record_unknown_command_cli_unknown_commands_post": ("implicit_client", "CLI telemetry emitted automatically, never invoked directly"),
     "record_web_events_signals_web_post": ("frontend_only", "browser analytics collector"),
     "create_demo_session_demo_session_post": ("implicit_client", "anonymous CLI session bootstrap performed by DeepCellClient"),