@cubis/foundry 0.3.53 → 0.3.55

package/src/cli/workflows/commands.ts

@@ -0,0 +1,163 @@
+import type { Command } from "commander";
+import type {
+  CommandDecorator,
+  WorkflowAction,
+  WorkflowDoctorAction,
+  WorkflowTargetAction,
+} from "../types.js";
+
+export interface WorkflowCommandDeps {
+  withInstallOptions: CommandDecorator;
+  withWorkflowBaseOptions: CommandDecorator;
+  registerConfigKeysSubcommands: (configCommand: Command) => void;
+  runWorkflowInstall: WorkflowAction;
+  runWorkflowRemove: WorkflowTargetAction;
+  runWorkflowRemoveAll: WorkflowAction;
+  runWorkflowPruneSkills: WorkflowAction;
+  runWorkflowSyncRules: WorkflowAction;
+  runWorkflowDoctor: WorkflowDoctorAction;
+  runWorkflowConfig: WorkflowAction;
+  printPlatforms: () => void;
+  defaultSkillProfile: string;
+}
+
+export function registerWorkflowCommands(
+  program: Command,
+  deps: WorkflowCommandDeps,
+) {
+  const workflowsCommand = program
+    .command("workflows")
+    .description(
+      "Install and manage workflow bundles for Antigravity, Codex, and Copilot",
+    );
+
+  workflowsCommand
+    .command("platforms")
+    .description("List workflow platform ids and defaults")
+    .action(deps.printPlatforms);
+
+  deps
+    .withInstallOptions(
+      workflowsCommand
+        .command("install")
+        .description("Install a workflow bundle into the selected platform"),
+    )
+    .action(deps.runWorkflowInstall);
+
+  deps
+    .withWorkflowBaseOptions(
+      workflowsCommand
+        .command("remove <bundle-or-workflow>")
+        .description("Remove an installed bundle or workflow and sync rules")
+        .option("--dry-run", "preview remove and sync without writing files")
+        .option("-y, --yes", "skip interactive confirmation"),
+    )
+    .action(deps.runWorkflowRemove);
+
+  workflowsCommand
+    .command("remove-all")
+    .description(
+      "Remove all CBX-managed generated artifacts (workflows/agents/skills/rules/MCP config)",
+    )
+    .option(
+      "-p, --platform <platform>",
+      "target platform id or 'all' (default: all)",
+      "all",
+    )
+    .option(
+      "--scope <scope>",
+      "target scope: project|global|all (default: all)",
+      "all",
+    )
+    .option(
+      "--target <path>",
+      "remove project-scope artifacts from target project directory",
+    )
+    .option(
+      "--include-credentials",
+      "also remove ~/.cbx/credentials.env when scope includes global",
+    )
+    .option("--dry-run", "preview remove operations without writing files")
+    .option("-y, --yes", "skip interactive confirmation")
+    .action(deps.runWorkflowRemoveAll);
+
+  deps
+    .withWorkflowBaseOptions(
+      workflowsCommand
+        .command("prune-skills")
+        .description(
+          "Prune nested duplicates and out-of-profile installed skills",
+        )
+        .option(
+          "-b, --bundle <bundle>",
+          "bundle id (default: agent-environment-setup)",
+        )
+        .option(
+          "--skill-profile <profile>",
+          "skill prune profile: core|web-backend|full (default: core)",
+          deps.defaultSkillProfile,
+        )
+        .option("--all-skills", "alias for --skill-profile full")
+        .option(
+          "--dry-run",
+          "preview prune operations without deleting files",
+        )
+        .option("-y, --yes", "skip interactive confirmation"),
+    )
+    .action(deps.runWorkflowPruneSkills);
+
+  deps
+    .withWorkflowBaseOptions(
+      workflowsCommand
+        .command("sync-rules")
+        .description(
+          "Rebuild the managed workflow routing block for the selected platform",
+        )
+        .option("--dry-run", "preview managed rule sync without writing files")
+        .option("--json", "output JSON"),
+    )
+    .action(deps.runWorkflowSyncRules);
+
+  deps
+    .withWorkflowBaseOptions(
+      workflowsCommand
+        .command("doctor [platform]")
+        .description(
+          "Validate workflow paths, rule file status, and managed block health",
+        )
+        .option("--json", "output JSON"),
+    )
+    .action(deps.runWorkflowDoctor);
+
+  const workflowsConfigCommand = workflowsCommand
+    .command("config")
+    .description("View or edit cbx_config.json from terminal")
+    .option(
+      "-p, --platform <platform>",
+      "target platform id for MCP target patch",
+    )
+    .option(
+      "--scope <scope>",
+      "config scope: project|workspace|global|user",
+      "global",
+    )
+    .option("--show", "show current config (default when no edit flags)")
+    .option("--edit", "edit Postman default workspace ID interactively")
+    .option("--workspace-id <id|null>", "set postman.defaultWorkspaceId")
+    .option("--clear-workspace-id", "set postman.defaultWorkspaceId to null")
+    .option(
+      "--postman-mode <mode>",
+      "set postman.mcpUrl via mode: minimal|code|full",
+    )
+    .option("--mcp-runtime <runtime>", "set mcp.runtime: docker|local")
+    .option("--mcp-fallback <fallback>", "set mcp.fallback: local|fail|skip")
+    .option("--show-after", "print JSON after update")
+    .option("--dry-run", "preview changes without writing files")
+    .action(deps.runWorkflowConfig);
+
+  deps.registerConfigKeysSubcommands(workflowsConfigCommand);
+
+  workflowsCommand.action(() => {
+    workflowsCommand.help();
+  });
+}

