@cubis/foundry 0.3.30 → 0.3.31

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to this project are documented in this file.
 
+## [0.3.31] - 2026-02-27
+
+### Changed
+
+- Renamed repository assets directory from `Ai Agent Workflow` to `workflows`.
+- Updated all CLI/scripts/package references to use the new `workflows` path.
+
 ## [0.3.30] - 2026-02-27
 
 ### Changed

package/bin/cubis.js

@@ -31,7 +31,7 @@ const TERMINAL_VERIFICATION_BLOCK_START_RE = /<!--\s*cbx:terminal:verification:s
 const TERMINAL_VERIFICATION_BLOCK_END_RE = /<!--\s*cbx:terminal:verification:end\s*-->/g;
 const ENGINEERING_RULES_BLOCK_START_RE = /<!--\s*cbx:engineering:auto:start[^>]*-->/g;
 const ENGINEERING_RULES_BLOCK_END_RE = /<!--\s*cbx:engineering:auto:end\s*-->/g;
-const AGENT_ASSETS_SUBDIR = "Ai Agent Workflow";
+const AGENT_ASSETS_SUBDIR = "workflows";
 const COPILOT_ALLOWED_SKILL_FRONTMATTER_KEYS = new Set([
   "compatibility",
   "description",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cubis/foundry",
-  "version": "0.3.30",
+  "version": "0.3.31",
   "description": "Cubis Foundry CLI for workflow-first AI agent environments",
   "type": "module",
   "bin": {
@@ -10,7 +10,7 @@
   },
   "files": [
     "bin",
-    "Ai Agent Workflow",
+    "workflows",
     "README.md",
     "CHANGELOG.md"
   ],
@@ -23,10 +23,10 @@
     "test:smoke": "bash scripts/smoke-workflows.sh",
     "test:all": "npm run test:attributes && npm run test:smoke",
     "test:all:strict": "npm run test:attributes:strict && npm run test:smoke",
-    "generate:powers": "node \"Ai Agent Workflow/scripts/generate-powers.mjs\"",
-    "generate:powers:force": "node \"Ai Agent Workflow/scripts/generate-powers.mjs\" --force",
-    "generate:powers:from-skills": "node \"Ai Agent Workflow/scripts/generate-powers.mjs\" --from-skills",
-    "generate:powers:sync": "node \"Ai Agent Workflow/scripts/generate-powers.mjs\" --sync-skills --force"
+    "generate:powers": "node \"workflows/scripts/generate-powers.mjs\"",
+    "generate:powers:force": "node \"workflows/scripts/generate-powers.mjs\" --force",
+    "generate:powers:from-skills": "node \"workflows/scripts/generate-powers.mjs\" --from-skills",
+    "generate:powers:sync": "node \"workflows/scripts/generate-powers.mjs\" --sync-skills --force"
   },
   "engines": {
     "node": ">=18.17"

package/{Ai Agent Workflow/powers/database-design/POWER.md → workflows/powers/database-design/POWER.md}

@@ -8,6 +8,6 @@ description: Database design principles and decision-making. Schema design, inde
 This is a compatibility power wrapper for the `database-design` skill.
 
 Primary source:
-- `Ai Agent Workflow/skills/database-design/SKILL.md`
+- `workflows/skills/database-design/SKILL.md`
 
 Use this folder for power-specific extensions when needed.

package/{Ai Agent Workflow/powers/database-design/SKILL.md → workflows/powers/database-design/SKILL.md}

@@ -6,6 +6,6 @@ description: Database design principles and decision-making. Schema design, inde
 # database-design
 
 This power mirrors the base skill:
-- `Ai Agent Workflow/skills/database-design/SKILL.md`
+- `workflows/skills/database-design/SKILL.md`
 
 When both exist, prefer the base skill as source of truth unless power-specific overrides are added here.

package/{Ai Agent Workflow/powers/database-skills/engines/mongodb/POWER.md → workflows/powers/database-skills/engines/mongodb/POWER.md}

@@ -1,7 +1,7 @@
 # mongodb
 
 Source skill:
-- `Ai Agent Workflow/skills/database-skills/skills/mongodb/SKILL.md`
+- `workflows/skills/database-skills/skills/mongodb/SKILL.md`
 
 Focus:
 - Access-pattern-first schema design

package/{Ai Agent Workflow/powers/database-skills/engines/mysql/POWER.md → workflows/powers/database-skills/engines/mysql/POWER.md}

@@ -1,7 +1,7 @@
 # mysql
 
 Source skill:
-- `Ai Agent Workflow/skills/database-skills/skills/mysql/SKILL.md`
+- `workflows/skills/database-skills/skills/mysql/SKILL.md`
 
 Focus:
 - Composite/covering index design

package/{Ai Agent Workflow/powers/database-skills/engines/neki/POWER.md → workflows/powers/database-skills/engines/neki/POWER.md}

@@ -1,7 +1,7 @@
 # neki
 
 Source skill:
-- `Ai Agent Workflow/skills/database-skills/skills/neki/SKILL.md`
+- `workflows/skills/database-skills/skills/neki/SKILL.md`
 
 Focus:
 - Shard key and locality planning

package/{Ai Agent Workflow/powers/database-skills/engines/postgres/POWER.md → workflows/powers/database-skills/engines/postgres/POWER.md}

@@ -1,7 +1,7 @@
 # postgres
 
 Source skill:
-- `Ai Agent Workflow/skills/database-skills/skills/postgres/SKILL.md`
+- `workflows/skills/database-skills/skills/postgres/SKILL.md`
 
 Focus:
 - Multicolumn/partial/INCLUDE indexes

package/{Ai Agent Workflow/powers/database-skills/engines/redis/POWER.md → workflows/powers/database-skills/engines/redis/POWER.md}

@@ -1,7 +1,7 @@
 # redis
 
 Source skill:
-- `Ai Agent Workflow/skills/database-skills/skills/redis/SKILL.md`
+- `workflows/skills/database-skills/skills/redis/SKILL.md`
 
 Focus:
 - Key schema as access index

package/{Ai Agent Workflow/powers/database-skills/engines/sqlite/POWER.md → workflows/powers/database-skills/engines/sqlite/POWER.md}

@@ -1,7 +1,7 @@
 # sqlite
 
 Source skill:
-- `Ai Agent Workflow/skills/database-skills/skills/sqlite/SKILL.md`
+- `workflows/skills/database-skills/skills/sqlite/SKILL.md`
 
 Focus:
 - `EXPLAIN QUERY PLAN` verification

package/{Ai Agent Workflow/powers/database-skills/engines/supabase/POWER.md → workflows/powers/database-skills/engines/supabase/POWER.md}

@@ -1,7 +1,7 @@
 # supabase
 
 Source skill:
-- `Ai Agent Workflow/skills/database-skills/skills/supabase/SKILL.md`
+- `workflows/skills/database-skills/skills/supabase/SKILL.md`
 
 Focus:
 - RLS policy correctness and predicate indexing

package/{Ai Agent Workflow/powers/database-skills/engines/vitess/POWER.md → workflows/powers/database-skills/engines/vitess/POWER.md}

@@ -1,7 +1,7 @@
 # vitess
 
 Source skill:
-- `Ai Agent Workflow/skills/database-skills/skills/vitess/SKILL.md`
+- `workflows/skills/database-skills/skills/vitess/SKILL.md`
 
 Focus:
 - Vindex and VSchema routing quality

package/{Ai Agent Workflow/scripts/generate-powers.mjs → workflows/scripts/generate-powers.mjs}

@@ -11,7 +11,7 @@
  *   2. powers/<name>/SKILL.md  ← fallback (local override only)
  *
  * Usage:
- *   node "Ai Agent Workflow/scripts/generate-powers.mjs" [--dry-run] [--force] [--from-skills] [--sync-skills]
+ *   node "workflows/scripts/generate-powers.mjs" [--dry-run] [--force] [--from-skills] [--sync-skills]
  *
  * Options:
  *   --dry-run      Preview changes without writing files
@@ -27,7 +27,7 @@ import { promises as fs } from "node:fs";
 
 const __dirname = path.dirname(fileURLToPath(import.meta.url));
 const ROOT = path.resolve(__dirname, "..", "..");
-const ASSETS_ROOT = path.join(ROOT, "Ai Agent Workflow");
+const ASSETS_ROOT = path.join(ROOT, "workflows");
 const POWERS_ROOT = path.join(ASSETS_ROOT, "powers");
 const SKILLS_ROOT = path.join(ASSETS_ROOT, "skills");
 

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/codex/agents/backend-specialist.md → workflows/workflows/agent-environment-setup/platforms/antigravity/agents/backend-specialist.md}

@@ -260,4 +260,4 @@ After editing any file:
 
 ---
 
-> **Note:** For database-heavy backend work, route through `database-skills` plus `Ai Agent Workflow/powers/database-skills`, and use `database-design`/`database-optimizer` for focused schema/tuning decisions so indexing, pagination, query-plan evidence, and rollback stay explicit.
+> **Note:** For database-heavy backend work, route through `database-skills` plus `workflows/powers/database-skills`, and use `database-design`/`database-optimizer` for focused schema/tuning decisions so indexing, pagination, query-plan evidence, and rollback stay explicit.

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/codex/agents/database-architect.md → workflows/workflows/agent-environment-setup/platforms/antigravity/agents/database-architect.md}

