@cubis/foundry 0.3.51 → 0.3.52

package/workflows/skills/postman/references/troubleshooting.md

@@ -0,0 +1,25 @@
+# Postman MCP Troubleshooting
+
+## Only `postman_get_*` / `postman_set_mode` tools appear
+
+1. Confirm active env alias exists in shell (or persisted env file).
+2. Sync catalog:
+
+```bash
+cbx mcp tools sync --service postman --scope global
+cbx mcp tools list --service postman --scope global
+```
+
+3. Restart runtime if using Docker:
+
+```bash
+cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310
+```
+
+## Client does not show dotted names
+
+Use alias tools (`postman_<tool>`) when dotted names are filtered by client UI.
+
+## Missing API key at startup
+
+Expected behavior: tool names can still come from cached catalog; tool calls fail with explicit auth error until env alias is set.

package/workflows/skills/postman/references/workspace-policy.md

@@ -0,0 +1,20 @@
+# Workspace Default Policy
+
+Resolve workspace ID in this order:
+
+1. User-provided workspace ID in the request
+2. `postman_get_status` default workspace
+3. Auto-detected workspace when only one exists
+4. Explicit user selection when multiple workspaces exist
+
+## Persist Selected Workspace
+
+```bash
+cbx workflows config --scope global --workspace-id <workspace-id>
+```
+
+Clear workspace default:
+
+```bash
+cbx workflows config --scope global --clear-workspace-id
+```

package/workflows/workflows/agent-environment-setup/manifest.json

@@ -533,7 +533,7 @@
         "webapp-testing",
         "wrangler"
       ],