package/src/cli/workflows/index.ts

@@ -0,0 +1 @@
+export {};

package/tsconfig.cli.json

@@ -0,0 +1,19 @@
+{
+  "compilerOptions": {
+    "target": "ES2022",
+    "module": "NodeNext",
+    "moduleResolution": "NodeNext",
+    "lib": ["ES2022"],
+    "outDir": "dist/cli",
+    "rootDir": "src/cli",
+    "strict": false,
+    "esModuleInterop": true,
+    "skipLibCheck": true,
+    "forceConsistentCasingInFileNames": true,
+    "resolveJsonModule": true,
+    "declaration": false,
+    "sourceMap": true
+  },
+  "include": ["src/cli/**/*.ts"],
+  "exclude": ["node_modules", "dist"]
+}

package/workflows/workflows/agent-environment-setup/platforms/antigravity/rules/GEMINI.md

@@ -14,18 +14,18 @@ This file defines mandatory behavior for Antigravity projects installed via `cbx
 - Gemini commands: `.gemini/commands`
 - Rules file: `.agent/rules/GEMINI.md`
 
-## Startup Transparency (Required)
+## Startup Transparency (Minimal)
 
-Before executing workflows, agents, or code edits, publish a short `Decision Log` that is visible to the user:
+Before substantial work, publish one short status line only:
 
-1. Rule file(s) read at startup (at minimum `.agent/rules/GEMINI.md`, plus any additional rule files loaded).
-2. MCP status: confirm Foundry MCP server (`cbx-mcp`) is reachable; if unavailable, declare "MCP offline — fallback mode" and continue without blocking.
-3. Workflow decision (`/workflow` or direct mode) and why it was chosen.
-4. Agent routing decision (`@agent` or direct mode) and why it was chosen.
-5. Skill loading decision: skill IDs selected, how they were discovered, and why.
+`Status: rules=<files> | mcp=<ok|offline> | route=<workflow|direct> | agent=<agent|direct> | skills=<ids|none>`
 
-If routing changes during the task, publish a `Decision Update` before continuing.
-Keep this user-visible summary concise and factual; do not expose private chain-of-thought.
+Rules:
+
+1. Emit this once at task start; send an update only when routing materially changes.
+2. Do not print tool-call transcripts (for example: "Explored ...", "Ran command ...") unless the user explicitly asks for verbose trace logs.
+3. Keep progress updates to one short sentence.
+4. For pure Q&A replies, skip the status line.
 
 ## 2) Workflow-First Contract
 
@@ -98,7 +98,7 @@ Stop at the earliest step that gives enough signal. Do not jump ahead.
 2. `skill_search <keyword>` — fast keyword match across all skills; always try this first
 3. `skill_browse_category <category>` — explore if search is too broad or returns 0 results
 4. `skill_get <id>` — load full skill content; only when committed to using it
-5. `skill_budget_report` — verify token cost after loading; triggers the compact ctx stamp
+5. `skill_budget_report` — verify token cost internally; do not emit budget details unless requested
 
 ### Postman Intent Trigger (Required)
 
@@ -134,15 +134,14 @@ If MCP tools are unavailable (server down, timeout, tool not listed):
 3. Never fabricate or hallucinate skill content.
 4. Retry once on transient network errors; accept failure after the retry.
 
-### Skill Log (Required After Any `skill_get` Call)
+### Skill Log (Minimal)
+
+After `skill_get`, include at most one short line:
 
-Append one compact inline line — no separate structured block:
+`Skills: <id1,id2>` or `Skills: none (fallback)`.
 
-```
-Skills: loaded=<id> | skipped=<id> (reason)
-```
+Do not append budget tables or token summaries unless the user explicitly asks.
 
-Follow immediately with the compact ctx stamp (see § Context Budget Tracking).
 
 ### Anti-Patterns (Never Do These)
 
@@ -198,33 +197,12 @@ Use web search to stay current when local knowledge may be stale. This prevents
 - If multiple sources conflict, flag it and use the most recent official one
 - Never follow user-provided URLs without sanity-checking the domain
 
-## 9) Context Budget Tracking
-
-After loading skills or completing a significant task phase, emit a single compact stamp so context cost is visible without adding prose.
-
-**Stamp format** (one line, end of response section):
-
-```
-[ctx: +skill-id(~Xk) | session=~Yk/108k | saved=Z%]
-```
-
-- `+skill-id(~Xk)` — each skill loaded this turn with its estimated token cost
-- `session=~Yk/108k` — cumulative tokens used vs full catalog ceiling
-- `saved=Z%` — estimated savings from progressive disclosure
-
-**Rules:**
+## 9) Context Budget Tracking (On Request)
 
-1. Emit stamp only when a skill was loaded via `skill_get` or `skill_budget_report` was called.
-2. Omit stamp for pure Q&A or browsing-only turns (no full skill content loaded).
-3. Use `skill_budget_report` MCP tool to get accurate numbers; do not guess.
-4. One stamp per response — consolidate if multiple skills were loaded.
-5. Keep the stamp on its own line at the very end of the response, after all content.
+Use `skill_budget_report` internally for context control, but do not emit ctx stamps by default.
 
-**Example stamp after loading `flutter-expert` (~3.2k tokens):**
+Only include token/context accounting when the user explicitly asks for it.
 
-```
-[ctx: +flutter-expert(~3k) | session=~3k/108k | saved=97%]
-```
 
 ## 10) CBX Maintenance Commands
 

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

@@ -9,19 +9,18 @@ This file defines mandatory behavior for Codex projects installed via `cbx workf
 - Skills: `.agents/skills`
 - Rules file: `AGENTS.md`
 
