faf-cli 8.0.0 → 8.1.0

package/README.md

@@ -65,6 +65,7 @@ No setup, no drift, no re-explaining.
 ```bash
 bunx faf auto                 # Bun — zero install, fastest path
 npx faf auto                  # npm — works everywhere
+pnpm dlx faf auto             # pnpm — zero install
 brew install wolfe-jam/faf/faf-cli && faf auto   # Homebrew (auto-taps)
 ```
 
@@ -132,9 +133,28 @@ faf memory etch "a durable fact" --id my-fact
 faf memory show
 ```
 
-### What's New in v8.0.0 — The Always33 Edition
+### What's New in v8.1.0 — The Always33+ Edition
 
-**One engine, one number: faf-cli v8 scores all 33 slots with the always-33 kernel — the same score faf-kernel, faf-rust-sdk and rust-faf-mcp give.**
+**From nothing to listed in one command: `faf card init` asks seven questions and writes your agent.fafa, your AI Catalog entry and your ARD entry.**
+
+The same always-33 engine, plus cards.
+
+```bash
+npx faf-cli@latest card init     # seven questions → agent.fafa → AI Catalog + ARD
+```
+
+| You have | `faf cards` gives you |
+|---|---|
+| `agent.fafa` | AI Catalog + ARD |
+| + `project.faf` | + A2A, MCP and registry cards |
+| `project.faf` filled out | the full context behind every card |
+
+- **Scripts ask nothing:** every answer is a flag (`--name`, `--domain`, `--url` or `--package`, `--skill`, `--example`, `--set-version`).
+- **Help says what each command touches,** with a "What touches what" footer and [docs.faf.one/side-effects](https://docs.faf.one/side-effects).
+
+### The Always33 Edition (8.0)
+
+**One engine, one number: faf-cli v8 scores with the always-33 kernel — the same score faf-kernel, faf-rust-sdk and rust-faf-mcp give.**
 
 - **The always-33 engine.** Every `.faf` is scored against all 33 Mk4 slots by one Rust kernel (`faf-scoring-kernel` 3.0.0, WASM). Verified identical to the reference always-33 scorer on the `project.faf` of all 80 FAF repos.
 - **Your 21 slots, and the 12 enterprise slots in view.** faf-cli fills the 21 base slots. The 12 enterprise slots — infra, app, ops — are marked `slotignored` unless your app-type uses them, and `faf score` shows all 33.
@@ -152,6 +172,8 @@ faf memory show
 
 **Recent sprint**
 
+- ✪ [8.1.0](https://github.com/Wolfe-Jam/faf-cli/releases/tag/v8.1.0) The Always33+ Edition — from nothing to listed in one command
+- ✪ [8.0.1](https://github.com/Wolfe-Jam/faf-cli/releases/tag/v8.0.1) pnpm installs work — faf-scoring-kernel from npm
 - ✪ [8.0.0](https://github.com/Wolfe-Jam/faf-cli/releases/tag/v8.0.0) The Always33 Edition — one engine, one number
 - 🧱 [7.16.2](https://github.com/Wolfe-Jam/faf-cli/releases/tag/v7.16.2) `faf compile` emits FAFb wire v2 — same bytes as the faf-fafb golden
 - 🧭 [7.16.1](https://github.com/Wolfe-Jam/faf-cli/releases/tag/v7.16.1) `faf` back in step with `faf-cli`
@@ -225,7 +247,7 @@ For a specific agent: [Grok, xAI & Cursor 👀](docs/faf-cli-for-agents.md) · [
 
 Pivotal releases — full history in [CHANGELOG.md](./CHANGELOG.md):
 
-- **v8.0 — Always33** — one engine, one number: every `.faf` scored against all 33 slots.
+- **v8.0 — Always33** — one engine, one number: the same score everywhere.
 - **v7.1 — AGENTS.md** — `faf export --agents` authors a complete, non-destructive `AGENTS.md`.
 - **v7.0 — GIT** — context goes git-native: `faf diff` / `log` / `hooks`.
 - **v6.16 — Know Your Stack** — every emitted file labels your stack identically.