-      "rulesTemplate": "platforms/copilot/rules/AGENTS.md",
+      "rulesTemplate": "platforms/copilot/rules/copilot-instructions.md",
       "hooks": [
         {
           "type": "conductor-reference",

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/database.md

@@ -16,7 +16,6 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Companion skills: `database-design` (schema/migrations), `database-optimizer` (tuning/triage)
 - Mobile/local persistence companion: `drift-flutter`
 - Power bridge: `workflows/powers/database-skills`
-- Engine wrappers: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
 
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
@@ -25,6 +24,7 @@ Use this when data modeling, query quality, migration safety, or database perfor
 ## Skill Routing
 - Primary skills: `database-skills`, `database-design`
 - Supporting skills (optional): `database-optimizer`
+- Engine packs (sub-skills): `database-skills/postgres`, `database-skills/mysql`, `database-skills/vitess`, `database-skills/neki`, `database-skills/mongodb`, `database-skills/sqlite`, `database-skills/supabase`, `database-skills/redis`
 
 ## Workflow steps
 1. Confirm data shape, access patterns, and workload size.

package/workflows/workflows/agent-environment-setup/platforms/codex/workflows/database.md

@@ -16,7 +16,6 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Companion skills: `database-design` (schema/migrations), `database-optimizer` (tuning/triage)
 - Mobile/local persistence companion: `drift-flutter`
 - Power bridge: `workflows/powers/database-skills`
-- Engine wrappers: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
 
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
@@ -25,6 +24,7 @@ Use this when data modeling, query quality, migration safety, or database perfor
 ## Skill Routing
 - Primary skills: `database-skills`, `database-design`
 - Supporting skills (optional): `database-optimizer`
+- Engine packs (sub-skills): `database-skills/postgres`, `database-skills/mysql`, `database-skills/vitess`, `database-skills/neki`, `database-skills/mongodb`, `database-skills/sqlite`, `database-skills/supabase`, `database-skills/redis`
 
 ## Workflow steps
 1. Confirm data shape, access patterns, and workload size.

package/workflows/workflows/agent-environment-setup/platforms/copilot/rules/AGENTS.md

@@ -1,6 +1,7 @@
-# .github/copilot-instructions.md - Cubis Foundry Copilot Protocol
+# AGENTS.md - Copilot Compatibility Bridge
 
-This file defines mandatory behavior for GitHub Copilot projects installed via `cbx workflows`.
+Primary Copilot rule file is `.github/copilot-instructions.md`.
+This `AGENTS.md` exists for cross-tool compatibility (for example Codex/Cursor style readers) and should defer to `.github/copilot-instructions.md` when both files are present.
 
 ## 1) Platform Paths
 
@@ -230,7 +231,7 @@ After loading skills or completing a significant task phase, emit a single compa
 Use these commands to keep this setup healthy:
 
 - Install/update bundle:
-  `cbx workflows install --platform copilot --bundle agent-environment-setup --scope global --overwrite --postman --stitch --mcp-runtime docker --mcp-fallback local --mcp-tool-sync`
+  `cbx workflows install --platform copilot --bundle agent-environment-setup --scope global --overwrite --postman --postman-mode full --stitch --mcp-runtime docker --mcp-fallback local --mcp-tool-sync`
 - Start MCP Docker runtime:
   `cbx mcp runtime up --scope global --name cbx-mcp --port 3310 --replace`
 - Check MCP Docker runtime:

package/workflows/workflows/agent-environment-setup/platforms/copilot/rules/copilot-instructions.md

@@ -230,7 +230,7 @@ After loading skills or completing a significant task phase, emit a single compa
 Use these commands to keep this setup healthy:
 
 - Install/update bundle:
-  `cbx workflows install --platform copilot --bundle agent-environment-setup --scope global --overwrite --postman --stitch --mcp-runtime docker --mcp-fallback local --mcp-tool-sync`
+  `cbx workflows install --platform copilot --bundle agent-environment-setup --scope global --overwrite --postman --postman-mode full --stitch --mcp-runtime docker --mcp-fallback local --mcp-tool-sync`
 - Start MCP Docker runtime:
   `cbx mcp runtime up --scope global --name cbx-mcp --port 3310 --replace`
 - Check MCP Docker runtime:

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/postman/SKILL.md

@@ -1,41 +1,53 @@
 ---
 name: postman
-description: Use Postman MCP tools for workspace, collection, environment, and run workflows with explicit default-workspace handling.
+description: Automate API testing and collection management with Postman MCP using full-mode defaults and workspace-aware execution.
 ---
 
-# Postman MCP
+# Postman MCP Skill
 
-Use this skill when you need to work with Postman through MCP tools.
+Use this skill when you need Postman workspace, collection, environment, or run operations through MCP.
+
+References:
+- [Full-Mode Setup](./references/full-mode-setup.md)
+- [Workspace Policy](./references/workspace-policy.md)
+- [Troubleshooting](./references/troubleshooting.md)
 
 ## MCP-First Rule
 
-- Prefer Postman MCP tools (`postman.*`) for all Postman operations.
+- Prefer Postman MCP tools for all Postman operations.
+- Accept both dynamic naming styles from clients:
+  - dotted: `postman.<tool>`
+  - alias: `postman_<tool>`
 - Do not use Newman/Postman CLI fallback unless the user explicitly asks for fallback.
-- If required Postman MCP tools are unavailable, stop and report the MCP discovery issue with remediation steps.
+- If required Postman MCP tools are unavailable, report discovery/remediation steps first.
 
-## Required Environment Variables
+## Setup Baseline
 
-- Active profile key alias must be set (typically `POSTMAN_API_KEY_DEFAULT`).
-- `POSTMAN_API_KEY_<PROFILE>` aliases are also valid if the active profile uses them.
+1. Install with Postman enabled and explicit full mode:
+   - `cbx workflows install --platform <codex|antigravity|copilot> --scope global --bundle agent-environment-setup --postman --postman-mode full --mcp-runtime docker --mcp-fallback local --mcp-tool-sync --yes`
+2. Persist env aliases once (no per-session re-export):
+   - `cbx workflows config keys persist-env --service postman --scope global`
+3. Verify mode/config:
+   - `cbx workflows config --scope global --show`
+   - `cbx mcp tools sync --service postman --scope global`
+   - `cbx mcp tools list --service postman --scope global`
 
-## Preflight Checklist
+## Preflight
 
 1. Read Postman status first:
-   - Call `postman_get_status` (`scope: auto` unless user requires a scope).
-2. Validate connectivity and mode:
-   - If not configured, report missing env alias/config and stop.
-   - If mode is not `full`, call `postman_set_mode` with `mode: full`.
+   - Call `postman_get_status`.
+2. Ensure mode is `full`:
+   - If not, call `postman_set_mode` with `mode: full`.
 3. Discover upstream tools:
-   - Prefer `postman.getEnabledTools` when available.
-   - Confirm required tool names before proceeding (for example `getWorkspaces`, `getCollections`, `runCollection`).
+   - Confirm required tools exist before execution (for example workspaces/collections/runs).
 
-## Default Workspace ID Policy
+## Default Workspace Policy
 
 Resolve workspace in this order:
 
 1. User-provided workspace ID.
 2. `postman_get_status.defaultWorkspaceId`.
-3. Auto-detect from `postman.getWorkspaces`:
+3. Auto-detect from workspace listing:
    - If exactly one workspace exists, use it and state that choice.
 4. If multiple workspaces and no default:
    - Ask user to choose one.
@@ -46,17 +58,11 @@ When a Postman tool requires a workspace argument, always pass the resolved work
 
 ## Common Workflows
 
-### List/Inspect
-
-- `postman.getWorkspaces`
-- `postman.getCollections` (with resolved workspace ID)
-- `postman.getEnvironments` (with resolved workspace ID)
-
 ### Collection Run
 
 1. Resolve workspace ID (policy above).
 2. Resolve `collectionId` and optional `environmentId`.
-3. Call `postman.runCollection`.
+3. Call Postman run tool (`postman.runCollection` or alias equivalent).
 4. Return a concise run summary:
    - total requests
    - passed/failed tests
@@ -65,7 +71,7 @@ When a Postman tool requires a workspace argument, always pass the resolved work
 
 ## Failure Handling
 
-If dynamic Postman tools are missing (only `postman_get_*` / `postman_set_mode` visible):
+If dynamic Postman tools are missing:
 
 1. Verify env alias expected by config is set.
 2. Resync catalog:

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/postman/references/full-mode-setup.md

@@ -0,0 +1,36 @@
+# Postman Full-Mode Setup
+
+Use CLI mode flags instead of manual `jq` edits.
+
+## Install/Upgrade with Full Mode
+
+```bash
+cbx workflows install \
+  --platform codex \
+  --scope global \
+  --bundle agent-environment-setup \
+  --postman \
+  --postman-mode full \
+  --mcp-runtime docker \
+  --mcp-fallback local \
+  --mcp-tool-sync \
+  --overwrite \
+  --yes
+```
+
+## Change Mode Later
+
+```bash
+cbx workflows config --scope global --platform codex --postman-mode full
+```
+
+This updates:
+- `cbx_config.json` Postman URL
+- managed Postman MCP definition under `.cbx/mcp/<platform>/postman.json`
+- platform MCP runtime target patch (when platform is resolvable)
+
+## Persist Env Aliases
+
+```bash
+cbx workflows config keys persist-env --service postman --scope global
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/postman/references/troubleshooting.md

@@ -0,0 +1,25 @@
+# Postman MCP Troubleshooting
+
+## Only `postman_get_*` / `postman_set_mode` tools appear
+
+1. Confirm active env alias exists in shell (or persisted env file).
+2. Sync catalog:
+
+```bash
+cbx mcp tools sync --service postman --scope global
+cbx mcp tools list --service postman --scope global
+```
+
+3. Restart runtime if using Docker:
+
+```bash
+cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310
+```
+
+## Client does not show dotted names
+
+Use alias tools (`postman_<tool>`) when dotted names are filtered by client UI.
+
+## Missing API key at startup
+
+Expected behavior: tool names can still come from cached catalog; tool calls fail with explicit auth error until env alias is set.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/postman/references/workspace-policy.md

@@ -0,0 +1,20 @@
+# Workspace Default Policy
+
+Resolve workspace ID in this order:
+
+1. User-provided workspace ID in the request
+2. `postman_get_status` default workspace
+3. Auto-detected workspace when only one exists
+4. Explicit user selection when multiple workspaces exist
+
+## Persist Selected Workspace
+
+```bash
+cbx workflows config --scope global --workspace-id <workspace-id>
+```
+
+Clear workspace default:
+
+```bash
+cbx workflows config --scope global --clear-workspace-id
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/workflows/database.md

@@ -16,7 +16,6 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Companion skills: `database-design` (schema/migrations), `database-optimizer` (tuning/triage)
 - Mobile/local persistence companion: `drift-flutter`
 - Power bridge: `workflows/powers/database-skills`
-- Engine wrappers: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
 
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
@@ -25,6 +24,7 @@ Use this when data modeling, query quality, migration safety, or database perfor
 ## Skill Routing
 - Primary skills: `database-skills`, `database-design`
 - Supporting skills (optional): `database-optimizer`
+- Engine packs (sub-skills): `database-skills/postgres`, `database-skills/mysql`, `database-skills/vitess`, `database-skills/neki`, `database-skills/mongodb`, `database-skills/sqlite`, `database-skills/supabase`, `database-skills/redis`
 
 ## Workflow steps
 1. Confirm data shape, access patterns, and workload size.

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/postman/SKILL.md

@@ -1,41 +1,53 @@
 ---
 name: postman
-description: Use Postman MCP tools for workspace, collection, environment, and run workflows with explicit default-workspace handling.
+description: Automate API testing and collection management with Postman MCP using full-mode defaults and workspace-aware execution.
 ---
 
-# Postman MCP
+# Postman MCP Skill
 
-Use this skill when you need to work with Postman through MCP tools.
+Use this skill when you need Postman workspace, collection, environment, or run operations through MCP.
+
+References:
+- [Full-Mode Setup](./references/full-mode-setup.md)
+- [Workspace Policy](./references/workspace-policy.md)
+- [Troubleshooting](./references/troubleshooting.md)
 
 ## MCP-First Rule
 
-- Prefer Postman MCP tools (`postman.*`) for all Postman operations.
+- Prefer Postman MCP tools for all Postman operations.
+- Accept both dynamic naming styles from clients:
+  - dotted: `postman.<tool>`
+  - alias: `postman_<tool>`
 - Do not use Newman/Postman CLI fallback unless the user explicitly asks for fallback.
-- If required Postman MCP tools are unavailable, stop and report the MCP discovery issue with remediation steps.
+- If required Postman MCP tools are unavailable, report discovery/remediation steps first.
 
-## Required Environment Variables
+## Setup Baseline
 
-- Active profile key alias must be set (typically `POSTMAN_API_KEY_DEFAULT`).
-- `POSTMAN_API_KEY_<PROFILE>` aliases are also valid if the active profile uses them.
+1. Install with Postman enabled and explicit full mode:
+   - `cbx workflows install --platform <codex|antigravity|copilot> --scope global --bundle agent-environment-setup --postman --postman-mode full --mcp-runtime docker --mcp-fallback local --mcp-tool-sync --yes`
+2. Persist env aliases once (no per-session re-export):
+   - `cbx workflows config keys persist-env --service postman --scope global`
+3. Verify mode/config:
+   - `cbx workflows config --scope global --show`
+   - `cbx mcp tools sync --service postman --scope global`
+   - `cbx mcp tools list --service postman --scope global`
 
-## Preflight Checklist
+## Preflight
 
 1. Read Postman status first:
-   - Call `postman_get_status` (`scope: auto` unless user requires a scope).
-2. Validate connectivity and mode:
-   - If not configured, report missing env alias/config and stop.
-   - If mode is not `full`, call `postman_set_mode` with `mode: full`.
+   - Call `postman_get_status`.
+2. Ensure mode is `full`:
+   - If not, call `postman_set_mode` with `mode: full`.
 3. Discover upstream tools:
-   - Prefer `postman.getEnabledTools` when available.
-   - Confirm required tool names before proceeding (for example `getWorkspaces`, `getCollections`, `runCollection`).
+   - Confirm required tools exist before execution (for example workspaces/collections/runs).
 
-## Default Workspace ID Policy
+## Default Workspace Policy
 
 Resolve workspace in this order:
 
 1. User-provided workspace ID.
 2. `postman_get_status.defaultWorkspaceId`.
-3. Auto-detect from `postman.getWorkspaces`:
+3. Auto-detect from workspace listing:
    - If exactly one workspace exists, use it and state that choice.
 4. If multiple workspaces and no default:
    - Ask user to choose one.
@@ -46,17 +58,11 @@ When a Postman tool requires a workspace argument, always pass the resolved work
 
 ## Common Workflows
 
-### List/Inspect
-
-- `postman.getWorkspaces`
-- `postman.getCollections` (with resolved workspace ID)
-- `postman.getEnvironments` (with resolved workspace ID)
-
 ### Collection Run
 
 1. Resolve workspace ID (policy above).
 2. Resolve `collectionId` and optional `environmentId`.
-3. Call `postman.runCollection`.
+3. Call Postman run tool (`postman.runCollection` or alias equivalent).
 4. Return a concise run summary:
    - total requests
    - passed/failed tests
@@ -65,7 +71,7 @@ When a Postman tool requires a workspace argument, always pass the resolved work
 
 ## Failure Handling
 
-If dynamic Postman tools are missing (only `postman_get_*` / `postman_set_mode` visible):
+If dynamic Postman tools are missing:
 
 1. Verify env alias expected by config is set.
 2. Resync catalog:

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/postman/references/full-mode-setup.md

@@ -0,0 +1,36 @@
+# Postman Full-Mode Setup
+
+Use CLI mode flags instead of manual `jq` edits.
+
+## Install/Upgrade with Full Mode
+
+```bash
+cbx workflows install \
+  --platform codex \
+  --scope global \
+  --bundle agent-environment-setup \
+  --postman \
+  --postman-mode full \
+  --mcp-runtime docker \
+  --mcp-fallback local \
+  --mcp-tool-sync \
+  --overwrite \
+  --yes
+```
+
+## Change Mode Later
+
+```bash
+cbx workflows config --scope global --platform codex --postman-mode full
+```
+
+This updates:
+- `cbx_config.json` Postman URL
+- managed Postman MCP definition under `.cbx/mcp/<platform>/postman.json`
+- platform MCP runtime target patch (when platform is resolvable)
+
+## Persist Env Aliases
+
+```bash
+cbx workflows config keys persist-env --service postman --scope global
+```

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/postman/references/troubleshooting.md

@@ -0,0 +1,25 @@
+# Postman MCP Troubleshooting
+
+## Only `postman_get_*` / `postman_set_mode` tools appear
+
+1. Confirm active env alias exists in shell (or persisted env file).
+2. Sync catalog:
+
+```bash
+cbx mcp tools sync --service postman --scope global
+cbx mcp tools list --service postman --scope global
+```
+
+3. Restart runtime if using Docker:
+
+```bash
+cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310
+```
+
+## Client does not show dotted names
+
+Use alias tools (`postman_<tool>`) when dotted names are filtered by client UI.
+
+## Missing API key at startup
+
+Expected behavior: tool names can still come from cached catalog; tool calls fail with explicit auth error until env alias is set.

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/postman/references/workspace-policy.md

@@ -0,0 +1,20 @@
+# Workspace Default Policy
+
+Resolve workspace ID in this order:
+
+1. User-provided workspace ID in the request
+2. `postman_get_status` default workspace
+3. Auto-detected workspace when only one exists
+4. Explicit user selection when multiple workspaces exist
+
+## Persist Selected Workspace
+
+```bash
+cbx workflows config --scope global --workspace-id <workspace-id>
+```
+
+Clear workspace default:
+
+```bash
+cbx workflows config --scope global --clear-workspace-id
+```

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/postman/SKILL.md

@@ -1,41 +1,53 @@
 ---
 name: postman
-description: Use Postman MCP tools for workspace, collection, environment, and run workflows with explicit default-workspace handling.
+description: Automate API testing and collection management with Postman MCP using full-mode defaults and workspace-aware execution.
 ---
 
-# Postman MCP
+# Postman MCP Skill
 
-Use this skill when you need to work with Postman through MCP tools.
+Use this skill when you need Postman workspace, collection, environment, or run operations through MCP.
+
+References:
+- [Full-Mode Setup](./references/full-mode-setup.md)
+- [Workspace Policy](./references/workspace-policy.md)
+- [Troubleshooting](./references/troubleshooting.md)
 
 ## MCP-First Rule
 
-- Prefer Postman MCP tools (`postman.*`) for all Postman operations.
+- Prefer Postman MCP tools for all Postman operations.
+- Accept both dynamic naming styles from clients:
+  - dotted: `postman.<tool>`
+  - alias: `postman_<tool>`
 - Do not use Newman/Postman CLI fallback unless the user explicitly asks for fallback.
-- If required Postman MCP tools are unavailable, stop and report the MCP discovery issue with remediation steps.
+- If required Postman MCP tools are unavailable, report discovery/remediation steps first.
 
-## Required Environment Variables
+## Setup Baseline
 
-- Active profile key alias must be set (typically `POSTMAN_API_KEY_DEFAULT`).
-- `POSTMAN_API_KEY_<PROFILE>` aliases are also valid if the active profile uses them.
+1. Install with Postman enabled and explicit full mode:
+   - `cbx workflows install --platform <codex|antigravity|copilot> --scope global --bundle agent-environment-setup --postman --postman-mode full --mcp-runtime docker --mcp-fallback local --mcp-tool-sync --yes`
+2. Persist env aliases once (no per-session re-export):
+   - `cbx workflows config keys persist-env --service postman --scope global`
+3. Verify mode/config:
+   - `cbx workflows config --scope global --show`
+   - `cbx mcp tools sync --service postman --scope global`
+   - `cbx mcp tools list --service postman --scope global`
 
-## Preflight Checklist
+## Preflight
 
 1. Read Postman status first:
-   - Call `postman_get_status` (`scope: auto` unless user requires a scope).
-2. Validate connectivity and mode:
-   - If not configured, report missing env alias/config and stop.
-   - If mode is not `full`, call `postman_set_mode` with `mode: full`.
+   - Call `postman_get_status`.
+2. Ensure mode is `full`:
+   - If not, call `postman_set_mode` with `mode: full`.
 3. Discover upstream tools:
-   - Prefer `postman.getEnabledTools` when available.
-   - Confirm required tool names before proceeding (for example `getWorkspaces`, `getCollections`, `runCollection`).
+   - Confirm required tools exist before execution (for example workspaces/collections/runs).
 
-## Default Workspace ID Policy
+## Default Workspace Policy
 
 Resolve workspace in this order:
 
 1. User-provided workspace ID.
 2. `postman_get_status.defaultWorkspaceId`.
-3. Auto-detect from `postman.getWorkspaces`:
+3. Auto-detect from workspace listing:
    - If exactly one workspace exists, use it and state that choice.
 4. If multiple workspaces and no default:
    - Ask user to choose one.
@@ -46,17 +58,11 @@ When a Postman tool requires a workspace argument, always pass the resolved work
 
 ## Common Workflows
 
-### List/Inspect
-
-- `postman.getWorkspaces`
-- `postman.getCollections` (with resolved workspace ID)
-- `postman.getEnvironments` (with resolved workspace ID)
-
 ### Collection Run
 
 1. Resolve workspace ID (policy above).
 2. Resolve `collectionId` and optional `environmentId`.
-3. Call `postman.runCollection`.
+3. Call Postman run tool (`postman.runCollection` or alias equivalent).
 4. Return a concise run summary:
    - total requests
    - passed/failed tests
@@ -65,7 +71,7 @@ When a Postman tool requires a workspace argument, always pass the resolved work
 
 ## Failure Handling
 
-If dynamic Postman tools are missing (only `postman_get_*` / `postman_set_mode` visible):
+If dynamic Postman tools are missing:
 
 1. Verify env alias expected by config is set.
 2. Resync catalog:

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/postman/references/full-mode-setup.md

@@ -0,0 +1,36 @@
+# Postman Full-Mode Setup
+
+Use CLI mode flags instead of manual `jq` edits.
+
+## Install/Upgrade with Full Mode
+
+```bash
+cbx workflows install \
+  --platform codex \
+  --scope global \
+  --bundle agent-environment-setup \
+  --postman \
+  --postman-mode full \
+  --mcp-runtime docker \
+  --mcp-fallback local \
+  --mcp-tool-sync \
+  --overwrite \
+  --yes
+```
+
+## Change Mode Later
+
+```bash
+cbx workflows config --scope global --platform codex --postman-mode full
+```
+
+This updates:
+- `cbx_config.json` Postman URL
+- managed Postman MCP definition under `.cbx/mcp/<platform>/postman.json`
+- platform MCP runtime target patch (when platform is resolvable)
+
+## Persist Env Aliases
+
+```bash
+cbx workflows config keys persist-env --service postman --scope global
+```