-## Startup Transparency (Required)
+## Startup Transparency (Minimal)
 
-Before executing workflows, agents, or code edits, publish a short `Decision Log` that is visible to the user:
+Before substantial work, publish one short status line only:
 
-1. Rule file(s) read at startup (at minimum `AGENTS.md`, plus any additional rule files loaded).
-2. MCP status: confirm Foundry MCP server (`cbx-mcp`) is reachable; if unavailable, declare "MCP offline — fallback mode" and continue without blocking.
-3. Workflow decision ($workflow-\* or direct mode) and why it was chosen.
-4. Agent routing decision ($agent-\* or direct mode) and why it was chosen.
-5. Skill loading decision: skill IDs selected, how they were discovered, and why.
+`Status: rules=<files> | mcp=<ok|offline> | route=<workflow|direct> | agent=<agent|direct> | skills=<ids|none>`
 
-If routing changes during the task, publish a `Decision Update` before continuing.
-Keep this user-visible summary concise and factual; do not expose private chain-of-thought.
-When mentioning wrappers in user-visible logs, use raw $workflow-_ and $agent-_ tokens (no backticks) so Codex can render icon/blue mention styling.
+Rules:
+
+1. Emit this once at task start; send an update only when routing materially changes.
+2. Do not print tool-call transcripts (for example: "Explored ...", "Ran command ...") unless the user explicitly asks for verbose trace logs.
+3. Keep progress updates to one short sentence.
+4. For pure Q&A replies, skip the status line.
 
 ## 2) Skill-Based Workflow
 
