@cubis/foundry 0.3.57 → 0.3.60

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

@@ -0,0 +1,40 @@
+---
+command: "/postman"
+description: "Execute Postman MCP operations for workspaces, collections, environments, and runs."
+triggers: ["postman", "collection", "workspace", "environment", "runcollection", "monitor", "mock", "api test"]
+---
+# Postman Workflow
+
+## When to use
+Use this when tasks are primarily about Postman workspaces, collections, environments, monitors, mocks, or collection runs.
+
+## Routing
+- Postman operations and execution: `@backend-specialist`
+- Security/compliance checks on test data: `@security-auditor`
+- Validation quality and assertions: `@test-engineer`
+
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Resolve and pass workspace IDs explicitly when tools require them.
+- Prefer MCP tools (`postman.*` or `postman_*`) over manual JSON/CLI fallback unless fallback is explicitly requested by the user.
+
+## Skill Routing
+- Primary skills: `postman`
+- Supporting skills (optional): `api-designer`, `test-master`
+
+## Workflow steps
+1. Load Postman skill and check integration status (`postman_get_status`).
+2. Resolve workspace ID (user-provided, configured default, or explicit selection).
+3. Execute required MCP operations (list/create/update/run) with explicit IDs.
+4. Summarize outcomes, failures, and next actions with exact object identifiers.
+
+## Verification
+- Confirm requested Postman action completed successfully.
+- Validate response status and key result fields (IDs, counts, failures).
+- Note any skipped steps and required follow-up.
+
+## Output Contract
+- Workspace/context used
+- Actions executed and resulting IDs
+- Pass/fail summary for runs
+- Follow-up or remediation steps

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/documentation-templates/docs/api.md

@@ -0,0 +1,16 @@
+# API Reference Template
+
+Use this file as the canonical entry point for API endpoint documentation.
+
+## Endpoint Index
+
+- `GET /resource`
+- `POST /resource`
+- `PATCH /resource/{id}`
+- `DELETE /resource/{id}`
+
+## Conventions
+
+- Include auth requirements per endpoint.
+- Include request/response examples.
+- Include error codes and retry guidance.

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/documentation-templates/docs/architecture.md

@@ -0,0 +1,23 @@
+# Architecture Overview Template
+
+Use this file to describe system boundaries and data flow.
+
+## Components
+
+- API layer
+- Domain/service layer
+- Persistence layer
+- External integrations
+
+## Runtime Flow
+
+1. Request enters API layer
+2. Domain logic validates and processes
+3. Persistence reads/writes state
+4. Response returns with observability metadata
+
+## Non-Functional Notes
+
+- Reliability/SLOs
+- Security model
+- Scaling strategy

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

@@ -18,19 +18,20 @@ References:
 - Accept both dynamic naming styles from clients:
   - dotted: `postman.<tool>`
   - alias: `postman_<tool>`
+- Never default to raw Postman REST JSON payloads, Newman, or Postman CLI when MCP tools are available.
 - Do not use Newman/Postman CLI fallback unless the user explicitly asks for fallback.
 - If required Postman MCP tools are unavailable, report discovery/remediation steps first.
 
 ## Setup Baseline
 
-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`
+1. Install with Postman enabled and explicit full mode (use the same scope as your current install):
+   - `cbx workflows install --platform <codex|antigravity|copilot> --scope <project|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`
+   - `cbx workflows config --scope <project|global> --show`
+   - `cbx mcp tools sync --service postman --scope <project|global>`
+   - `cbx mcp tools list --service postman --scope <project|global>`
 
 ## Preflight
 
@@ -41,6 +42,10 @@ References:
 3. Discover upstream tools:
    - Confirm required tools exist before execution (for example workspaces/collections/runs).
 
+Execution rule:
+- For Postman requests, call MCP tools directly (`postman.*` or `postman_*`) instead of drafting manual JSON or curl payloads.
+- If the user asks for API payload examples, provide them only as supplemental documentation after MCP execution guidance.
+
 ## Default Workspace Policy
 
 Resolve workspace in this order:
@@ -52,7 +57,7 @@ Resolve workspace in this order:
 4. If multiple workspaces and no default:
    - Ask user to choose one.
    - Recommend persisting it with:
-     - `cbx workflows config --scope global --workspace-id <workspace-id>`
+     - `cbx workflows config --scope <project|global> --workspace-id <workspace-id>`
 
 When a Postman tool requires a workspace argument, always pass the resolved workspace ID explicitly.
 
@@ -75,10 +80,10 @@ If dynamic Postman tools are missing:
 
 1. Verify env alias expected by config is set.
 2. Resync catalog:
-   - `cbx mcp tools sync --service postman --scope global`
-   - `cbx mcp tools list --service postman --scope global`
+   - `cbx mcp tools sync --service postman --scope <project|global>`
+   - `cbx mcp tools list --service postman --scope <project|global>`
 3. Recreate runtime if needed:
-   - `cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310 --skills-root ~/.agents/skills`
+   - `cbx mcp runtime up --scope <project|global> --name cbx-mcp --replace --port 3310 --skills-root ~/.agents/skills`
 
 ## Security Notes
 

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

@@ -7,7 +7,7 @@ Use CLI mode flags instead of manual `jq` edits.
 ```bash
 cbx workflows install \
   --platform codex \
