@cubis/foundry 0.3.67 → 0.3.69

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

@@ -1,40 +0,0 @@
-# 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 <project|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 <project|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
-```
-
-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/copilot/skills/postman/references/troubleshooting.md

@@ -1,69 +0,0 @@
-# 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 in the same install scope:
-
-```bash
-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 <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.
-
-## 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.
-
-## Quota-safe execution
-
-Preferred path:
-
-1. Use direct Postman MCP collection execution first (`postman.runCollection` or equivalent).
-2. If that fails, stop and classify the error.
-3. Recommend Postman CLI as the safe default secondary path.
-4. Use monitor execution only when the user explicitly asks for monitor-based cloud execution.
-
-Do not auto-fallback from `runCollection` to `runMonitor`.
-
-## Error classification
-
-### `limitBreachedError` or "breached monitoring usage limit"
-
-- This is monitor quota exhaustion, not generic API failure.
-- Do not retry monitor runs.
-- Do not reinterpret it as an MCP auth issue.
-- Tell the user to check Postman monitoring usage and billing-period reset in the Postman dashboard.
-- Recommend Postman CLI as the next execution path.
-
-### `429` or rate-limited API response
-
-- This is Postman API rate limiting.
-- Reduce request burst, add backoff, and retry later.
-- Do not treat it as monitor quota exhaustion.
-
-### `runCollection` timeout without quota/rate-limit signal
-
-- Treat this as direct MCP/runtime timeout.
-- Do not auto-convert to monitor execution.
-- Recommend Postman CLI or a smaller-scope rerun.
-
-## Monitor usage facts
-
-- Monitor usage is separate from Postman API RPM limits.
-- Monitor usage is consumed by request count, region count, and auth requests.
-- Monitor runtime caps are separate from monitor quota and do not imply usage remains available.

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

@@ -1,20 +0,0 @@
-# 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/skills/powershell-windows/SKILL.md

@@ -1,165 +0,0 @@
----
-name: powershell-windows
-description: PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.
----
-# PowerShell Windows Patterns
-
-> Critical patterns and pitfalls for Windows PowerShell.
-
----
-
-## 1. Operator Syntax Rules
-
-### CRITICAL: Parentheses Required
-
-| ❌ Wrong | ✅ Correct |
-|----------|-----------|
-| `if (Test-Path "a" -or Test-Path "b")` | `if ((Test-Path "a") -or (Test-Path "b"))` |
-| `if (Get-Item $x -and $y -eq 5)` | `if ((Get-Item $x) -and ($y -eq 5))` |
-
-**Rule:** Each cmdlet call MUST be in parentheses when using logical operators.
-
----
-
-## 2. Unicode/Emoji Restriction
-
-### CRITICAL: No Unicode in Scripts
-
-| Purpose | ❌ Don't Use | ✅ Use |
-|---------|-------------|--------|
-| Success | ✅ ✓ | [OK] [+] |
-| Error | ❌ ✗ 🔴 | [!] [X] |
-| Warning | ⚠️ 🟡 | [*] [WARN] |
-| Info | ℹ️ 🔵 | [i] [INFO] |
-| Progress | ⏳ | [...] |
-
-**Rule:** Use ASCII characters only in PowerShell scripts.
-
----
-
-## 3. Null Check Patterns
-
-### Always Check Before Access
-
-| ❌ Wrong | ✅ Correct |
-|----------|-----------|
-| `$array.Count -gt 0` | `$array -and $array.Count -gt 0` |
-| `$text.Length` | `if ($text) { $text.Length }` |
-
----
-
-## 4. String Interpolation
-
-### Complex Expressions
-
-| ❌ Wrong | ✅ Correct |
-|----------|-----------|
-| `"Value: $($obj.prop.sub)"` | Store in variable first |
-
-**Pattern:**
-```
-$value = $obj.prop.sub
-Write-Output "Value: $value"
-```
-
----
-
-## 5. Error Handling
-
-### ErrorActionPreference
-
-| Value | Use |
-|-------|-----|
-| Stop | Development (fail fast) |
-| Continue | Production scripts |
-| SilentlyContinue | When errors expected |
-
-### Try/Catch Pattern
-
-- Don't return inside try block
-- Use finally for cleanup
-- Return after try/catch
-
----
-
-## 6. File Paths
-
-### Windows Path Rules
-
-| Pattern | Use |
-|---------|-----|
-| Literal path | `C:\Users\User\file.txt` |
-| Variable path | `Join-Path $env:USERPROFILE "file.txt"` |
-| Relative | `Join-Path $ScriptDir "data"` |
-
-**Rule:** Use Join-Path for cross-platform safety.
-
----
-
-## 7. Array Operations
-
-### Correct Patterns
-
-| Operation | Syntax |
-|-----------|--------|
-| Empty array | `$array = @()` |
-| Add item | `$array += $item` |
-| ArrayList add | `$list.Add($item) | Out-Null` |
-
----
-
-## 8. JSON Operations
-
-### CRITICAL: Depth Parameter
-
-| ❌ Wrong | ✅ Correct |
-|----------|-----------|
-| `ConvertTo-Json` | `ConvertTo-Json -Depth 10` |
-
-**Rule:** Always specify `-Depth` for nested objects.
-
-### File Operations
-
-| Operation | Pattern |
-|-----------|---------|
-| Read | `Get-Content "file.json" -Raw | ConvertFrom-Json` |
-| Write | `$data | ConvertTo-Json -Depth 10 | Out-File "file.json" -Encoding UTF8` |
-
----
-
-## 9. Common Errors
-
-| Error Message | Cause | Fix |
-|---------------|-------|-----|
-| "parameter 'or'" | Missing parentheses | Wrap cmdlets in () |
-| "Unexpected token" | Unicode character | Use ASCII only |
-| "Cannot find property" | Null object | Check null first |
-| "Cannot convert" | Type mismatch | Use .ToString() |
-
----
-
-## 10. Script Template
-
-```powershell
-# Strict mode
-Set-StrictMode -Version Latest
-$ErrorActionPreference = "Continue"
-
-# Paths
-$ScriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
-
-# Main
-try {
-    # Logic here
-    Write-Output "[OK] Done"
-    exit 0
-}
-catch {
-    Write-Warning "Error: $_"
-    exit 1
-}
-```
-
----
-
-> **Remember:** PowerShell has unique syntax rules. Parentheses, ASCII-only, and null checks are non-negotiable.