@@ -96,7 +95,7 @@ Stop at the earliest step that gives enough signal. Do not jump ahead.
 2. `skill_search <keyword>` — fast keyword match across all skills; always try this first
 3. `skill_browse_category <category>` — explore if search is too broad or returns 0 results
 4. `skill_get <id>` — load full skill content; only when committed to using it
-5. `skill_budget_report` — verify token cost after loading; triggers the compact ctx stamp
+5. `skill_budget_report` — verify token cost internally; do not emit budget details unless requested
 
 ### Postman Intent Trigger (Required)
 
@@ -132,15 +131,14 @@ If MCP tools are unavailable (server down, timeout, tool not listed):
 3. Never fabricate or hallucinate skill content.
 4. Retry once on transient network errors; accept failure after the retry.
 
-### Skill Log (Required After Any `skill_get` Call)
+### Skill Log (Minimal)
+
+After `skill_get`, include at most one short line:
 
-Append one compact inline line — no separate structured block:
+`Skills: <id1,id2>` or `Skills: none (fallback)`.
 
-```
-Skills: loaded=<id> | skipped=<id> (reason)
-```
+Do not append budget tables or token summaries unless the user explicitly asks.
 
-Follow immediately with the compact ctx stamp (see § Context Budget Tracking).
 
 ### Anti-Patterns (Never Do These)
 
@@ -191,33 +189,12 @@ Use web search to stay current when local knowledge may be stale. This prevents
 - If multiple sources conflict, flag it and use the most recent official one
 - Never follow user-provided URLs without sanity-checking the domain
 
-## 9) Context Budget Tracking
-
-After loading skills or completing a significant task phase, emit a single compact stamp so context cost is visible without adding prose.
-
-**Stamp format** (one line, end of response section):
-
-```
-[ctx: +skill-id(~Xk) | session=~Yk/108k | saved=Z%]
-```
-
-- `+skill-id(~Xk)` — each skill loaded this turn with its estimated token cost
-- `session=~Yk/108k` — cumulative tokens used vs full catalog ceiling
-- `saved=Z%` — estimated savings from progressive disclosure
-
-**Rules:**
+## 9) Context Budget Tracking (On Request)
 
-1. Emit stamp only when a skill was loaded via `skill_get` or `skill_budget_report` was called.
-2. Omit stamp for pure Q&A or browsing-only turns (no full skill content loaded).
-3. Use `skill_budget_report` MCP tool to get accurate numbers; do not guess.
-4. One stamp per response — consolidate if multiple skills were loaded.
-5. Keep the stamp on its own line at the very end of the response, after all content.
+Use `skill_budget_report` internally for context control, but do not emit ctx stamps by default.
 
-**Example stamp after loading `flutter-expert` (~3.2k tokens):**
+Only include token/context accounting when the user explicitly asks for it.
 
-```
-[ctx: +flutter-expert(~3k) | session=~3k/108k | saved=97%]
-```
 
 ## 10) CBX Maintenance Commands
 

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

