@soleri/forge 5.14.1 → 5.14.3

package/src/skills/deliver-and-ship.md

@@ -0,0 +1,123 @@
+---
+name: deliver-and-ship
+description: >
+  Use when the user says "ship it", "ready to deploy", "package", "release",
+  "pre-PR check", "delivery checklist", "is this ready", "final review", or mentions
+  shipping, deploying, packaging, or releasing work. Runs pre-delivery quality gates
+  to ensure nothing ships without passing stability, knowledge capture, and code quality checks.
+---
+
+# Deliver & Ship — Quality Gate Runner
+
+Run all pre-delivery quality gates before shipping. This ensures nothing leaves without passing stability checks, knowledge capture, and code quality verification.
+
+## When to Use
+
+When work is considered "done" and ready to be committed, PR'd, or deployed. This is the last checkpoint before code leaves the developer's hands.
+
+## Orchestration Sequence
+
+### Step 1: Code Quality
+
+Run the project's linter, formatter, and type checker on all modified files:
+
+1. Check for lint/format scripts in `package.json` (or equivalent)
+2. Run `typecheck` / `tsc --noEmit` if TypeScript
+3. Run any project-specific quality gates (clippy for Rust, mypy for Python, etc.)
+
+Any type error or lint failure is a blocker.
+
+### Step 2: Test Suite
+
+Run the full test suite to catch regressions:
+
+```
+YOUR_AGENT_core op:admin_health
+```
+
+Verify the agent itself is healthy, then run project tests. All tests must pass.
+
+### Step 3: Stability Assessment
+
+Classify the changes as safe or breaking:
+
+- **Safe**: Internal refactors, bug fixes, additive features (new exports, new ops)
+- **Breaking**: Removed exports, changed signatures, renamed public APIs, schema migrations
+- Breaking changes need migration guidance in the commit/PR description
+
+### Step 4: Knowledge Audit
+
+Check if patterns discovered during this work session should be captured before shipping:
+
+```
+YOUR_AGENT_core op:memory_search
+  params: { query: "current session" }
+```
+
+```
+YOUR_AGENT_core op:brain_stats
+```
+
+Look for:
+
+- Bug fixes that reveal an anti-pattern worth capturing
+- New patterns that should be in the vault for next time
+- Architectural decisions that need documenting
+
+Uncaptured knowledge is lost knowledge. If something should be captured:
+
+```
+YOUR_AGENT_core op:capture_knowledge
+  params: {
+    title: "<what was learned>",
+    description: "<the pattern or anti-pattern>",
+    type: "pattern",
+    tags: ["<relevant-tags>"]
+  }
+```
+
+### Step 5: Commit Quality
+
+Verify commit messages follow conventional commits:
+
+- `feat:` for new features
+- `fix:` for bug fixes
+- `refactor:` for refactors
+- `chore:` for maintenance
+- No AI attribution (blocked by engine rules)
+
+### Step 6: Delivery Report
+
+Present a checklist:
+
+- [ ] Code quality: pass/fail (Step 1)
+- [ ] Tests: pass/fail (Step 2)
+- [ ] Stability: safe change / breaking change (Step 3)
+- [ ] Knowledge: captured / needs capture (Step 4)
+- [ ] Commits: clean / needs cleanup (Step 5)
+
+All items must pass before recommending "ship it."
+
+## Domain-Specific Gates
+
+Agents with domain-specific facades may add extra gates. For example:
+
+- **Design system agents**: token validation, contrast checks, accessibility audit
+- **API agents**: schema validation, backward compatibility checks
+- **Security agents**: dependency audit, secret scanning
+
+These are additive — they don't replace the generic gates above.
+
+## Exit Criteria
+
+Delivery is approved when all gates pass. If any gate fails, report the failure and recommend fixes before shipping. Never approve delivery with blocking issues.
+
+## Agent Tools Reference
+
+| Op | When to Use |
+|----|-------------|
+| `admin_health` | Verify agent/system health |
+| `memory_search` | Check for uncaptured session knowledge |
+| `brain_stats` | Review learning state |
+| `capture_knowledge` | Persist patterns before shipping |
+| `capture_quick` | Fast capture for simple learnings |