-  --scope global \
+  --scope <project|global> \
   --bundle agent-environment-setup \
   --postman \
   --postman-mode full \
@@ -21,7 +21,7 @@ cbx workflows install \
 ## Change Mode Later
 
 ```bash
-cbx workflows config --scope global --platform codex --postman-mode full
+cbx workflows config --scope <project|global> --platform codex --postman-mode full
 ```
 
 This updates:
@@ -34,3 +34,7 @@ This updates:
 ```bash
 cbx workflows config keys persist-env --service postman --scope global
 ```
+
+Note:
+- `persist-env` writes CBX-managed aliases to `~/.cbx/credentials.env`.
+- Keep MCP target scope (`project` or `global`) aligned with the scope where you installed Postman integration.

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

@@ -3,19 +3,24 @@
 ## Only `postman_get_*` / `postman_set_mode` tools appear
 
 1. Confirm active env alias exists in shell (or persisted env file).
-2. Sync catalog:
+2. Sync catalog in the same install scope:
 
 ```bash
-cbx mcp tools sync --service postman --scope global
-cbx mcp tools list --service postman --scope global
+cbx mcp tools sync --service postman --scope <project|global>
+cbx mcp tools list --service postman --scope <project|global>
 ```
 
 3. Restart runtime if using Docker:
 
 ```bash
-cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310
+cbx mcp runtime up --scope <project|global> --name cbx-mcp --replace --port 3310
 ```
 
+4. If dynamic Postman tools are still missing, do not fall back to manual JSON/CLI by default:
+   - report MCP tool discovery failure
+   - ask for remediation approval
+   - only use fallback if the user explicitly requests it
+
 ## Client does not show dotted names
 
 Use alias tools (`postman_<tool>`) when dotted names are filtered by client UI.

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/documentation-templates/docs/api.md

@@ -0,0 +1,16 @@
+# API Reference Template
+
+Use this file as the canonical entry point for API endpoint documentation.
+
+## Endpoint Index
+
+- `GET /resource`
+- `POST /resource`
+- `PATCH /resource/{id}`
+- `DELETE /resource/{id}`
+
+## Conventions
+
+- Include auth requirements per endpoint.
+- Include request/response examples.
+- Include error codes and retry guidance.

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/documentation-templates/docs/architecture.md

@@ -0,0 +1,23 @@
+# Architecture Overview Template
+
+Use this file to describe system boundaries and data flow.
+
+## Components
+
+- API layer
+- Domain/service layer
+- Persistence layer
+- External integrations
+
+## Runtime Flow
+
+1. Request enters API layer
+2. Domain logic validates and processes
+3. Persistence reads/writes state
+4. Response returns with observability metadata
+
+## Non-Functional Notes
+
+- Reliability/SLOs
+- Security model
+- Scaling strategy

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

@@ -18,19 +18,20 @@ References:
 - Accept both dynamic naming styles from clients:
   - dotted: `postman.<tool>`
   - alias: `postman_<tool>`
+- Never default to raw Postman REST JSON payloads, Newman, or Postman CLI when MCP tools are available.
 - Do not use Newman/Postman CLI fallback unless the user explicitly asks for fallback.
 - If required Postman MCP tools are unavailable, report discovery/remediation steps first.
 
 ## Setup Baseline
 