@@ -214,8 +214,8 @@ After database changes:
 1. Load `database-skills` as the core package.
 2. Use `database-design` for schema and migration design choices.
 3. Use `database-optimizer` for query-plan and tuning triage.
-4. Load power bridge: `Ai Agent Workflow/powers/database-skills/POWER.md`.
-5. Pick engine wrapper in `Ai Agent Workflow/powers/database-skills/engines/<engine>/POWER.md`.
+4. Load power bridge: `workflows/powers/database-skills/POWER.md`.
+5. Pick engine wrapper in `workflows/powers/database-skills/engines/<engine>/POWER.md`.
 6. Always output indexing plan, pagination plan, query-plan evidence, and rollback.
 
 ## When You Should Be Used
@@ -232,4 +232,4 @@ After database changes:
 
 ---
 
-> **Note:** Use `database-skills` as primary hub. Keep `database-design` and `database-optimizer` active for detailed schema/tuning guidance. Use `Ai Agent Workflow/powers/database-skills` for power-mode routing, especially engine wrappers (`postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`).
+> **Note:** Use `database-skills` as primary hub. Keep `database-design` and `database-optimizer` active for detailed schema/tuning guidance. Use `workflows/powers/database-skills` for power-mode routing, especially engine wrappers (`postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`).

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/agents/performance-optimizer.md → workflows/workflows/agent-environment-setup/platforms/antigravity/agents/performance-optimizer.md}