package/src/skills/env-setup.md

@@ -0,0 +1,151 @@
+---
+name: env-setup
+description: >
+  Use when a developer needs to set up, fix, or restore a local development environment.
+  Triggers on post-clone setup, project onboarding, first-time running a repo, pulled changes
+  that broke the build, missing or misconfigured dependencies, MODULE_NOT_FOUND or Cannot find
+  module errors, gyp ERR or native module build failures, missing .env files or unknown required
+  environment variables, database setup, Docker compose issues, or connection refused during
+  local dev. Covers Node.js, Python, Rust, Go, Ruby, PHP, and Docker-based projects.
+---
+
+# Environment Setup
+
+Detect what a project needs, diagnose what's missing, and produce an actionable setup checklist.
+
+## Overview
+
+Scan the project root for configuration files, detect the tech stack and dependencies, identify gaps between what's required and what's present, then generate ordered setup steps. Offer to execute each step.
+
+## When to Use
+
+- Just cloned a repo and need to get it running
+- Getting errors after pulling changes (missing deps, env vars, DB migrations)
+- Onboarding to an unfamiliar project
+- Setting up a project on a new machine
+- Docker/container environment not starting
+- Missing `.env` file or environment variables
+
+## Detection Phase
+
+Scan the project root and identify:
+
+### Package Managers & Dependencies
+
+| File | Stack | Install Command |
+|------|-------|-----------------|
+| `package.json` | Node.js | `npm install` / `yarn` / `pnpm install` (check for lockfile) |
+| `requirements.txt` | Python | `pip install -r requirements.txt` |
+| `pyproject.toml` | Python | `pip install -e .` or `poetry install` or `uv sync` |
+| `Pipfile` | Python | `pipenv install` |
+| `Cargo.toml` | Rust | `cargo build` |
+| `go.mod` | Go | `go mod download` |
+| `Gemfile` | Ruby | `bundle install` |
+| `composer.json` | PHP | `composer install` |
+
+**Lockfile priority:** If a lockfile exists (`package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`, `Pipfile.lock`, `poetry.lock`), use the matching package manager. Don't mix.
+
+### Environment Variables
+
+1. Check for `.env.example`, `.env.sample`, `.env.template`
+2. Check for existing `.env` — if missing, copy from template
+3. Parse template for required variables (lines without defaults or with placeholder values)
+4. Flag variables that need real values (API keys, secrets, database URLs)
+5. **If no template exists:** grep source for `process.env.`, `os.environ`, `env::var`, `os.Getenv` to discover env vars the project actually uses.
+
+### Native Dependencies
+
+| Indicator | What It Means |
+|-----------|--------------|
+| `better-sqlite3`, `sqlite3` in deps | Needs C++ compiler |
+| `node-gyp` in deps or scripts | Needs Python 3 + C++ toolchain |
+| `sharp` in deps | Needs `libvips` |
+| `Cargo.toml` with `[build-dependencies]` | Needs Rust toolchain for build scripts |
+| `setup.py` with `ext_modules` | Needs C compiler for Python extensions |
+
+### Databases
+
+| File/Config | Database | Setup Needed |
+|-------------|----------|-------------|
+| `docker-compose.yml` with postgres/mysql | PostgreSQL/MySQL | Container + migrations |
+| `prisma/schema.prisma` | Prisma-managed | `npx prisma migrate dev` |
+| `drizzle.config.*` | Drizzle-managed | `npx drizzle-kit push` |
+| `alembic.ini` | SQLAlchemy | `alembic upgrade head` |
+| `config/database.yml` | Rails | `rails db:create db:migrate` |
+
+### Infrastructure
+
+| File | What It Means |
+|------|--------------|
+| `docker-compose.yml` | Services to start with `docker compose up` |
+| `Dockerfile` | Can build container locally |
+| `Makefile` | Check for `setup`, `install`, `dev` targets |
+| `.tool-versions` / `.node-version` / `.nvmrc` | Required runtime version |
+| `turbo.json` / `nx.json` / `lerna.json` | Monorepo setup |
+
+### IDE & Tool Integration
+
+| File | Integration |
+|------|------------|
+| `.vscode/` | VS Code settings, extensions |
+| `.mcp.json` / `mcp.json` | MCP server config |
+| `.editorconfig` | Cross-editor formatting |
+
+## Diagnosis Phase
+
+After detection, check what's present vs needed:
+
+1. **Runtime version** — does installed version match version files?
+2. **Dependencies installed?** — does `node_modules/`, `venv/`, `vendor/` exist?
+3. **Native build tools?** — are compilers available?
+4. **Env file present?** — does `.env` exist when a template does?
+5. **Database reachable?** — can the configured DB URL connect?
+6. **Docker running?** — is Docker daemon running if needed?
+7. **Build artifacts** — does the project need an initial build step?
+
+## Checklist Generation
+
+Produce steps in dependency order:
+
+```
+## Setup Checklist
+
+1. [ ] Install runtime (Node 20.x via nvm)
+2. [ ] Install dependencies (pnpm install)
+3. [ ] Copy environment file (cp .env.example .env)
+4. [ ] Fill in required env vars: DATABASE_URL, API_KEY
+5. [ ] Start Docker services (docker compose up -d)
+6. [ ] Run database migrations (npx prisma migrate dev)
+7. [ ] Build the project (pnpm build)
+8. [ ] Start dev server (pnpm dev)
+```
+
+**Order matters:** runtime → deps → env → infrastructure → migrations → build → run.
+
+After presenting the checklist, offer: "Want me to run these steps for you?"
+
+## Execution Phase
+
+If the user says yes, execute steps sequentially. Stop and ask if:
+
+- A step fails
+- A step requires manual input (API keys, passwords)
+- A step would modify system-level config (global installs, PATH changes)
+
+## Monorepo Handling
+
+If monorepo detected (turbo.json, nx.json, pnpm-workspace.yaml):
+
+1. Install root dependencies first
+2. Ask which package/app the user wants to work on
+3. Check for package-specific setup
+4. Run package-specific setup after root
+
+## Common Mistakes
+
+- **Wrong package manager** — using `npm install` when `yarn.lock` exists. Always check lockfiles first.
+- **Skipping env file** — project crashes on first API call. Always check for templates.
+- **Missing native build tools** — `npm install` fails with gyp errors. Check before installing.
+- **Missing runtime version** — subtle bugs from wrong Node/Python version.
+- **Docker not running** — cryptic "connection refused" errors.
+- **Stale dependencies** — after `git pull`, always re-install if lockfile changed.