-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`
+1. Install with Postman enabled and explicit full mode (use the same scope as your current install):
+   - `cbx workflows install --platform <codex|antigravity|copilot> --scope <project|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`
+   - `cbx workflows config --scope <project|global> --show`
+   - `cbx mcp tools sync --service postman --scope <project|global>`
+   - `cbx mcp tools list --service postman --scope <project|global>`
 
 ## Preflight
 
@@ -41,6 +42,10 @@ References:
 3. Discover upstream tools:
    - Confirm required tools exist before execution (for example workspaces/collections/runs).
 
+Execution rule:
+- For Postman requests, call MCP tools directly (`postman.*` or `postman_*`) instead of drafting manual JSON or curl payloads.
+- If the user asks for API payload examples, provide them only as supplemental documentation after MCP execution guidance.
+
 ## Default Workspace Policy
 
 Resolve workspace in this order:
@@ -52,7 +57,7 @@ Resolve workspace in this order:
 4. If multiple workspaces and no default:
    - Ask user to choose one.
    - Recommend persisting it with:
-     - `cbx workflows config --scope global --workspace-id <workspace-id>`
+     - `cbx workflows config --scope <project|global> --workspace-id <workspace-id>`
 
 When a Postman tool requires a workspace argument, always pass the resolved workspace ID explicitly.
 
@@ -75,10 +80,10 @@ If dynamic Postman tools are missing:
 
 1. Verify env alias expected by config is set.
 2. Resync catalog:
-   - `cbx mcp tools sync --service postman --scope global`
-   - `cbx mcp tools list --service postman --scope global`
+   - `cbx mcp tools sync --service postman --scope <project|global>`
+   - `cbx mcp tools list --service postman --scope <project|global>`
 3. Recreate runtime if needed:
-   - `cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310 --skills-root ~/.agents/skills`
+   - `cbx mcp runtime up --scope <project|global> --name cbx-mcp --replace --port 3310 --skills-root ~/.agents/skills`
 
 ## Security Notes
 

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

@@ -7,7 +7,7 @@ Use CLI mode flags instead of manual `jq` edits.
 ```bash
 cbx workflows install \
   --platform codex \
-  --scope global \
+  --scope <project|global> \
   --bundle agent-environment-setup \
   --postman \
   --postman-mode full \
@@ -21,7 +21,7 @@ cbx workflows install \
 ## Change Mode Later
 
 ```bash
-cbx workflows config --scope global --platform codex --postman-mode full
+cbx workflows config --scope <project|global> --platform codex --postman-mode full
 ```
 
 This updates:
@@ -34,3 +34,7 @@ This updates:
 ```bash
 cbx workflows config keys persist-env --service postman --scope global
 ```
+
+Note:
+- `persist-env` writes CBX-managed aliases to `~/.cbx/credentials.env`.
+- Keep MCP target scope (`project` or `global`) aligned with the scope where you installed Postman integration.

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

@@ -3,19 +3,24 @@
 ## Only `postman_get_*` / `postman_set_mode` tools appear
 
 1. Confirm active env alias exists in shell (or persisted env file).
-2. Sync catalog:
+2. Sync catalog in the same install scope:
 
 ```bash
-cbx mcp tools sync --service postman --scope global
-cbx mcp tools list --service postman --scope global
+cbx mcp tools sync --service postman --scope <project|global>
+cbx mcp tools list --service postman --scope <project|global>
 ```
 
 3. Restart runtime if using Docker:
 
 ```bash
-cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310
+cbx mcp runtime up --scope <project|global> --name cbx-mcp --replace --port 3310
 ```
 
+4. If dynamic Postman tools are still missing, do not fall back to manual JSON/CLI by default:
+   - report MCP tool discovery failure
+   - ask for remediation approval
+   - only use fallback if the user explicitly requests it
+
 ## Client does not show dotted names
 
 Use alias tools (`postman_<tool>`) when dotted names are filtered by client UI.

package/workflows/workflows/agent-environment-setup/shared/workflows/postman.md

@@ -0,0 +1,40 @@
+---
+command: "/postman"
+description: "Execute Postman MCP operations for workspaces, collections, environments, and runs."
+triggers: ["postman", "collection", "workspace", "environment", "runcollection", "monitor", "mock", "api test"]
+---
+# Postman Workflow
+
+## When to use
+Use this when tasks are primarily about Postman workspaces, collections, environments, monitors, mocks, or collection runs.
+
+## Routing
+- Postman operations and execution: `@backend-specialist`
+- Security/compliance checks on test data: `@security-auditor`
+- Validation quality and assertions: `@test-engineer`
+
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Resolve and pass workspace IDs explicitly when tools require them.
+- Prefer MCP tools (`postman.*` or `postman_*`) over manual JSON/CLI fallback unless fallback is explicitly requested by the user.
+
+## Skill Routing
+- Primary skills: `postman`
+- Supporting skills (optional): `api-designer`, `test-master`
+
+## Workflow steps
+1. Load Postman skill and check integration status (`postman_get_status`).
+2. Resolve workspace ID (user-provided, configured default, or explicit selection).
+3. Execute required MCP operations (list/create/update/run) with explicit IDs.
+4. Summarize outcomes, failures, and next actions with exact object identifiers.
+
+## Verification
+- Confirm requested Postman action completed successfully.
+- Validate response status and key result fields (IDs, counts, failures).
+- Note any skipped steps and required follow-up.
+
+## Output Contract
+- Workspace/context used
+- Actions executed and resulting IDs
+- Pass/fail summary for runs
+- Follow-up or remediation steps