impreza-mcp 0.45.0 → 0.46.0

package/README.md

@@ -268,24 +268,23 @@ Static npm sites: choose build_strategy=node_npm_static with a Git/context sourc
 
 ## Status
 
-**Package version: 0.38.0.** The tool catalog covers app deployment plus account +
+**Package version: 0.46.0.** The tool catalog covers app deployment plus account +
 crypto balance, catalog + ordering, domains/DNS + registration, invoices, VPS
 lifecycle with snapshots and backups, dedicated / bare-metal servers, plan
 upgrades, and Titan / Google Workspace mailboxes — with a setup wizard that
 generates ready-to-paste config snippets for 5 AI tools.
 
-On top of that, everything an app needs after it is running: backup and
-restore into the customer's **own** S3 bucket, a timer on an app with its
-output kept, outbound webhooks so you stop polling, and reading the app's own
-files to find out why it behaves as if it were not configured.
-
 On top of that, everything an app needs after it is running: backup and
 restore into the customer's **own** S3 bucket, a timer on an app with its
 output kept, outbound webhooks so you stop polling, reading the app's own
 files, and running the app's own command line.
 
-The local (`npx`) server and the hosted OAuth connector expose the **same 116
-tools**, so nothing is lost by picking either path.
+The local (`npx`) server and the hosted OAuth connector expose the **same tool
+catalog — 184 tools on both sides**. Two declared, one-direction gaps remain:
+`impreza_get_log_request` stays hosted-only (only the control plane resolves a
+bare `request_id`; locally, call `impreza_tail_logs` again on the application —
+requests dedupe), and `impreza_upload_context` stays local-only (binary tarball
+streaming does not fit the hosted transport).
 
 ### New in 0.11.0
 
@@ -731,32 +730,51 @@ See the [Tor runtime guide](https://docs.imprezahost.com/onion-services.html#run
 for availability and verification. This option is separate from using Tor to
 connect the MCP client itself and from publishing an inbound onion address.
 
-## Point-in-time PostgreSQL recovery (0.45.0)
-
-Six tools cover status, configuration, a recovery drill, and prepare/get/apply
-of a reviewed UTC recovery point: `impreza_get_pitr`, `impreza_configure_pitr`,
-`impreza_drill_pitr`, `impreza_prepare_pitr_restore`,
-`impreza_get_pitr_restore`, and `impreza_apply_pitr_restore`. Status uses read
-scope; changes use deploy scope. The hosted connector requires a credential
-without resource confinement because physical PostgreSQL recovery can cover
-several bindings on a provider.
-
-WAL and base backups consume the account's storage. After six consecutive
-failures, automatic work pauses until the cause is repaired and configuration
-is saved again. Disabling stops protection but retains stored objects. A
-restore requires the review digest and `confirm: true`, creates a new database,
-and never redirects the live application. Poll the review until its receipt
-says `verified` or `failed`; acceptance alone is not a successful recovery.
-
-## Scheduled tasks (0.45.0)
-
-`impreza_create_task` creates a scheduled task on an app and `impreza_update_task`
-changes one that exists (any field you leave out keeps its current value, so
-`enabled=false` pauses a task without losing its schedule or history), as on the
-hosted connector. They replace `impreza_schedule_task`, which is gone: update
-any client or prompt that still calls it. `impreza_list_tasks`,
-`impreza_run_task` and `impreza_delete_task` are unchanged.
-
+## Local and hosted parity (0.46.0)
+
+The local package now carries the 16 tools that only the hosted connector had:
+
+- projects and environments: `impreza_rename_project`, `impreza_delete_project`,
+  `impreza_rename_environment` and `impreza_delete_environment`;
+- variable groups: `impreza_get_variable_group` and `impreza_set_variable_group`;
+- configuration promotion: `impreza_prepare_config_promotion`,
+  `impreza_get_config_promotion` and `impreza_apply_config_promotion`;
+- ordered environment deploys: `impreza_deploy_environment`,
+  `impreza_get_environment_deploy` and `impreza_list_environment_deploys`;
+- agent updates: `impreza_get_update_policy`, `impreza_set_update_policy` and
+  `impreza_request_agent_update`;
+- Shield: `impreza_set_shield`.
+
+Tool annotations (read-only, destructive, idempotent) now match the hosted
+connector. A destructive tool called with `confirm` missing or false is refused
+before any request is sent.
+
+## Point-in-time PostgreSQL recovery (0.45.0)
+
+Six tools cover status, configuration, a recovery drill, and prepare/get/apply
+of a reviewed UTC recovery point: `impreza_get_pitr`, `impreza_configure_pitr`,
+`impreza_drill_pitr`, `impreza_prepare_pitr_restore`,
+`impreza_get_pitr_restore`, and `impreza_apply_pitr_restore`. Status uses read
+scope; changes use deploy scope. The hosted connector requires a credential
+without resource confinement because physical PostgreSQL recovery can cover
+several bindings on a provider.
+
+WAL and base backups consume the account's storage. After six consecutive
+failures, automatic work pauses until the cause is repaired and configuration
+is saved again. Disabling stops protection but retains stored objects. A
+restore requires the review digest and `confirm: true`, creates a new database,
+and never redirects the live application. Poll the review until its receipt
+says `verified` or `failed`; acceptance alone is not a successful recovery.
+
+## Scheduled tasks (0.45.0)
+
+`impreza_create_task` creates a scheduled task on an app and `impreza_update_task`
+changes one that exists (any field you leave out keeps its current value, so
+`enabled=false` pauses a task without losing its schedule or history), as on the
+hosted connector. They replace `impreza_schedule_task`, which is gone: update
+any client or prompt that still calls it. `impreza_list_tasks`,
+`impreza_run_task` and `impreza_delete_task` are unchanged.
+
 ## VPS resize (0.44.0)
 
 `impreza_vps_resize` gives a configurable VPS more vCPUs, memory or disk. Price it