@@ -186,4 +186,4 @@ What's slow?
 
 > **Remember:** Users don't care about benchmarks. They care about feeling fast.
 
-> **Database path:** For query/storage bottlenecks, route through `database-skills` and `Ai Agent Workflow/powers/database-skills`, and lean on `database-design`/`database-optimizer` when narrowing schema vs tuning issues; report index/pagination/plan evidence.
+> **Database path:** For query/storage bottlenecks, route through `database-skills` and `workflows/powers/database-skills`, and lean on `database-design`/`database-optimizer` when narrowing schema vs tuning issues; report index/pagination/plan evidence.

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/codex/workflows/database.md → workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/database.md}

@@ -14,7 +14,7 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Core skill hub: `database-skills`
 - Companion skills: `database-design` (schema/migrations), `database-optimizer` (tuning/triage)
 - Mobile/local persistence companion: `drift-flutter`
-- Power bridge: `Ai Agent Workflow/powers/database-skills`
+- Power bridge: `workflows/powers/database-skills`
 - Engine wrappers: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
 
 ## Steps

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/agents/backend-specialist.md → workflows/workflows/agent-environment-setup/platforms/codex/agents/backend-specialist.md}

@@ -260,4 +260,4 @@ After editing any file:
 
 ---
 
-> **Note:** For database-heavy backend work, route through `database-skills` plus `Ai Agent Workflow/powers/database-skills`, and use `database-design`/`database-optimizer` for focused schema/tuning decisions so indexing, pagination, query-plan evidence, and rollback stay explicit.
+> **Note:** For database-heavy backend work, route through `database-skills` plus `workflows/powers/database-skills`, and use `database-design`/`database-optimizer` for focused schema/tuning decisions so indexing, pagination, query-plan evidence, and rollback stay explicit.

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/agents/database-architect.md → workflows/workflows/agent-environment-setup/platforms/codex/agents/database-architect.md}

@@ -214,8 +214,8 @@ After database changes:
 1. Load `database-skills` as the core package.
 2. Use `database-design` for schema and migration design choices.
 3. Use `database-optimizer` for query-plan and tuning triage.
-4. Load power bridge: `Ai Agent Workflow/powers/database-skills/POWER.md`.
-5. Pick engine wrapper in `Ai Agent Workflow/powers/database-skills/engines/<engine>/POWER.md`.
+4. Load power bridge: `workflows/powers/database-skills/POWER.md`.
+5. Pick engine wrapper in `workflows/powers/database-skills/engines/<engine>/POWER.md`.
 6. Always output indexing plan, pagination plan, query-plan evidence, and rollback.
 
 ## When You Should Be Used
@@ -232,4 +232,4 @@ After database changes:
 
 ---
 
-> **Note:** Use `database-skills` as primary hub. Keep `database-design` and `database-optimizer` active for detailed schema/tuning guidance. Use `Ai Agent Workflow/powers/database-skills` for power-mode routing, especially engine wrappers (`postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`).
+> **Note:** Use `database-skills` as primary hub. Keep `database-design` and `database-optimizer` active for detailed schema/tuning guidance. Use `workflows/powers/database-skills` for power-mode routing, especially engine wrappers (`postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`).

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/codex/agents/performance-optimizer.md → workflows/workflows/agent-environment-setup/platforms/codex/agents/performance-optimizer.md}

