@ductape/mcp 0.1.10 → 0.1.12

package/dist/index.js

@@ -65,6 +65,26 @@ There are THREE categories of operations. Use the right tool for each:
        cloud connections, and secrets. Environments, app actions, auths, features, quotas,
        fallbacks, jobs, and healthchecks are configured in the Workbench UI.
 
+       ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
+       messageBroker, graph, vector, and any other resource with an envs array):
+       The envs array MUST contain one entry for EVERY environment defined on the product.
+       import-persist and provision-persist enforce this with a preflight check: if the
+       generated draft does not cover all product environments the operation fails immediately
+       with error code MISSING_ENV_COVERAGE and a message listing exactly which envs are absent.
+       No creation or mutation is attempted. You cannot scope an asset to a subset of environments.
+
+       BEFORE constructing any resource file or initiating import/provision:
+         1. Run: ductape_cli("products environments list <product_tag> --json")
+         2. Note every slug returned (e.g. dev, snd, prd).
+         3. Collect connection details or confirmation for EACH slug from the user.
+            Do not proceed until you have details for every env.
+
+       Sharing one resource across multiple envs is allowed but must be confirmed per env:
+         - Ask the user explicitly: "Should <env> use the same <resource> as <other_env>?"
+         - Never assume shared configuration without confirmation.
+         - For cloud-linked envs, set config.cloud to the connection tag for that env and
+           omit raw credentials; the cloud connection must exist for that env too.
+
   2. RUNTIME OPERATIONS  (run, dispatch, execute, start, send, produce, query, insert, update, delete…)
        The "input" field shape is product- and operation-specific — it is NOT derivable from Joi validators.
        It is defined by how the product's action/feature/session/quota/etc. was configured in Ductape.
@@ -1133,6 +1153,11 @@ async function main() {
                 '    ALWAYS call ductape_schema(module="product") first to get the exact field shape before\n' +
                 '    constructing a file. Storage envs[].config is conditional on envs[].type (aws/gcp/azure)\n' +
                 '    and returned as oneOf — pick the variant matching the type.\n' +
+                '    REQUIRED: before building any resource file, run\n' +
+                '      ductape_cli("products environments list <product_tag> --json")\n' +
+                '    and include an envs entry for EVERY environment returned. Omitting any env causes a\n' +
+                '    validation error. If the user has not supplied connection details for every env, ask\n' +
+                '    them explicitly. Confirm per-env before reusing the same resource across environments.\n' +
                 '  - Three distinct storage registration flows — choose the right one:\n' +
                 '    1. Manual credentials (bucket already exists, you supply keys directly):\n' +
                 '         resources storage create -f storage.json\n' +

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ductape/mcp",
-  "version": "0.1.10",
+  "version": "0.1.12",
   "description": "MCP server that exposes Ductape SDK operations via the backend proxy",
   "type": "module",
   "main": "dist/index.js",

package/src/index.ts

@@ -76,6 +76,26 @@ There are THREE categories of operations. Use the right tool for each:
        cloud connections, and secrets. Environments, app actions, auths, features, quotas,
        fallbacks, jobs, and healthchecks are configured in the Workbench UI.
 
+       ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
+       messageBroker, graph, vector, and any other resource with an envs array):
+       The envs array MUST contain one entry for EVERY environment defined on the product.
+       import-persist and provision-persist enforce this with a preflight check: if the
+       generated draft does not cover all product environments the operation fails immediately
+       with error code MISSING_ENV_COVERAGE and a message listing exactly which envs are absent.
+       No creation or mutation is attempted. You cannot scope an asset to a subset of environments.
+
+       BEFORE constructing any resource file or initiating import/provision:
+         1. Run: ductape_cli("products environments list <product_tag> --json")
+         2. Note every slug returned (e.g. dev, snd, prd).
+         3. Collect connection details or confirmation for EACH slug from the user.
+            Do not proceed until you have details for every env.
+
+       Sharing one resource across multiple envs is allowed but must be confirmed per env:
+         - Ask the user explicitly: "Should <env> use the same <resource> as <other_env>?"
+         - Never assume shared configuration without confirmation.
+         - For cloud-linked envs, set config.cloud to the connection tag for that env and
+           omit raw credentials; the cloud connection must exist for that env too.
+
   2. RUNTIME OPERATIONS  (run, dispatch, execute, start, send, produce, query, insert, update, delete…)
        The "input" field shape is product- and operation-specific — it is NOT derivable from Joi validators.
        It is defined by how the product's action/feature/session/quota/etc. was configured in Ductape.
@@ -1227,6 +1247,11 @@ async function main() {
           '    ALWAYS call ductape_schema(module="product") first to get the exact field shape before\n' +
           '    constructing a file. Storage envs[].config is conditional on envs[].type (aws/gcp/azure)\n' +
           '    and returned as oneOf — pick the variant matching the type.\n' +
+          '    REQUIRED: before building any resource file, run\n' +
+          '      ductape_cli("products environments list <product_tag> --json")\n' +
+          '    and include an envs entry for EVERY environment returned. Omitting any env causes a\n' +
+          '    validation error. If the user has not supplied connection details for every env, ask\n' +
+          '    them explicitly. Confirm per-env before reusing the same resource across environments.\n' +
           '  - Three distinct storage registration flows — choose the right one:\n' +
           '    1. Manual credentials (bucket already exists, you supply keys directly):\n' +
           '         resources storage create -f storage.json\n' +