package/src/templates/skills.ts

@@ -12,6 +12,7 @@ const AGENT_SPECIFIC_SKILLS = new Set([
   'brainstorming',
   'code-patrol',
   'context-resume',
+  'deliver-and-ship',
   'executing-plans',
   'fix-and-learn',
   'health-check',

package/src/templates/test-facades.ts

@@ -63,9 +63,10 @@ ${domainDescribes}
       return createSemanticFacades(runtime, '${config.id}');
     }
 
-    it('should create 10 semantic facades', () => {
+    it('should create all expected semantic facades', () => {
       const facades = buildSemanticFacades();
-      expect(facades).toHaveLength(10);
+      // At least the core 10 facades must exist; new ones may be added by @soleri/core
+      expect(facades.length).toBeGreaterThanOrEqual(10);
       const names = facades.map(f => f.name);
       expect(names).toContain('${config.id}_vault');
       expect(names).toContain('${config.id}_plan');
@@ -79,10 +80,11 @@ ${domainDescribes}
       expect(names).toContain('${config.id}_cognee');
     });
 
-    it('total ops across all facades should be 209', () => {
+    it('total ops across all facades should meet minimum threshold', () => {
       const facades = buildSemanticFacades();
       const totalOps = facades.reduce((sum, f) => sum + f.ops.length, 0);
-      expect(totalOps).toBe(209);
+      // At least 209 ops (baseline); new ops may be added by @soleri/core
+      expect(totalOps).toBeGreaterThanOrEqual(209);
     });
   });