@@ -186,4 +186,4 @@ What's slow?
 
 > **Remember:** Users don't care about benchmarks. They care about feeling fast.
 
-> **Database path:** For query/storage bottlenecks, route through `database-skills` and `Ai Agent Workflow/powers/database-skills`, and lean on `database-design`/`database-optimizer` when narrowing schema vs tuning issues; report index/pagination/plan evidence.
+> **Database path:** For query/storage bottlenecks, route through `database-skills` and `workflows/powers/database-skills`, and lean on `database-design`/`database-optimizer` when narrowing schema vs tuning issues; report index/pagination/plan evidence.

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/database.md → workflows/workflows/agent-environment-setup/platforms/codex/workflows/database.md}

@@ -14,7 +14,7 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Core skill hub: `database-skills`
 - Companion skills: `database-design` (schema/migrations), `database-optimizer` (tuning/triage)
 - Mobile/local persistence companion: `drift-flutter`
-- Power bridge: `Ai Agent Workflow/powers/database-skills`
+- Power bridge: `workflows/powers/database-skills`
 - Engine wrappers: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
 
 ## Steps

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/agents/backend-specialist.md → workflows/workflows/agent-environment-setup/platforms/copilot/agents/backend-specialist.md}

@@ -273,4 +273,4 @@ After editing any file:
 
 ---
 
-> **Note:** For database-heavy backend work, route through `database-skills` plus `Ai Agent Workflow/powers/database-skills`, and use `database-design`/`database-optimizer` for focused schema/tuning decisions so indexing, pagination, query-plan evidence, and rollback stay explicit.
+> **Note:** For database-heavy backend work, route through `database-skills` plus `workflows/powers/database-skills`, and use `database-design`/`database-optimizer` for focused schema/tuning decisions so indexing, pagination, query-plan evidence, and rollback stay explicit.

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/agents/database-architect.md → workflows/workflows/agent-environment-setup/platforms/copilot/agents/database-architect.md}

@@ -225,8 +225,8 @@ After database changes:
 1. Load `database-skills` as the core package.
 2. Use `database-design` for schema and migration design choices.
 3. Use `database-optimizer` for query-plan and tuning triage.
-4. Load power bridge: `Ai Agent Workflow/powers/database-skills/POWER.md`.
-5. Pick engine wrapper in `Ai Agent Workflow/powers/database-skills/engines/<engine>/POWER.md`.
+4. Load power bridge: `workflows/powers/database-skills/POWER.md`.
+5. Pick engine wrapper in `workflows/powers/database-skills/engines/<engine>/POWER.md`.
 6. Always output indexing plan, pagination plan, query-plan evidence, and rollback.
 
 ## When You Should Be Used
@@ -243,4 +243,4 @@ After database changes:
 
 ---
 
-> **Note:** Use `database-skills` as primary hub. Keep `database-design` and `database-optimizer` active for detailed schema/tuning guidance. Use `Ai Agent Workflow/powers/database-skills` for power-mode routing, especially engine wrappers (`postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`).
+> **Note:** Use `database-skills` as primary hub. Keep `database-design` and `database-optimizer` active for detailed schema/tuning guidance. Use `workflows/powers/database-skills` for power-mode routing, especially engine wrappers (`postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`).

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/agents/performance-optimizer.md → workflows/workflows/agent-environment-setup/platforms/copilot/agents/performance-optimizer.md}

@@ -189,4 +189,4 @@ What's slow?
 
 > **Remember:** Users don't care about benchmarks. They care about feeling fast.
 
-> **Database path:** For query/storage bottlenecks, route through `database-skills` and `Ai Agent Workflow/powers/database-skills`, and lean on `database-design`/`database-optimizer` when narrowing schema vs tuning issues; report index/pagination/plan evidence.
+> **Database path:** For query/storage bottlenecks, route through `database-skills` and `workflows/powers/database-skills`, and lean on `database-design`/`database-optimizer` when narrowing schema vs tuning issues; report index/pagination/plan evidence.

package/{Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/workflows/database.md → workflows/workflows/agent-environment-setup/platforms/copilot/workflows/database.md}

@@ -14,7 +14,7 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Core skill hub: `database-skills`
 - Companion skills: `database-design` (schema/migrations), `database-optimizer` (tuning/triage)
 - Mobile/local persistence companion: `drift-flutter`
-- Power bridge: `Ai Agent Workflow/powers/database-skills`
+- Power bridge: `workflows/powers/database-skills`
 - Engine wrappers: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
 
 ## Steps