ventilatepro-cli 0.3.1__tar.gz → 0.5.0__tar.gz

{ventilatepro_cli-0.3.1 → ventilatepro_cli-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ventilatepro-cli
-Version: 0.3.1
+Version: 0.5.0
 Summary: VentilatePro CLI
 Project-URL: Homepage, https://ventilatepro.com/exam/cli/
 Project-URL: Documentation, https://ventilatepro.com/exam/cli/
@@ -11,11 +11,11 @@ Requires-Dist: typer>=0.16.0
 Requires-Dist: requests>=2.32.0
 Requires-Dist: keyring>=25.6.0
 Requires-Dist: platformdirs>=4.3.0
-Requires-Dist: mcp>=1.23.0
+Requires-Dist: mcp<2.0.0,>=1.23.0
 
 # VentilatePro CLI
 
-VentilatePro CLI is a local command-line client for authenticating to VentilatePro and creating or syncing notes through the scoped CLI API.
+VentilatePro CLI is a local command-line client for authenticating to VentilatePro, recording project notes and meeting minutes, and running scoped engineering workflows.
 
 ## Install
 
@@ -45,6 +45,12 @@ ventilatepro auth login
 ventilatepro projects list
 ventilatepro projects show 1
 ventilatepro rooms list --project 1
+ventilatepro room-equipment summary --project 1
+ventilatepro room-equipment create --data '{"room": 501, "name": "Sterilizer", "heat_gain_value": 1.8, "heat_gain_unit": "KW"}'
+ventilatepro revit-imports review --project 1 --json
+ventilatepro revit-imports confirm 41 --project 1 --review-token <token-from-review> --yes
+ventilatepro categorization review --project 1 --output room-categorization.json
+ventilatepro categorization apply --project 1 --input room-categorization.json --yes
 ventilatepro ahus list --project 1
 ventilatepro systems hierarchy --project 1
 ventilatepro calc status --project 1
@@ -52,6 +58,9 @@ ventilatepro calc ahu-properties --ahu 1
 ventilatepro design-day context --project 1
 ventilatepro notes create --project 1 --body "Captured from terminal"
 ventilatepro notes sync
+ventilatepro meetings context --project 1 --json
+ventilatepro meetings record --project 1 --input meeting.json --json
+ventilatepro meetings list --project 1
 ventilatepro mcp doctor
 ventilatepro-mcp
 ```
@@ -60,6 +69,21 @@ ventilatepro-mcp
 and other MCP clients. It uses the same saved base URL and CLI token created by
 `ventilatepro auth login`.
 
+For meeting capture, Codex first reads `meetings context` to resolve names to
+stable project-member IDs, interprets the PM's prose into a structured JSON
+payload, and calls `meetings record`. The server atomically creates the meeting,
+decisions, and assigned project tasks and returns a direct web-app link.
+
+For room classification, Codex can read the project-specific categorization
+review resource or use the dedicated MCP tools. Review manifests default every
+room to rejected so ambiguous spaces remain visible until a category is
+explicitly accepted with a reason.
+
+For staged Revit imports, agents use `revit-imports review` or
+`vp_review_revit_import` first. The returned review token identifies the exact
+payload and diff that was inspected. Confirmation requires that unchanged token
+plus explicit `--yes` or MCP `confirm=true`; stale reviews are rejected.
+
 ## MCP setup
 
 1. In the VentilatePro web app, open Account Settings and create a CLI token with

{ventilatepro_cli-0.3.1 → ventilatepro_cli-0.5.0}/README.md

@@ -1,6 +1,6 @@
 # VentilatePro CLI
 
-VentilatePro CLI is a local command-line client for authenticating to VentilatePro and creating or syncing notes through the scoped CLI API.
+VentilatePro CLI is a local command-line client for authenticating to VentilatePro, recording project notes and meeting minutes, and running scoped engineering workflows.
 
 ## Install
 
@@ -30,6 +30,12 @@ ventilatepro auth login
 ventilatepro projects list
 ventilatepro projects show 1
 ventilatepro rooms list --project 1
+ventilatepro room-equipment summary --project 1
+ventilatepro room-equipment create --data '{"room": 501, "name": "Sterilizer", "heat_gain_value": 1.8, "heat_gain_unit": "KW"}'
+ventilatepro revit-imports review --project 1 --json
+ventilatepro revit-imports confirm 41 --project 1 --review-token <token-from-review> --yes
+ventilatepro categorization review --project 1 --output room-categorization.json
+ventilatepro categorization apply --project 1 --input room-categorization.json --yes
 ventilatepro ahus list --project 1
 ventilatepro systems hierarchy --project 1
 ventilatepro calc status --project 1
@@ -37,6 +43,9 @@ ventilatepro calc ahu-properties --ahu 1
 ventilatepro design-day context --project 1
 ventilatepro notes create --project 1 --body "Captured from terminal"
 ventilatepro notes sync
+ventilatepro meetings context --project 1 --json
+ventilatepro meetings record --project 1 --input meeting.json --json
+ventilatepro meetings list --project 1
 ventilatepro mcp doctor
 ventilatepro-mcp
 ```
@@ -45,6 +54,21 @@ ventilatepro-mcp
 and other MCP clients. It uses the same saved base URL and CLI token created by
 `ventilatepro auth login`.
 
+For meeting capture, Codex first reads `meetings context` to resolve names to
+stable project-member IDs, interprets the PM's prose into a structured JSON
+payload, and calls `meetings record`. The server atomically creates the meeting,
+decisions, and assigned project tasks and returns a direct web-app link.
+
+For room classification, Codex can read the project-specific categorization
+review resource or use the dedicated MCP tools. Review manifests default every
+room to rejected so ambiguous spaces remain visible until a category is
+explicitly accepted with a reason.
+
+For staged Revit imports, agents use `revit-imports review` or
+`vp_review_revit_import` first. The returned review token identifies the exact
+payload and diff that was inspected. Confirmation requires that unchanged token
+plus explicit `--yes` or MCP `confirm=true`; stale reviews are rejected.
+
 ## MCP setup
 
 1. In the VentilatePro web app, open Account Settings and create a CLI token with

{ventilatepro_cli-0.3.1 → ventilatepro_cli-0.5.0}/pyproject.toml

@@ -13,7 +13,7 @@ dependencies = [
   "requests>=2.32.0",
   "keyring>=25.6.0",
   "platformdirs>=4.3.0",
-  "mcp>=1.23.0",
+  "mcp>=1.23.0,<2.0.0",
 ]
 
 [project.urls]