@@ -11,18 +11,18 @@ This `AGENTS.md` exists for cross-tool compatibility (for example Codex/Cursor s
 - Prompt files: `.github/prompts`
 - Rules file (project): `.github/copilot-instructions.md`
 
-## Startup Transparency (Required)
+## Startup Transparency (Minimal)
 
-Before executing workflows, agents, or code edits, publish a short `Decision Log` that is visible to the user:
+Before substantial work, publish one short status line only:
 
-1. Rule file(s) read at startup (at minimum `.github/copilot-instructions.md`, plus any additional rule files loaded).
-2. MCP status: confirm Foundry MCP server (`cbx-mcp`) is reachable; if unavailable, declare "MCP offline — fallback mode" and continue without blocking.
-3. Workflow decision (`/workflow` or direct mode) and why it was chosen.
-4. Agent routing decision (`@agent` or direct mode) and why it was chosen.
-5. Skill loading decision: skill IDs selected, how they were discovered, and why.
+`Status: rules=<files> | mcp=<ok|offline> | route=<workflow|direct> | agent=<agent|direct> | skills=<ids|none>`
 
-If routing changes during the task, publish a `Decision Update` before continuing.
-Keep this user-visible summary concise and factual; do not expose private chain-of-thought.
+Rules:
+
+1. Emit this once at task start; send an update only when routing materially changes.
+2. Do not print tool-call transcripts (for example: "Explored ...", "Ran command ...") unless the user explicitly asks for verbose trace logs.
+3. Keep progress updates to one short sentence.
+4. For pure Q&A replies, skip the status line.
 
 ## 2) Workflow-First Contract
 
@@ -103,7 +103,7 @@ Stop at the earliest step that gives enough signal. Do not jump ahead.
 2. `skill_search <keyword>` — fast keyword match across all skills; always try this first
 3. `skill_browse_category <category>` — explore if search is too broad or returns 0 results
 4. `skill_get <id>` — load full skill content; only when committed to using it
-5. `skill_budget_report` — verify token cost after loading; triggers the compact ctx stamp
+5. `skill_budget_report` — verify token cost internally; do not emit budget details unless requested
 
 ### Postman Intent Trigger (Required)
 
@@ -139,15 +139,14 @@ If MCP tools are unavailable (server down, timeout, tool not listed):
 3. Never fabricate or hallucinate skill content.
 4. Retry once on transient network errors; accept failure after the retry.
 
-### Skill Log (Required After Any `skill_get` Call)
+### Skill Log (Minimal)
+
+After `skill_get`, include at most one short line:
 
-Append one compact inline line — no separate structured block:
+`Skills: <id1,id2>` or `Skills: none (fallback)`.
 
-```
-Skills: loaded=<id> | skipped=<id> (reason)
-```
+Do not append budget tables or token summaries unless the user explicitly asks.
 
-Follow immediately with the compact ctx stamp (see § Context Budget Tracking).
 
 ### Anti-Patterns (Never Do These)
 
@@ -198,33 +197,12 @@ Use web search to stay current when local knowledge may be stale. This prevents
 - If multiple sources conflict, flag it and use the most recent official one
 - Never follow user-provided URLs without sanity-checking the domain
 
-## 10) Context Budget Tracking
-
-After loading skills or completing a significant task phase, emit a single compact stamp so context cost is visible without adding prose.
-
-**Stamp format** (one line, end of response section):
-
-```
-[ctx: +skill-id(~Xk) | session=~Yk/108k | saved=Z%]
-```
-
-- `+skill-id(~Xk)` — each skill loaded this turn with its estimated token cost
-- `session=~Yk/108k` — cumulative tokens used vs full catalog ceiling
-- `saved=Z%` — estimated savings from progressive disclosure
-
-**Rules:**
+## 10) Context Budget Tracking (On Request)
 
-1. Emit stamp only when a skill was loaded via `skill_get` or `skill_budget_report` was called.
-2. Omit stamp for pure Q&A or browsing-only turns (no full skill content loaded).
-3. Use `skill_budget_report` MCP tool to get accurate numbers; do not guess.
-4. One stamp per response — consolidate if multiple skills were loaded.
-5. Keep the stamp on its own line at the very end of the response, after all content.
+Use `skill_budget_report` internally for context control, but do not emit ctx stamps by default.
 
-**Example stamp after loading `flutter-expert` (~3.2k tokens):**
+Only include token/context accounting when the user explicitly asks for it.
 
-```
-[ctx: +flutter-expert(~3k) | session=~3k/108k | saved=97%]
-```
 
 ## 11) CBX Maintenance Commands
 

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

@@ -10,18 +10,18 @@ This file defines mandatory behavior for GitHub Copilot projects installed via `
 - Prompt files: `.github/prompts`
 - Rules file (project): `.github/copilot-instructions.md`
 
-## Startup Transparency (Required)
+## Startup Transparency (Minimal)
 
-Before executing workflows, agents, or code edits, publish a short `Decision Log` that is visible to the user:
+Before substantial work, publish one short status line only:
 
-1. Rule file(s) read at startup (at minimum `.github/copilot-instructions.md`, plus any additional rule files loaded).
-2. MCP status: confirm Foundry MCP server (`cbx-mcp`) is reachable; if unavailable, declare "MCP offline — fallback mode" and continue without blocking.
-3. Workflow decision (`/workflow` or direct mode) and why it was chosen.
-4. Agent routing decision (`@agent` or direct mode) and why it was chosen.
-5. Skill loading decision: skill IDs selected, how they were discovered, and why.
+`Status: rules=<files> | mcp=<ok|offline> | route=<workflow|direct> | agent=<agent|direct> | skills=<ids|none>`
 
-If routing changes during the task, publish a `Decision Update` before continuing.
-Keep this user-visible summary concise and factual; do not expose private chain-of-thought.
+Rules:
+
+1. Emit this once at task start; send an update only when routing materially changes.
+2. Do not print tool-call transcripts (for example: "Explored ...", "Ran command ...") unless the user explicitly asks for verbose trace logs.
+3. Keep progress updates to one short sentence.
+4. For pure Q&A replies, skip the status line.
 
 ## 2) Workflow-First Contract
 
@@ -102,7 +102,7 @@ Stop at the earliest step that gives enough signal. Do not jump ahead.
 2. `skill_search <keyword>` — fast keyword match across all skills; always try this first
 3. `skill_browse_category <category>` — explore if search is too broad or returns 0 results
 4. `skill_get <id>` — load full skill content; only when committed to using it
-5. `skill_budget_report` — verify token cost after loading; triggers the compact ctx stamp
+5. `skill_budget_report` — verify token cost internally; do not emit budget details unless requested
 
 ### Postman Intent Trigger (Required)
 
@@ -138,15 +138,14 @@ If MCP tools are unavailable (server down, timeout, tool not listed):
 3. Never fabricate or hallucinate skill content.
 4. Retry once on transient network errors; accept failure after the retry.
 
-### Skill Log (Required After Any `skill_get` Call)
+### Skill Log (Minimal)
+
+After `skill_get`, include at most one short line:
 
-Append one compact inline line — no separate structured block:
+`Skills: <id1,id2>` or `Skills: none (fallback)`.
 
-```
-Skills: loaded=<id> | skipped=<id> (reason)
-```
+Do not append budget tables or token summaries unless the user explicitly asks.
 
-Follow immediately with the compact ctx stamp (see § Context Budget Tracking).
 
 ### Anti-Patterns (Never Do These)
 
@@ -197,33 +196,12 @@ Use web search to stay current when local knowledge may be stale. This prevents
 - If multiple sources conflict, flag it and use the most recent official one
 - Never follow user-provided URLs without sanity-checking the domain
 
-## 10) Context Budget Tracking
-
-After loading skills or completing a significant task phase, emit a single compact stamp so context cost is visible without adding prose.
-
-**Stamp format** (one line, end of response section):
-
-```
-[ctx: +skill-id(~Xk) | session=~Yk/108k | saved=Z%]
-```
-
-- `+skill-id(~Xk)` — each skill loaded this turn with its estimated token cost
-- `session=~Yk/108k` — cumulative tokens used vs full catalog ceiling
-- `saved=Z%` — estimated savings from progressive disclosure
-
-**Rules:**
+## 10) Context Budget Tracking (On Request)
 
-1. Emit stamp only when a skill was loaded via `skill_get` or `skill_budget_report` was called.
-2. Omit stamp for pure Q&A or browsing-only turns (no full skill content loaded).
-3. Use `skill_budget_report` MCP tool to get accurate numbers; do not guess.
-4. One stamp per response — consolidate if multiple skills were loaded.
-5. Keep the stamp on its own line at the very end of the response, after all content.
+Use `skill_budget_report` internally for context control, but do not emit ctx stamps by default.
 
-**Example stamp after loading `flutter-expert` (~3.2k tokens):**
+Only include token/context accounting when the user explicitly asks for it.
 
-```
-[ctx: +flutter-expert(~3k) | session=~3k/108k | saved=97%]
-```
 
 ## 11) CBX Maintenance Commands