@warpgogol/forge 4.1.6 → 4.2.2

package/README.md

@@ -2,15 +2,19 @@
 
 [Українська](README.uk.md) | English
 
-Portable governance engine for AI-assisted project development. Provides skills, RFC/ADR workflows, naming conventions, spec vendoring, and a CLI — all framework-agnostic and dependency-free (only `yaml` + `zod`).
+**AI can write the code. Forge keeps the project engineered.**
+
+A repository-native control layer for AI-assisted development. Decisions, rules, skills and verification stay with the project — independent of the agent that works on it.
 
 > Engineered at [Warpgogol](https://warpgogol.com) · Released as open source.
 
+[![npm version](https://img.shields.io/npm/v/@warpgogol/forge.svg)](https://www.npmjs.com/package/@warpgogol/forge) [![npm downloads](https://img.shields.io/npm/dm/@warpgogol/forge.svg)](https://www.npmjs.com/package/@warpgogol/forge) [![CI](https://github.com/syrokomskyi/forge/actions/workflows/ci.yml/badge.svg)](https://github.com/syrokomskyi/forge/actions) [![Node](https://img.shields.io/badge/Node-24%2B-green.svg)](https://nodejs.org) [![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](LICENSE)
+
 ---
 
 ## Start right now
 
-Create a new folder, open it in your AI IDE (Windsurf, Cursor, or any IDE that supports AI agents), and paste this:
+Create a new folder, open it in your AI IDE (Windsurf, Cursor, Claude Code, Codex CLI, or any IDE that supports AI agents), and paste this:
 
 ```
 Install https://npmjs.com/package/@warpgogol/forge in this folder and set up my project. I want to build: [describe your project]
@@ -32,323 +36,133 @@ The skill asks a few simple questions in the chat, then sets everything up. Afte
 
 ---
 
-## What you can build with Forge
-
-Forge supports five kinds of projects. You pick one when you start — everything else is automatic.
-
-| Project type | What it is | Example ideas |
-| --- | --- | --- |
-| **Browser game** | An interactive game that runs in a web browser — 2D, arcade, puzzle, adventure | Catch falling stars, tile-matching puzzle, platformer |
-| **Governance / library** | A code library or governance-only project — no website, no game, no video, just structure and documentation | npm package, internal toolkit, documentation hub |
-| **Godot game** | A desktop or mobile game built with Godot 4.x and C# — 2D, 3D, platformer, RPG | Top-down adventure, 3D platformer, puzzle game |
-| **Knowledge system** | An evidence-backed knowledge base — structured datasets where claims are backed by registered source provenance | Game knowledge base, domain ontology, curated reference dataset |
-| **TypeScript library** | A generic TypeScript monorepo with best-practice validators — tsconfig, import boundaries, phantom deps, package exports, strict mode, barrel safety | Internal toolkit, shared library, TypeScript monorepo |
-
-Each project type gets its own scaffold: the right folder structure, the right dependencies, the right tools. You don't need to know what any of those are — Forge sets them up for you.
-
----
-
-## Forge and the Werkstatt engine
-
-Forge is the **governance layer** — skills, RFC/ADR workflows, naming conventions, spec vendoring, and the CLI. It is framework-agnostic and has zero runtime dependencies (only `yaml` + `zod`).
-
-For full project lifecycle management — missions, releases, deployment, certification, quality checks, content codegen — Forge connects to the **Werkstatt engine** and **stack-specific plugins**. These are separate npm packages installed alongside Forge when you need runtime capabilities beyond governance.
-
-| Package | Purpose | Required for |
-| --- | --- | --- |
-| [`@warpgogol/werkstatt`](https://github.com/syrokomskyi/werkstatt) | Runtime engine — missions, releases, Leitstand deployment, certification, Bordbuch, artifact store | All project types with lifecycle management |
-| [`@warpgogol/werkstatt-shared`](https://github.com/syrokomskyi/werkstatt-shared) | Shared infrastructure — checks, integration, ontology, passport | Installed automatically with the engine |
-| [`@warpgogol/werkstatt-phaser-game`](https://github.com/syrokomskyi/werkstatt-phaser-game) | Phaser game plugin — phaser validators, Vite build, deploy adapters | Browser game projects (`phaser-turborepo`) |
-| [`@warpgogol/werkstatt-godot-game`](https://github.com/syrokomskyi/werkstatt-godot-game) | Godot plugin — scene validators, dotnet build, itch.io deploy, Godot skills | Godot game projects (`godot-csharp`) |
-| [`@warpgogol/werkstatt-knowledge`](https://github.com/syrokomskyi/werkstatt-knowledge) | Knowledge plugin — source binding, canonical verification, extraction, materialization, release checks | Knowledge system projects (`knowledge-typescript-turborepo`) |
-| [`@warpgogol/werkstatt-typescript`](https://github.com/syrokomskyi/werkstatt-typescript) | TypeScript plugin — tsconfig, import boundaries, phantom deps, package exports, strict mode, barrel validators | TypeScript TurboRepo projects (`typescript-turborepo`) |
-
-### When you need these packages
-
-- **Governance-only projects** (RFCs, ADRs, skills, documentation hubs) — Forge alone is sufficient.
-- **Games, Godot projects, Knowledge systems** — install `@warpgogol/werkstatt` (the engine) plus the matching stack plugin. The `forge-bootstrap` skill configures bindings automatically; the packages themselves must be installed as devDependencies.
-
-### Installing engine packages
+## Quick start (terminal)
 
 ```sh
-# Browser game project
-pnpm add -D @warpgogol/werkstatt @warpgogol/werkstatt-phaser-game
-
-# Godot game project
-pnpm add -D @warpgogol/werkstatt @warpgogol/werkstatt-godot-game
-
-# Knowledge system project
-pnpm add -D @warpgogol/werkstatt @warpgogol/werkstatt-knowledge
-```
-
-```sh
-# TypeScript TurboRepo project
-pnpm add -D @warpgogol/werkstatt @warpgogol/werkstatt-typescript
+pnpm dlx @warpgogol/forge@latest create --in-place --profile typescript-turborepo
 ```
 
-> **Note for agents:** When scaffolding a new project with `forge create`, always install the engine and matching stack plugin after the scaffold completes. The `forge.yaml` bindings reference commands from these packages (e.g. `pnpm exec werkstatt run rfc.validate`), and they will fail if the packages are not installed.
-
----
-
-## Complete installation guide (from zero)
-
-If you've never programmed before, this section takes you from a completely empty computer to a working Forge setup. Follow the steps for your operating system.
-
-### What you need
-
-You need two free programs:
-
-- **Node.js** (version 24 or newer) — lets your computer run JavaScript tools.
-- **pnpm** — the package manager Forge uses to install dependencies. It's built into Node.js and just needs to be switched on.
-
-Both are free. You install Node.js first, then enable pnpm with a single command.
-
-### Ubuntu
+Then open the project in your AI IDE (Windsurf, Cursor, Claude Code, Codex CLI, or any IDE that supports AI agents) and tell the agent what you want to build.
 
-#### Step 1 — Install Node.js
+One bootstrap command. After that, work through your coding agent.
 
-1. Open the **Terminal** app (press `Ctrl + Alt + T`, or search for "Terminal" in your applications).
+### Stack profiles
 
-2. Download and install Node.js 24 (LTS) by pasting this command and pressing Enter:
+Forge is project-agnostic. Stack profiles provide ready-made starting points.
 
-   ```sh
-   curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash - && sudo apt-get install -y nodejs
-   ```
-
-   You'll be asked for your password — type it (you won't see the characters as you type, that's normal) and press Enter.
-
-3. Verify it worked:
-
-   ```sh
-   node --version
-   ```
-
-   You should see a version number like `v22.x.x`, not an error message.
-
-#### Step 2 — Enable pnpm
-
-Node.js includes a tool called **Corepack** that manages package managers. Enable pnpm with:
-
-```sh
-corepack enable pnpm
-```
-
-Verify:
+| Profile                          | Use case                                              |
+| -------------------------------- | ----------------------------------------------------- |
+| `forge-shell`                    | Governance-only projects, libraries, non-web projects |
+| `typescript-turborepo`           | TypeScript monorepo with best-practice validators     |
+| `phaser-turborepo`               | Browser games, interactive experiences                |
+| `godot-csharp`                   | Desktop/mobile games with Godot 4.x + C#              |
+| `knowledge-typescript-turborepo` | Evidence-backed knowledge bases                       |
 
 ```sh
-pnpm --version
+# List available profiles
+pnpm exec forge profile.validate
 ```
 
-You should see a version number like `10.x.x`.
-
-#### Step 3 — Install an AI-powered IDE
-
-Forge works through conversation with an AI agent. You need an IDE that supports AI agents. We recommend **Windsurf** (tested with Forge):
-
-1. Go to [windsurf.com](https://windsurf.com) and download the Linux version.
-2. Open the downloaded file and follow the installer.
-3. Launch Windsurf.
-
-You can also use **Cursor** ([cursor.com](https://cursor.com)) or any IDE that supports AI agent skills.
-
-### Windows
-
-#### Step 1 — Install Node.js
-
-1. Go to [nodejs.org](https://nodejs.org) in your web browser.
-2. Download the **LTS version** (it will say "LTS" and "Recommended for Most Users"). It should be version 22.x or newer.
-3. Run the downloaded installer (`.msi` file). Accept all default options by clicking **Next** through each screen, then **Install**. If Windows asks for permission, click **Yes**.
-
-4. Verify it worked. Open **PowerShell** (search for "PowerShell" in the Start menu) and type:
-
-   ```sh
-   node --version
-   ```
-
-   You should see a version number like `v22.x.x`, not an error message.
-
-#### Step 2 — Enable pnpm
+---
 
-Node.js includes a tool called **Corepack** that manages package managers. Enable pnpm with:
+## Architecture
 
-```sh
-corepack enable pnpm
 ```
-
-Verify:
-
-```sh
-pnpm --version
+IDE / AGENT / MODEL
+       ↓
+┌──────────────────────────────────┐
+│             FORGE                 │
+│                                   │
+│ Project contract      forge.yaml  │
+│ Decisions             RFC / ADR   │
+│ Agent workflows       Skills      │
+│ Verification          Validators  │
+│ Evolution             Upgrade     │
+└──────────────────────────────────┘
+       ↓
+YOUR REPOSITORY
 ```
 
-You should see a version number like `10.x.x`.
-
-#### Step 3 — Install an AI-powered IDE
-
-Forge works through conversation with an AI agent. You need an IDE that supports AI agents. We recommend **Windsurf** (tested with Forge):
-
-1. Go to [windsurf.com](https://windsurf.com) and download the Windows version.
-2. Run the downloaded installer and follow the setup wizard.
-3. Launch Windsurf.
-
-You can also use **Cursor** ([cursor.com](https://cursor.com)) or any IDE that supports AI agent skills.
-
-### Optional — Install Godot and .NET (only for Godot game projects)
-
-If you're planning to create **Godot game** projects (the `godot-csharp` profile), you need two additional tools:
-
-- **Godot 4.x** (with .NET support) — the game engine. Download it from [godotengine.org/download](https://godotengine.org/download). Make sure to choose the ".NET" version (not the standard version).
-- **.NET SDK 8+** — the C# runtime and build tools. Download it from [dotnet.microsoft.com/download](https://dotnet.microsoft.com/download).
-
-Verify both are installed:
-
-```sh
-godot --version
-dotnet --version
-```
-
-### Troubleshooting
-
-- **"command not found" after installing Node.js** — Close and reopen your terminal (Ubuntu) or PowerShell (Windows). The system needs to reload the list of available commands.
-- **"corepack: command not found"** — Your Node.js version is too old. Install Node.js 24+ using the steps above.
-- **AI agent doesn't know about Forge** — You opened an empty folder, but the AI agent has no Forge context. Run `pnpm dlx @warpgogol/forge@latest create --in-place --profile phaser-turborepo` (or the appropriate profile) in a terminal first, then open the folder in your IDE. The `forge create` command populates the current folder with skills, configuration, and `AGENTS.md` — without it, the AI agent can't discover Forge.
+Agents can change. Models can change. IDEs can change. Engineering rules stay with the project.
 
 ---
 
-## Quick start
-
-### For creative operators — one command, then just talk
-
-You need to run one command in the terminal to create your project. After that, everything works through conversation with an AI agent — no more commands.
-
-#### Start a new project from scratch
-
-1. **Create a project folder and scaffold Forge in-place.** Open a terminal (PowerShell on Windows, Terminal on Ubuntu) and run:
-
-   ```sh
-   mkdir my-game
-   cd my-game
-   pnpm dlx @warpgogol/forge@latest create --in-place --profile phaser-turborepo
-   ```
-
-   The project name is derived from the folder name (`my-game` in this example). You can override it with `--name`. This populates the current folder with everything Forge needs — skills, configuration, and project structure. For other project types, use a different `--profile`:
-
-   | What you want to build              | Profile flag                               |
-   | ----------------------------------- | ------------------------------------------ |
-   | Browser game (2D, arcade, puzzle)   | `--profile phaser-turborepo`               |
-   | Godot game (desktop, mobile, 2D/3D) | `--profile godot-csharp`                   |
-   | Knowledge system (evidence-backed)  | `--profile knowledge-typescript-turborepo` |
-   | TypeScript library (monorepo)       | `--profile typescript-turborepo`           |
-   | Library or governance-only project  | `--profile forge-shell`                    |
-
-2. **Open the project folder in your AI IDE.** Open the folder from step 1 in Windsurf or your preferred IDE.
-
-3. **Tell the AI agent what you want to build.** Just type it in the chat, in your own words. For example:
-
-   > I want to build a Godot game where you catch falling stars.
-
-   Or:
-
-   > I want to make a browser game where you catch falling stars.
-
-   Or:
-
-   > I want to create a TypeScript library for calculating astrology charts.
-
-   That's it. The AI agent will do everything else:
-   - Set up the project structure based on what you described (game, library, etc.)
-   - Configure language preferences and project settings
-   - Start a live preview so you can see your work (for games)
-   - Tell you the URL to open in your browser
+## What Forge controls
 
-4. **Watch the preview.** For games, the AI agent will give you a localhost link. Click it — your project is already running. As you describe changes, the agent updates the project and the preview refreshes automatically.
+| Plane              | What it governs                                    |
+| ------------------ | -------------------------------------------------- |
+| **Intent**         | RFCs, architectural DNA, acceptance criteria       |
+| **Decisions**      | ADRs, decision logs, traceability                  |
+| **Agent behavior** | Repository-local skills and workflows              |
+| **Verification**   | Doctor, validators, contracts, deterministic gates |
+| **Evolution**      | Profiles, vendored specs, additive upgrades        |
 
-   For governance and library projects, there's no visual preview — the agent will set up the project structure and tell you when it's ready.
-
-5. **Create together.** From here on, you just talk. Want a different color? Want to add a scene? Want to add a new function to your library? Just say it. The agent handles all the technical work.
-
-#### Bring an existing project into Forge
-
-If you already have a project somewhere else and want to move it into Forge:
+---
 
-1. **Create a Forge project.** Open a terminal, create a folder, and run:
+## Without Forge / With Forge
 
-   ```sh
-   mkdir my-project
-   cd my-project
-   pnpm dlx @warpgogol/forge@latest create --in-place --profile forge-shell
-   ```
+| AI development without Forge          | With Forge                                       |
+| ------------------------------------- | ------------------------------------------------ |
+| Rules live in prompts                 | Rules live in the repository                     |
+| Architecture is implicit              | Decisions become RFCs and ADRs                   |
+| Agent behavior depends on the session | Project-local skills define repeatable workflows |
+| "Done" means the agent says so        | Validators provide deterministic checks          |
+| New agent starts from zero            | Project contract travels with the code           |
+| Upgrades risk overwriting decisions   | Upgrade is additive and idempotent               |
+| Tool-specific conventions             | Agent- and IDE-independent project layer         |
 
-   Then open the folder in your AI IDE.
+---
 
-2. **Tell the AI agent:**
+## Forge IS / Forge IS NOT
 
-   > I want to bring my existing project into Forge. It's located at /path/to/my/project.
+**Forge IS**
 
-   The agent will:
-   - Detect what kind of project it is (game, library, etc.)
-   - Move all your files into the new Forge project — including hidden files like `.env`
-   - Optionally bring your git history
-   - Verify everything builds correctly
-   - Start a live preview (for visual project types)
+- A repository-native governance layer
+- Agent-independent project infrastructure
+- A deterministic complement to probabilistic AI agents
+- A portable project contract
 
-#### What if something goes wrong?
+**Forge IS NOT**
 
-Just tell the AI agent. It can check the project's health, fix issues, and explain what happened — all in plain language. You never need to open a terminal or run commands yourself.
+- Another AI model
+- Another coding agent
+- An IDE
+- A hosted platform
+- A replacement for Git
+- A magic "vibe coding" wrapper
 
 ---
 
-### For developers — CLI commands
-
-#### Create a new project (in-place)
-
-```sh
-# Create a project folder, then scaffold Forge in-place
-# pnpm dlx downloads Forge temporarily — no global install needed
-mkdir my-project
-cd my-project
-pnpm dlx @warpgogol/forge@latest create --in-place --profile forge-shell
+## What you get
 
-# With a specific stack profile
-mkdir my-game && cd my-game
-pnpm dlx @warpgogol/forge@latest create --in-place --profile phaser-turborepo
+- **37 skills** — idea-to-RFC pipeline, grilling, preferences, skill authoring
+- **RFC workflow** — create, validate, list, graph, archive, acceptance probes
+- **ADR workflow** — lightweight architectural decision records
+- **Spec vendoring** — vendor external specs as immutable snapshots
+- **Naming conventions** — kebab-case linting
+- **Workflow linting** — validate `.agents/workflows/` frontmatter
+- **Stack scaffolding** — pnpm + Turborepo monorepo from a profile
+- **Bindings contract** — de-hardcode project-specific commands via `forge.yaml`
+- **Doctor** — project health check
+- **Upgrade** — additive, idempotent skill and config sync
 
-mkdir my-godot-game && cd my-godot-game
-pnpm dlx @warpgogol/forge@latest create --in-place --profile godot-csharp
+---
 
-mkdir my-knowledge-base && cd my-knowledge-base
-pnpm dlx @warpgogol/forge@latest create --in-place --profile knowledge-typescript-turborepo
+## Working with your AI agent
 
-mkdir my-ts-project && cd my-ts-project
-pnpm dlx @warpgogol/forge@latest create --in-place --profile typescript-turborepo
+Forge works with any AI agent — Windsurf, Cursor, Claude Code, Codex CLI, or any IDE that supports agent skills. The setup is the same; only the conversation matters.
 
-# Override the project name (derived from folder name by default)
-pnpm dlx @warpgogol/forge@latest create --in-place --profile forge-shell --name my-custom-name
-```
+**Start with questions, not commands.** Before asking the agent to write code, ask it about the codebase. The agent can read files, search git history, and run Forge CLI commands — let it explore first.
 
-After scaffolding, Forge is installed as a local devDependency. Use `pnpm exec forge` for all subsequent commands within the project:
+**Describe results, not steps.** Tell the agent what you want, not how to do it. For complex work, ask the agent to plan first and wait for your approval.
 
-#### Bring an existing project into Forge
+**Let the agent verify its own work.** Give criteria for "done" and let the agent check itself: "Run the tests after you're done." "Validate the RFC before committing." "Check project health with `forge doctor`."
 
-There is no CLI command for transplant — it is an interactive, AI-guided process:
+**AGENTS.md is your project's persistent memory.** Forge generates `AGENTS.md` files that the agent reads at the start of every session. Put build commands, code style, architecture decisions, and "do X, not Y" rules there.
 
-```sh
-# 1. Create a new empty Forge project (in-place)
-mkdir my-project && cd my-project
-pnpm dlx @warpgogol/forge@latest create --in-place --profile forge-shell
-
-# 2. Open the project in Windsurf (tested with forge) or your preferred IDE
-
-# 3. Run the /forge-bootstrap skill and choose "transplant" mode
-#    The skill will:
-#    - Ask for the path to your existing codebase
-#    - Detect the stack automatically (Phaser, Godot, etc.)
-#    - Migrate all files (including .env and git-ignored files)
-#    - Optionally transfer git history
-#    - Verify the build
-```
+---
 
-#### Diagnose and validate
+## CLI
 
 ```sh
 # Check project health
@@ -359,250 +173,21 @@ pnpm exec forge rfc.validate
 
 # List available skills
 pnpm exec forge skill.list
-```
-
----
-
-## Working with your AI agent
-
-Forge works with any AI agent — Windsurf, Cursor, Claude Code, Codex CLI, or any IDE that supports agent skills. The setup is the same; only the conversation matters. Here are the patterns that make the biggest difference.
-
-### Start with questions, not commands
-
-The single most effective habit: before asking the agent to write code, ask it about the codebase. The agent can read files, search git history, and run Forge CLI commands — let it explore first.
-
-Good questions to start a session:
-
-- "How is this project structured?"
-- "What skills are available and what do they do?"
-- "Walk me through the RFC workflow in this project."
-- "What did we change this week?" (the agent reads git log)
-- "Why does this function have 15 parameters? Check git history."
-
-This works for onboarding too — new team members can get up to speed by asking the agent questions instead of reading code manually. The agent reads everything locally; nothing is uploaded or trained on.
 
-### AGENTS.md — your project's persistent memory
-
-Forge generates `AGENTS.md` files at the project root and in each workspace directory. The agent reads them automatically at the start of every session — think of them as instructions that survive between conversations.
-
-**What to put in AGENTS.md:**
-
-- Build and test commands (`pnpm test`, `pnpm run build:check`)
-- Code style conventions ("use 2 spaces, not tabs")
-- Architecture decisions ("the game package owns all scene logic")
-- "Do X, not Y" rules ("use `resolveImage()` for all image props, never raw `src`")
-- Common mistakes to avoid
-
-**When the agent makes a mistake**, tell it to update AGENTS.md so it doesn't repeat the error. Over time, AGENTS.md accumulates the team's hard-won knowledge.
-
-Forge generates AGENTS.md from `forge.yaml` via `forge.agents.generate`. Hand-written AGENTS.md files (without the generated marker) are preserved. Generated ones are regenerated when you run `forge upgrade` or `forge.agents.generate` — so put your custom rules in `forge.yaml` or in a hand-written AGENTS.md, not in a generated one.
-
-### Describe results, not steps
-
-The agent is an autonomous worker, not a typewriter. Tell it what you want, not how to do it.
-
-**Bad** (over-specified):
-
-> Open src/game/player.ts, add a function called calculateScore that takes a number array, sum it, return the result. Then open src/game/player.test.ts and add a test.
-
-**Good** (result-oriented):
-
-> Add a scoring system that calculates total points from collected items.
-
-For complex work, ask the agent to plan first:
-
-> I want to add a multiplayer mode. Make a plan first, show it to me, and wait for my approval before implementing.
-
-Forge's `/fo-idea` skill formalizes this: idea → audit → plan → implement → review. You can invoke it explicitly, or the agent will follow the pattern when the task is complex enough.
-
-### Let the agent explore
-
-Don't over-explain. The agent knows how to read files, search code, check git history, and run commands. Instead of pointing it to specific files, describe what you want to understand or change:
-
-**Instead of:** "Look in the src/game folder for player.ts and check if it has a move function."
-
-**Say:** "How does player movement work?"
-
-The agent will find the relevant files, trace the call chain, and explain it back to you. If it needs more context, it will ask.
-
-### Parallel work
-
-You can run multiple agent sessions simultaneously — in separate IDE windows, terminal tabs, or git worktrees. Each session works independently.
-
-This is useful for:
-
-- Writing an RFC in one session while implementing a different feature in another
-- Exploring two design approaches in parallel before committing to one
-- Running a long validation in one session while continuing work in another
-
-If you use the Werkstatt engine, its mission system keeps work isolated — each mission has its own workpiece directory, so parallel sessions don't conflict.
-
-### Let the agent verify its own work
-
-Give the agent criteria for "done" and let it check itself:
-
-- "Run the tests after you're done."
-- "Validate the RFC before committing."
-- "Check project health with `forge doctor`."
-
-Forge provides the tools — `forge doctor`, `forge rfc.validate`, `forge skill.list`, test runners. Tell the agent to use them. The agent can run commands, read the output, and fix issues without your intervention.
-
----
-
-## Skill packs
-
-Skill packs let you create project-local skills under your own prefix, separate from Forge's portable `fo-` skills. This is useful when your project has domain-specific workflows that don't belong in Forge's portable skill set.
-
-### Declaring a pack
-
-Add a `skillPacks` entry to `forge.yaml`:
-
-```yaml
-skillPacks:
-  - prefix: wg
-    dir: packages/my-skills/skills
-```
-
-- `prefix` — short identifier used as a skill name prefix (e.g. `wg-deploy`, `wg-content-check`). Cannot be `fo` (reserved for Forge).
-- `dir` — directory containing your pack skills. Each skill is a subdirectory with a `SKILL.md` file.
-
-### Pack manifest (`forge.plugin.yaml`)
-
-Each pack directory must contain a `forge.plugin.yaml` manifest:
-
-```yaml
-id: my-pack
-version: 1.0.0
-```
-
-- `id` — kebab-case identifier for the pack.
-- `version` — semver version string.
-
-`forge init` auto-creates this manifest if it's missing. You can also create it manually.
-
-### Skill structure
-
-Skills follow the same structure as Forge skills:
-
-```
-packages/my-skills/skills/
-  forge.plugin.yaml          # pack manifest
-  wg-deploy/
-    SKILL.md                 # skill definition with frontmatter
-  wg-content-check/
-    SKILL.md
-```
-
-Each `SKILL.md` has standardized frontmatter (name, description, category, concerns, dependsOn) — the same format as Forge's `fo-` skills.
-
-### Validation commands
-
-```sh
-# Validate all pack manifests
-pnpm exec forge plugin.validate
-
-# List discovered packs
-pnpm exec forge plugin.discover
-
-# Validate individual skills (including pack skills)
-pnpm exec forge skill.validate
-
-# List all skills (pack skills annotated with pack:<prefix>)
-pnpm exec forge skill.list
-```
-
-### Extension points (Compass contract blocks)
-
-Packs can declare custom Compass contract blocks — source-file markers that `compass.validate` enforces. This lets your pack define its own `<MY_CONTRACT>` blocks with required tags:
-
-```yaml
-id: my-pack
-version: 1.0.0
-extensionPoints:
-  compass:
-    contract:
-      blocks:
-        - blockId: api-contract
-          requiredFor:
-            - "packages/my-pack/**/*.ts"
-          requiredTags:
-            - name: purpose
-              minWords: 3
-```
-
-`compass.validate` will emit `COMPASS-PLUGIN-01` (missing block), `COMPASS-PLUGIN-02` (missing required tag), and `COMPASS-PLUGIN-03` (tag below minWords) for files matching `requiredFor` that don't carry the block.
-
-### Rules
-
-- Pack skill names must start with the pack prefix (e.g. `wg-deploy` for prefix `wg`).
-- Pack skills cannot use the `fo-` prefix (reserved for Forge).
-- Pack skills cannot reference platform RFC/ADR ids or platform names.
-- Pack skills may depend on Forge skills, but Forge skills may not depend on pack skills (preserves portability).
-- If a pack skill name conflicts with a Forge skill name, the pack skill is skipped during sync.
-
----
-
-## Stack profiles
-
-A stack profile defines the project scaffold: directory structure, dependencies, CI config, and first workspace. Choose a profile with `--profile` when creating a new project.
-
-| Profile | Project type | Description | First workspace | Use case |
-| --- | --- | --- | --- | --- |
-| `forge-shell` | Governance / library | Minimal Forge shell (default) | — | Governance-only projects, libraries, non-web projects |
-| `phaser-turborepo` | Browser game | Phaser + TypeScript + pnpm + Turborepo | `games/my-game` | Browser games, interactive experiences |
-| `godot-csharp` | Godot game | Godot 4.x + C# + pnpm + Turborepo | `games/my-game` | Desktop/mobile games, Godot-based interactive projects |
-| `knowledge-typescript-turborepo` | Knowledge system | TypeScript + pnpm + Turborepo | `knowledge/my-kb` | Evidence-backed knowledge bases, structured datasets with source provenance |
-| `typescript-turborepo` | TypeScript library | TypeScript + pnpm + Turborepo | — | Generic TypeScript TurboRepo monorepo with best-practice validators |
-
-```sh
-# List available profiles (after install)
-pnpm exec forge profile.validate
-```
-
-When you bring an existing project through the `/forge-bootstrap` transplant mode, Forge detects the matching profile automatically by checking for marker files (`phaser.config.*`, `project.godot`, etc.).
-
-## Upgrade flow
-
-When a new version of `@warpgogol/forge` is published, consumers upgrade additively:
-
-```sh
-# 1. Update Forge to the latest version (local devDependency)
-pnpm update @warpgogol/forge
-
-# 2. Sync skills and binding defaults from the installed version
+# Sync skills and config from installed version
 pnpm exec forge upgrade
 
-# 3. Check project health
-pnpm exec forge doctor
+# Validate public surface consistency
+pnpm exec forge public-surface.validate
 ```
 
-`forge upgrade` is additive — it never overwrites operator-set bindings, never deletes files, and is idempotent. It updates `forge.syncedVersion` in `forge.yaml` to track the last synced version. Use `--dry-run` to preview changes.
-
-## What forge gives you
-
-- **37 skills** (fo-pipeline, grilling, preferences, skill authoring) — deployed to `.agents/skills/` by `forge create`
-- **RFC workflow** — create, validate, list, graph, archive, acceptance probes, decision logs, DNA trace
-- **ADR workflow** — lightweight architectural decision records
-- **Spec vendoring** — vendor external spec packages as immutable snapshots with integrity manifests
-- **Naming conventions** — kebab-case linting
-- **Workflow linting** — validate `.agents/workflows/` frontmatter and references
-- **Stack scaffolding** — scaffold a new pnpm + Turborepo monorepo from a profile
-- **Bindings contract** — de-hardcode project-specific commands/paths from skills via `forge.yaml`
-
-## Lifecycle
-
-The typical forge project lifecycle:
+Full CLI reference: [docs/reference/cli.md](docs/reference/cli.md)
 
-1. **Create** — `pnpm dlx @warpgogol/forge@latest create --in-place --profile <profile>` scaffolds a new project in the current directory with forge.yaml, skills, and docs directories
-2. **IDE** — open the project in Windsurf (tested with forge) or your preferred IDE
-3. **Bootstrap** — run `/forge-bootstrap` to configure the project interactively. The skill supports two modes:
-   - **Greenfield** — start a new project from scratch: pick a stack, fill in bindings, init git
-   - **Transplant** — bring an existing codebase into Forge: detect the stack, migrate code (including git-ignored files like `.env`), optionally transfer git history, verify the build
-4. **Upgrade** — when a new `@warpgogol/forge` version is published, run `pnpm exec forge upgrade` to sync skills and binding defaults additively
+---
 
 ## forge.yaml
 
-The single source of truth for project configuration. Created by `forge create`:
+The single source of truth for project configuration:
 
 ```yaml
 schema: forge/config@1
@@ -626,6 +211,10 @@ bindings:
     invariants: DNA
 ```
 
+Full reference: [docs/reference/forge-yaml.md](docs/reference/forge-yaml.md)
+
+---
+
 ## Programmatic API
 
 ```ts
@@ -637,52 +226,59 @@ import {
   FORGE_SKILLS,
 } from "@warpgogol/forge";
 
-// Load config
 const config = loadForgeConfig(process.cwd());
-
-// Resolve a binding
 const cmd = resolveBinding(config, "commands.validateRfc", { id: "RFC-0001" });
 
-// Register modules in your own registry
 const registry = /* your ForgeModuleRegistry */;
 await forgeCoreModule.register(registry);
 await forgeRfcModule.register(registry);
 ```
 
+Full API reference: [docs/reference/programmatic-api.md](docs/reference/programmatic-api.md)
+
+---
+
 ## Architecture
 
 | Directory | Purpose |
 | --- | --- |
 | `src/` | Portable core — types, config, skills registry, validators, onboarding. Zero `@warpgogol/*` imports. |
-| `os/` | ForgeModule registrations. `compass` and `werkstatt` are fully autonomous (RFC-0556) — all handlers inlined, no `@warpgogol/*` imports. |
+| `os/` | ForgeModule registrations. `compass` and `werkstatt` are fully autonomous — all handlers inlined. |
 | `bin/` | CLI entrypoint (`forge` command). |
 | `skills/` | 37 skill definitions (29 fo + 5 shared + 3 meta) with SKILL.md frontmatter. |
 | `profiles/` | Stack profiles for `scaffold`. |
 
-## Publishing to npm
-
-This package is published to the npm registry as `@warpgogol/forge`. Publishing is automated via GitHub Actions CI.
-
-### How it works
+---
 
-1. The source lives in the [warpgogol/werkstatt](https://github.com/syrokomskyi/werkstatt) monorepo under `packages/forge/`.
-2. [`@warpgogol/repo-extract`](https://github.com/syrokomskyi/repo-extract) extracts the package into the standalone [syrokomskyi/forge](https://github.com/syrokomskyi/forge) repository, flattening it to repo root and stripping workspace dependencies.
-3. The generated GitHub Actions CI workflow (`.github/workflows/ci.yml`) runs on every push to `main`: lint → typecheck → build → test → `npm publish --provenance --access public`.
-4. The `NPM_TOKEN` secret must be set in the [repository settings](https://github.com/syrokomskyi/forge/settings/secrets/actions).
+## Upgrade flow
 
-### Triggering a new release
+```sh
+pnpm update @warpgogol/forge
+pnpm exec forge upgrade
+pnpm exec forge doctor
+```
 
-From the werkstatt monorepo root:
+`forge upgrade` is additive — it never overwrites operator-set bindings, never deletes files, and is idempotent. Use `--dry-run` to preview changes.
 
-```sh
-# 1. Bump the version in packages/forge/package.json
-# 2. Run the extraction (extracts + commits + pushes to github.com:syrokomskyi/forge.git)
-pnpm exec repo-extract --config packages/forge/extract.config.yaml --verbose
+---
 
-# 3. CI picks up the push and publishes to npm automatically
-```
+## Documentation
+
+- [Getting started](docs/getting-started.md)
+- [Why Forge?](docs/concepts/why-forge.md)
+- [Project contract](docs/concepts/project-contract.md)
+- [Governance model](docs/concepts/governance-model.md)
+- [Bring an existing project](docs/guides/existing-project.md)
+- [Upgrading](docs/guides/upgrading.md)
+- [Skills](docs/guides/skills.md)
+- [RFC and ADR workflows](docs/guides/rfc-adr.md)
+- [CLI reference](docs/reference/cli.md)
+- [forge.yaml reference](docs/reference/forge-yaml.md)
+- [Profiles](docs/reference/profiles.md)
+- [Programmatic API](docs/reference/programmatic-api.md)
+- [Publishing](docs/maintainers/publishing.md)
 
-After CI completes, verify the new version on [npmjs.com/package/@warpgogol/forge](https://www.npmjs.com/package/@warpgogol/forge).
+---
 
 ## License