argsbarg 7.0.10 → 7.1.0

package/CHANGELOG.md

@@ -7,6 +7,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [7.1.0] - 2026-09-18
+
+### Changed
+
+- Updated copy-template READMEs (`full-example`, `full-example-json`) to be user-facing (Homebrew install via tap and simplified formula install, CLI commands, usage examples, agent/MCP integration, and documentation links) rather than template contributor guides.
+- Copy-template justfiles use hardcoded CLI/tap literals (substituted by `argsbarg create`); removed `scripts/print-identity.ts` and runtime `bun` indirection. `{tapOrg}` / `{tapRepo}` remain only for Homebrew tap paths. Comment documents `set shell`.
+- Inverted `AGENTS.md` hierarchy in copy templates and consumer sync: argsbarg managed framework baseline sits at the top (under the app title) with an explicit precedence note, and all app-specific sections (`## Tooling`, `## Documentation`, `## App conventions`, custom sections) live below `<!-- /argsbarg:managed -->` so project-specific rules override framework defaults. `merge-agents-md` automatically migrates legacy sandwich layouts to the new structure.
+
+### Added
+
+- **`mcp-plugin` copy template** (`examples/mcp-plugin/`) — Agent MCP plugin template for Cursor and Claude Code marketplaces, featuring in-repo manifests (`.cursor-plugin/plugin.json`, `mcp.json`, `.claude-plugin/plugin.json`, `.mcp.json`), a standalone bundled Node script (`scripts/mcp.mjs`), and an in-memory datastore with `@sg` schemagen.
+- Cross-runtime MCP stdio loop using `process.stdin` in `mcpServeStdioLoop` to support standalone bundled execution under Node.js as well as Bun.
+- bunfig.toml to examples so bun will auto-install deps on run
+- **`mcpServer.cursorPlugin`** — opt-in Cursor plugin zip packaging (`dist/cursor-plugin/<name>.zip`) via `mcp bundle`, generating `.cursor-plugin/plugin.json`, `mcp.json` with `${CURSOR_PLUGIN_ROOT}`, and preservation of repository skills.
+- **Plugin skill preservation** — `mcp bundle` (`claudePlugin` and `cursorPlugin`) copies repository skills (`skills/<key>/`) when present in the project, falling back to generated MCP routing stubs when absent.
+- **Extended bundle metadata** — `CliMcpBundleConfig` supports `displayName`, `homepage`, `repository`, `license`, and `skillsDir` overrides for plugin manifests.
+
+## [7.0.11] - 2026-09-16
+
+### Fixed
+
+- **Help table box sizing and wrapping** — fixed an off-by-two sizing bug in TTY help rendering where table rows wrapped their description column based on `hw - 2` instead of the inner content width `hw - 4`. This caused long table lines to exceed the terminal width and the box borders by up to 2 columns, resulting in the trailing border character `│` wrapping onto a new line in terminals matching `stdout.columns`.
+
 ## [7.0.10] - 2026-09-16
 
 ### Added
@@ -1010,7 +1033,9 @@ const cli = { ... } satisfies CliProgram;  // or : CliProgram
 - Migrate schemas: rename every `children` property to **`commands`**; move positional definitions to **`CliPositional`** objects on `positionals` and strip `positional` / `argMin` / `argMax` from flag definitions under `options` (flags only carry `name`, `description`, `kind`, and optional `shortName`).
 - Imports: use `CliPositional` where needed; replace `CliOptionDef` with `CliOption` or `CliPositional` as appropriate.
 
-[Unreleased]: https://github.com/bdombro/bun-argsbarg/compare/v7.0.10...HEAD
+[Unreleased]: https://github.com/bdombro/bun-argsbarg/compare/v7.1.0...HEAD
+[7.1.0]: https://github.com/bdombro/bun-argsbarg/releases/tag/v7.1.0
+[7.0.11]: https://github.com/bdombro/bun-argsbarg/releases/tag/v7.0.11
 [7.0.10]: https://github.com/bdombro/bun-argsbarg/releases/tag/v7.0.10
 [7.0.9]: https://github.com/bdombro/bun-argsbarg/releases/tag/v7.0.9
 [7.0.7]: https://github.com/bdombro/bun-argsbarg/releases/tag/v7.0.7

package/README.md

@@ -1,4 +1,5 @@
-Logo
+![Logo](logo.png)
+<!-- Big money NE - https://patorjk.com/software/taag/#p=testall&f=Bulbhead&t=shebangsy&x=none&v=4&h=4&w=80&we=false> -->
 
 [GitHub](https://github.com/bdombro/bun-argsbarg)
 [License: MIT](LICENSE)
@@ -381,7 +382,7 @@ ArgsBarg ships authoring docs under `node_modules/argsbarg/docs/`. Because AI ag
 bun scripts/merge-agents-md.ts .
 ```
 
-This refreshes the argsbarg-managed section in `AGENTS.md` while preserving your app-specific prefix and `**<app> conventions:**` footer. See **Agent instructions** in [docs/cli-program.md](docs/cli-program.md).
+This refreshes the argsbarg-managed section at the top of `AGENTS.md` while preserving all app-specific sections below it. See **Agent instructions** in [docs/cli-program.md](docs/cli-program.md).
 
 ### 3. Agent Skills & Workspace Configuration
 

package/docs/ai-skills.md

@@ -15,9 +15,9 @@ Because developers customize `skills/<app>/SKILL.md` with domain workflows, exec
 - **Commands catalog** — compact intent-based router directing agents to the right subcommands
 - **Workflow & Pitfalls** — guidelines for automated execution (e.g. using non-interactive flags like `--yes`)
 
-## Claude Code plugin
+## Claude Code and Cursor plugins
 
-When `mcpServer.claudePlugin: true` is configured, running `myapp mcp bundle` packages `dist/claude-plugin/<name>.zip` containing an MCP pointer skill (`SKILL.md` only) that routes Claude Code to the bundled MCP server. This is a dist packaging artifact, not installed via `configure`.
+When `mcpServer.claudePlugin: true` and/or `mcpServer.cursorPlugin: true` is configured, running `myapp mcp bundle` packages plugin archives (`dist/claude-plugin/<name>.zip` and `dist/cursor-plugin/<name>.zip`). If a repository skill directory exists (`skills/<key>/`), the package bundles that custom skill; otherwise it falls back to a generated MCP pointer skill that routes agents to the bundled MCP server. These are dist packaging artifacts, not installed via `configure`.
 
 ## Uninstalling legacy skills
 

package/docs/cli-program.md

@@ -584,18 +584,16 @@ bun scripts/merge-agents-md.ts .
 
 `bunx argsbarg create` copies `AGENTS.md` and `CLAUDE.md` (`@AGENTS.md`) into new projects automatically.
 
-2. **Add an app-specific block at the bottom** (recommended). Replace the template placeholder with a heading like `**myapp conventions:**` and short bullets — shared flag modules, `read*Flags` / `resolve*` paths, Ink vs JSON-only, etc. Example:
+2. **Add app-specific sections below the managed block** (recommended). The framework baseline lives between `<!-- argsbarg:managed -->` and `<!-- /argsbarg:managed -->` at the top of the file. All application-specific sections (`## Tooling`, `## Documentation`, `## App conventions`, custom rules) live below the closing marker where they take precedence over framework defaults. Example:
 
 ```markdown
-**sqsp-qa conventions:**
+## App conventions
 
 - Shared mutator flags: `readQaMutatingFlags(ctx)` in `src/cli/shared.ts`.
 - Per command: `read*Flags` + `resolve*Input` in `commands/<name>/resolve.ts`.
 ```
 
-If you maintain argsbarg from a sibling checkout, `just consumers-dev` / `just consumers-sync` refresh the shared managed section and **keep** your prefix and conventions footer. Commit `AGENTS.md` in your repo.
-
-3. **Optional:** add consumer-specific sections above the `<!-- argsbarg:managed -->` marker in `AGENTS.md` (project context, Ink patterns, domain notes).
+If you maintain argsbarg from a sibling checkout, `just consumers-dev` / `just consumers-sync` refresh the shared managed section and **keep** all app-specific sections below it. Commit `AGENTS.md` in your repo.
 
 - **Not this file:** `skills/<app>/SKILL.md` in your repository is the **app** skill — how to *invoke* the CLI. `AGENTS.md` is for *authoring* argsbarg schema.
 

package/docs/developing.md

@@ -36,15 +36,15 @@ Sibling consumer repos (machine-specific paths in the root `justfile` `consumer_
 
 | Recipe | When | Effect |
 | --- | --- | --- |
-| `just consumers-dev` | Before publish; hacking on argsbarg locally | `bun add argsbarg@file:<relative>`; fix `.bin/argsbarg` symlink; refresh `AGENTS.md` from template (keeps app-specific prefix and conventions footer) |
+| `just consumers-dev` | Before publish; hacking on argsbarg locally | `bun add argsbarg@file:<relative>`; fix `.bin/argsbarg` symlink; refresh `AGENTS.md` from template (preserves app-specific sections below managed block) |
 | `just consumers-sync` | After release | Sets `"argsbarg": "^<this package.json version>"`, `bun install`, merge `AGENTS.md`, `just build`, `just docgen`, `just install-local` (Homebrew dev formula + agent artifacts; `just install` is an alias) |
 | `just consumers-schemagen` | After `@sg` type changes in consumers | Runs `argsbarg schemagen` in each `consumer_apps` path (fails if missing) |
 
 `consumers-sync` reads the version from **this repo’s** `package.json` — not npm. Run it **after** `just release` so consumers pin a version that exists on the registry.
 
-**Argsbarg authoring rules** — `scripts/merge-agents-md.ts` copies the template from `examples/full-example-json/AGENTS.md` into each consumer, preserving any existing prefix and `**… conventions:**` footer block.
+**Argsbarg authoring rules** — `scripts/merge-agents-md.ts` copies the template from `examples/full-example-json/AGENTS.md` into each consumer. The framework baseline is placed at the top, and all app-specific sections live below `<!-- /argsbarg:managed -->` where they take precedence over framework defaults.
 
-**Recommended in each consumer:** replace template placeholders with `**<app> conventions:**` bullets. Commit `AGENTS.md`; merges refresh the managed section, not your prefix or footer.
+**Recommended in each consumer:** replace template placeholders under `## App conventions` with project-specific bullets. Commit `AGENTS.md`; merges refresh the managed section, not your app-specific sections.
 
 ## Upgrading consumer apps to 7.0
 

package/docs/mcp.md

@@ -343,17 +343,19 @@ When `mcpServer.enabled` is true, **`mcp bundle`** writes dist artifacts you opt
 ```bash
 just build
 ./dist/myapp mcp bundle
-# → dist/myapp.mcpb          (when mcpServer.mcpd: true)
+# → dist/myapp.mcpb               (when mcpServer.mcpd: true)
 # → dist/claude-plugin/myapp.zip  (when mcpServer.claudePlugin: true)
+# → dist/cursor-plugin/myapp.zip  (when mcpServer.cursorPlugin: true)
 ```
 
-Enable one or both flags:
+Enable any combination of packaging flags:
 
 ```typescript
 mcpServer: {
   enabled: true,
   mcpd: true,           // Claude Desktop `.mcpb`
   claudePlugin: true,   // Claude Code plugin zip
+  cursorPlugin: true,   // Cursor plugin zip
 },
 ```
 
@@ -363,8 +365,9 @@ Expects the compiled binary at **`dist/<program.key>`**. Stdout prints one path
 | --- | --- |
 | **`dist/<key>.mcpb`** | Claude Desktop MCP Bundle — when `mcpd: true` (default **false**) |
 | **`dist/claude-plugin/<name>.zip`** | Claude Code plugin zip — when `claudePlugin: true` (default **false**) |
+| **`dist/cursor-plugin/<name>.zip`** | Cursor plugin zip — when `cursorPlugin: true` (default **false**) |
 
-Manifest metadata is generated from your schema (`mcpServerId`, tools, `program.appConfig` user config for env-mapped entries). Optional pack-time fields live under **`mcpServer.bundle`** (`author`, `icon`, `longDescription`).
+Manifest metadata is generated from your schema (`mcpServerId`, tools, `program.appConfig` user config for env-mapped entries). Optional pack-time fields live under **`mcpServer.bundle`** (`author`, `displayName`, `homepage`, `icon`, `license`, `longDescription`, `repository`, `skillsDir`).
 
 **Claude Code plugin zip layout** (paths at archive root):
 
@@ -372,14 +375,24 @@ Manifest metadata is generated from your schema (`mcpServerId`, tools, `program.
 .claude-plugin/plugin.json   # includes "mcpServers": ".mcp.json"
 .mcp.json
 bin/myapp                    # executable (0755 preserved in the zip)
-skills/<dirName>/SKILL.md
+skills/<dirName>/...
 ```
 
-`plugin.json` references `.mcp.json` so Claude Desktop and Claude Code load the bundled MCP server when the plugin is enabled. The plugin zip preserves the executable bit on `bin/<key>`.
+**Cursor plugin zip layout** (paths at archive root):
 
-The bundled `SKILL.md` is an **MCP routing stub** — it tells Claude to use the plugin’s MCP toolset (server id, `tools/list`, schema resource). It is not a shell CLI catalog and does not include `reference.md`. Use **`configure`** for a persisted shell-oriented skill bundle.
+```
+.cursor-plugin/plugin.json   # Cursor plugin manifest
+mcp.json                     # includes mcpServers with ${CURSOR_PLUGIN_ROOT}
+bin/myapp                    # executable (0755 preserved in the zip)
+skills/<dirName>/...
+```
+
+`plugin.json` and `mcp.json` configure Cursor and Claude to load the bundled MCP server when the plugin is enabled. The plugin zip preserves the executable bit on `bin/<key>`.
+
+If the repository has a skill directory under `skills/<dirName>/` (or `mcpServer.bundle.skillsDir`), the plugin bundles that repository skill. Otherwise, it falls back to a generated **MCP routing stub** telling the agent to use the plugin's MCP toolset.
 
-Load locally with `claude --plugin-dir ./dist/claude-plugin/myapp.zip`.
+Load Claude plugin locally with `claude --plugin-dir ./dist/claude-plugin/myapp.zip`.
+Unpack Cursor plugin locally into `~/.cursor/plugins/local/<name>`.
 
 Bare **`myapp mcp`** still runs the stdio MCP server (unchanged for `configure` MCP targets and MCP hosts). Use **`configure install`** for Cursor, Claude Code, Claude Desktop, and OpenCode JSON config.
 

package/docs/output-schema.md

@@ -212,7 +212,7 @@ Per consumer repo (optional):
 4. `just docgen` / `myapp docs cli --save` — refresh consumer docs.
 5. Document which commands use which roots in **your** `docs/architecture.md` (argsbarg does not maintain per-app tables).
 
-Add a bullet under your app’s `**… conventions:**` block in `AGENTS.md` pointing at `node_modules/argsbarg/docs/output-schema.md`.
+Add a bullet under your app’s `## App conventions` section in `AGENTS.md` pointing at `node_modules/argsbarg/docs/output-schema.md`.
 
 **Reference implementation:** [`examples/full-example-json/`](../examples/full-example-json/) in this repo — `@sg` on command types, `__generated__/`, and `status` leaf with `StatusJsonOutputSchema`.
 

package/examples/full-example/AGENTS.md

@@ -1,17 +1,8 @@
 # full-example
 
-## Tooling
-
-- Bun only (`bun`, `bunx`, `bun test`). No Node/npm/pnpm.
-
-## Documentation
-
-- `README.md` — user-facing install/commands
-- `docs/architecture.md` — maintainer internals (create if missing)
-- Generated: `just docgen` → `docs/cli.md`, `docs/cli-schema.json`
-- `skills/full-example/SKILL.md` — agent skill router (scaffolded from template; customize as needed)
+<!-- argsbarg:managed — overwritten on merge; framework baseline; app-specific sections below take precedence -->
 
-<!-- argsbarg:managed -->
+> **Baseline framework rules:** The conventions below are defaults for argsbarg projects. Project-specific sections below this managed block override these defaults.
 
 ## Argsbarg schema
 
@@ -70,8 +61,25 @@ When adding commands: `src/commands/<name>/command.ts`; register in `program.ts`
 - **Tests:** `just test` (after `just check`)
 - **Repository skill:** When adding, renaming, or removing commands, update `skills/<key>/SKILL.md` so the intent-based router remains accurate for end-user agents. (`just docgen` updates `./docs/` only and never overwrites `skills/`).
 
+### Abstractions
+
+Avoid needless extraction: keep single-use helpers in the calling file by default. Split only when reused elsewhere, the caller is large or hard to follow, or extraction clarifies a substantial unit. Do not create tiny one-off helpers.
+- ❌ `utils/formatX.ts` — 60-line helper used by one command
+- ✅ inline helper in that command file
+
 <!-- /argsbarg:managed -->
 
-**full-example conventions:**
+## Tooling
+
+- Bun only (`bun`, `bunx`, `bun test`). No Node/npm/pnpm.
+
+## Documentation
+
+- `README.md` — user-facing install/commands
+- `docs/architecture.md` — maintainer internals (create if missing)
+- Generated: `just docgen` → `docs/cli.md`, `docs/cli-schema.json`
+- `skills/full-example/SKILL.md` — agent skill router (scaffolded from template; customize as needed)
+
+## App conventions
 
 Replace with app-specific bullets.

package/examples/full-example/README.md

@@ -1,24 +1,69 @@
 # full-example
 
-Argsbarg **CLI copy template** — production shell without schemagen (not a kitchen-sink product).
+Argsbarg CLI copy template (MCP, HTTP, configure, skills; no schemagen).
 
-For `@sg` schemagen, JSON Schema validation, and REST CRUD patterns, use `examples/full-example-json/` or `argsbarg create --template json`.
+## Installation
 
-## What's in this app
+Install via Homebrew:
 
-- **Builtins enabled:** CLI, shell completion, `docs`, MCP, HTTP API, `configure`, agent skills
-- **Commands:**
-  - `echo` — simple flags/positionals (MCP-friendly)
-  - `status` — app version with optional `--json` (no `outputSchema`)
-- **Tooling:** `just docgen`, Homebrew/just dev workflow (no schemagen)
+```bash
+brew tap bdombro/bun-argsbarg git@github.com:bdombro/bun-argsbarg.git
+brew install full-example
+full-example configure install
+```
+
+`full-example configure install` sets up shell completions, agent skills, and MCP configuration.
+
+## Commands
+
+- `full-example echo` — Echo text back to stdout or inspect flags.
+- `full-example status` — Show application version with optional `--json`.
+
+### Built-in commands
+
+- `full-example completion` — Install or inspect shell tab completions (bash, zsh, fish).
+- `full-example configure` — Manage agent artifacts (skills, MCP, application configuration).
+- `full-example docs` — Browse bundled documentation topics (`cli`, `mcp`, `http`, `readme`).
+- `full-example mcp` — Start the Model Context Protocol (stdio) server for AI coding agents.
+- `full-example version` — Display version information.
+
+## Usage
+
+```bash
+# Print a message
+full-example echo "Hello, world!"
+
+# Inspect JSON status
+full-example status --json
+
+# Start the MCP server for AI agents
+full-example mcp
+```
+
+## AI Agent & MCP Integration
+
+`full-example` includes an integrated MCP server and agent skills out of the box:
+
+- **MCP server**: Run `full-example mcp` or register via `full-example configure install`.
+- **Agent skill**: See `skills/full-example/SKILL.md` for agent router instructions.
+
+## Documentation
+
+| Need | Resource |
+| --- | --- |
+| CLI reference | [docs/cli.md](docs/cli.md) or `full-example docs cli` |
+| MCP tools | [docs/mcp.md](docs/mcp.md) or `full-example docs mcp` |
+| HTTP API | [docs/http.md](docs/http.md) or `full-example docs http` |
+| Agent skill router | [skills/full-example/SKILL.md](skills/full-example/SKILL.md) |
+| CLI schema (JSON) | [docs/cli-schema.json](docs/cli-schema.json) |
 
-## Quick start
+## Development
 
-From a git checkout at this directory (requires [Homebrew](https://brew.sh), [just](https://just.systems), and [Bun](https://bun.sh)):
+Requires [Homebrew](https://brew.sh), [just](https://just.systems), and [Bun](https://bun.sh):
 
 ```bash
 brew install just bun
 just setup
-just run status --json
-just run docs readme
+just check
+just test
 ```

package/examples/full-example/biome.json

@@ -4,7 +4,10 @@
   "linter": {
     "enabled": true,
     "rules": {
-      "preset": "recommended"
+      "preset": "recommended",
+      "complexity": {
+        "noStaticOnlyClass": "off"
+      }
     }
   },
   "formatter": {
@@ -14,9 +17,7 @@
   },
   "overrides": [
     {
-      "includes": ["**/*.json"],
-      "formatter": { "enabled": false },
-      "linter": { "enabled": false }
+      "includes": ["**/*.json"]
     }
   ]
 }

package/examples/full-example/bunfig.toml

@@ -0,0 +1,3 @@
+[install]
+# fetch package.json deps on first `bun src/index.ts` without manual `bun install`.
+auto = "fallback"

package/examples/full-example/justfile

@@ -1,16 +1,11 @@
+# bash (not sh); -e bail on errors, -u error on unset vars, pipefail fails pipelines when any stage fails
 set shell := ["bash", "-eu", "-o", "pipefail", "-c"]
 
 export PATH := justfile_directory() + "/node_modules/.bin:" + env_var("PATH")
 
-cli_key := `bun scripts/print-identity.ts key`
-tap_org := `bun scripts/print-identity.ts tapOrg`
-tap_repo := `bun scripts/print-identity.ts tapRepo`
-tap := `bun scripts/print-identity.ts tap`
-release_repo := `bun scripts/print-identity.ts releaseRepo`
-tap_git_url := "git@github.com:" + release_repo + ".git"
 brew_prefix := `brew --prefix`
-tap_parent := brew_prefix + "/Library/Taps/" + tap_org
-tap_path := tap_parent + "/homebrew-" + tap_repo
+tap_parent := brew_prefix + "/Library/Taps/{tapOrg}"
+tap_path := tap_parent + "/homebrew-{tapRepo}"
 
 # List available recipes (default)
 _:
@@ -18,7 +13,7 @@ _:
 
 # Compile the CLI binary to dist/full-example
 build:
-    bun build ./src/index.ts --compile --outfile=dist/{{cli_key}}
+    bun build ./src/index.ts --compile --outfile=dist/full-example
     @rm -f .*.bun-build
 
 # Run typecheck and format
@@ -34,11 +29,11 @@ demo-http:
 
 # demo a CLI command
 demo-cli:
-    @just run {{cli_key}} status
+    @just run full-example status
 
 # demo a CLI command
 demo-help:
-    @just run {{cli_key}} --help
+    @just run full-example --help
 
 # Run the CLI from source with optional args; restarts on file changes
 dev *ARGS:
@@ -70,26 +65,26 @@ install-local: uninstall build
     mkdir -p {{tap_parent}}
     ln -sfn '{{justfile_directory()}}' {{tap_path}}
     bun scripts/dev-formula.ts install
-    HOMEBREW_NO_ASK=1 brew reinstall --formula {{tap}}/{{cli_key}} || HOMEBREW_NO_ASK=1 brew install --force --formula {{tap}}/{{cli_key}}
+    HOMEBREW_NO_ASK=1 brew reinstall --formula bdombro/bun-argsbarg/full-example || HOMEBREW_NO_ASK=1 brew install --force --formula bdombro/bun-argsbarg/full-example
     bun scripts/dev-formula.ts reset
-    {{cli_key}} configure install
+    full-example configure install
 
 # Remove local dev install, then install from GitHub tap (requires gh auth login)
 install-production: uninstall
-    brew tap {{release_repo}} {{tap_git_url}}
-    brew install --formula {{release_repo}}/{{cli_key}}
-    {{cli_key}} configure install
+    brew tap bdombro/bun-argsbarg git@github.com:bdombro/bun-argsbarg.git
+    brew install full-example
+    full-example configure install
 
 # Alias for backward compatibility
 reinstall: reinstall-local
 
 # Rebuild binary and swap into Cellar (run install-local first; run `just refresh` for skills/MCP)
 reinstall-local: build
-    install -m 755 dist/{{cli_key}} "$(brew --prefix {{cli_key}})/bin/{{cli_key}}"
+    install -m 755 dist/full-example "$(brew --prefix full-example)/bin/full-example"
 
 # Refresh agent skills/MCP without reinstalling the binary
 refresh:
-    {{cli_key}} configure install
+    full-example configure install
 
 # Lint sources without writing
 lint:
@@ -101,7 +96,7 @@ run *ARGS:
 
 # Generate JSON Schema artifacts from TypeScript types (not used in this template)
 schemagen:
-    @echo "This CLI template has no @sg types. Use full-example-json or add /** @sg */ types first."
+    @echo "No @sg types in the cli template. Use argsbarg create --template json or add /** @sg */ types first."
 
 # Install bun/npm dependencies
 setup:
@@ -118,12 +113,12 @@ release *ARGS:
 
 # Install release formula from tap and run formula test
 test-release:
-    HOMEBREW_NO_ASK=1 brew untap {{tap}} 2>/dev/null || true
+    HOMEBREW_NO_ASK=1 brew untap bdombro/bun-argsbarg 2>/dev/null || true
     mkdir -p {{tap_parent}}
     ln -sfn '{{justfile_directory()}}' {{tap_path}}
-    HOMEBREW_NO_ASK=1 brew uninstall --formula {{tap}}/{{cli_key}} 2>/dev/null || true
-    brew install --formula {{tap}}/{{cli_key}}
-    brew test {{cli_key}}
+    HOMEBREW_NO_ASK=1 brew uninstall --formula bdombro/bun-argsbarg/full-example 2>/dev/null || true
+    brew install --formula bdombro/bun-argsbarg/full-example
+    brew test full-example
 
 # Typecheck without emitting build artifacts
 typecheck:
@@ -131,7 +126,7 @@ typecheck:
 
 # Undo dev/Homebrew install (remove agent artifacts, then keg + untap)
 uninstall:
-    @{{cli_key}} configure uninstall --yes 2>/dev/null || just run configure uninstall --yes
-    @HOMEBREW_NO_ASK=1 brew uninstall --formula {{tap}}/{{cli_key}} 2>/dev/null || true
-    @HOMEBREW_NO_ASK=1 brew uninstall --formula {{tap}}/{{cli_key}}-local 2>/dev/null || true
-    @HOMEBREW_NO_ASK=1 brew untap {{tap}} 2>/dev/null || true
+    @full-example configure uninstall --yes 2>/dev/null || just run configure uninstall --yes
+    @HOMEBREW_NO_ASK=1 brew uninstall --formula bdombro/bun-argsbarg/full-example 2>/dev/null || true
+    @HOMEBREW_NO_ASK=1 brew uninstall --formula bdombro/bun-argsbarg/full-example-local 2>/dev/null || true
+    @HOMEBREW_NO_ASK=1 brew untap bdombro/bun-argsbarg 2>/dev/null || true

package/examples/full-example-json/AGENTS.md

@@ -1,17 +1,8 @@
 # full-example-json
 
-## Tooling
-
-- Bun only (`bun`, `bunx`, `bun test`). No Node/npm/pnpm.
+<!-- argsbarg:managed — overwritten on merge; framework baseline; app-specific sections below take precedence -->
 
-## Documentation
-
-- `README.md` — user-facing install/commands
-- `docs/architecture.md` — maintainer internals (create if missing)
-- Generated: `just docgen` → `docs/cli.md`, `docs/cli-schema.json`
-- `skills/full-example-json/SKILL.md` — agent skill router (scaffolded from template; customize as needed)
-
-<!-- argsbarg:managed -->
+> **Baseline framework rules:** The conventions below are defaults for argsbarg projects. Project-specific sections below this managed block override these defaults.
 
 ## Argsbarg schema
 
@@ -83,6 +74,17 @@ Avoid needless extraction: keep single-use helpers in the calling file by defaul
 
 <!-- /argsbarg:managed -->
 
-**full-example-json conventions:**
+## Tooling
+
+- Bun only (`bun`, `bunx`, `bun test`). No Node/npm/pnpm.
+
+## Documentation
+
+- `README.md` — user-facing install/commands
+- `docs/architecture.md` — maintainer internals (create if missing)
+- Generated: `just docgen` → `docs/cli.md`, `docs/cli-schema.json`
+- `skills/full-example-json/SKILL.md` — agent skill router (scaffolded from template; customize as needed)
+
+## App conventions
 
 Replace with app-specific bullets.

package/examples/full-example-json/README.md

@@ -1,27 +1,75 @@
 # full-example-json
 
-Argsbarg **schema-first copy template** — `@sg` schemagen, JSON Schema validation, REST CRUD demo (not a kitchen-sink product).
+Argsbarg schema-first copy template (@sg schemagen, JSON schemas, REST CRUD).
 
-For a CLI-only template without schemagen, use `examples/full-example/` or `argsbarg create --template cli`.
+## Installation
 
-## What's in this app
+Install via Homebrew:
 
-- **Builtins enabled:** CLI, shell completion, `docs`, MCP, HTTP API, `configure`, agent skills
-- **Commands:**
-  - `echo` — simple flags/positionals
-  - `render-json` — `kind: "json"` leaf, schemagen `inputSchema`, `ctx.inputsAs`
-  - `status` — schemagen `outputSchema`, `--json`
-  - `workspaces` — REST CRUD, `:id` param routers, verb leaves, schemagen input schemas
-- **Tooling:** `@sg` schemagen, `just docgen`, Homebrew/just dev workflow, in-memory SQLite (`bun:sqlite`)
+```bash
+brew tap bdombro/bun-argsbarg git@github.com:bdombro/bun-argsbarg.git
+brew install full-example-json
+full-example-json configure install
+```
+
+`full-example-json configure install` sets up shell completions, agent skills, and MCP configuration.
+
+## Commands
+
+- `full-example-json echo` — Echo text back to stdout or inspect flags.
+- `full-example-json render-json` — Process structured JSON payloads with schema validation.
+- `full-example-json status` — Show application version with schemagen output schema (`--json`).
+- `full-example-json workspaces` — Manage workspace resources (REST CRUD with in-memory SQLite).
+
+### Built-in commands
+
+- `full-example-json completion` — Install or inspect shell tab completions (bash, zsh, fish).
+- `full-example-json configure` — Manage agent artifacts (skills, MCP, application configuration).
+- `full-example-json docs` — Browse bundled documentation topics (`cli`, `mcp`, `http`, `readme`).
+- `full-example-json mcp` — Start the Model Context Protocol (stdio) server for AI coding agents.
+- `full-example-json version` — Display version information.
+
+## Usage
+
+```bash
+# Print a message
+full-example-json echo "Hello, world!"
+
+# Inspect JSON status
+full-example-json status --json
+
+# List workspaces
+full-example-json workspaces list
+
+# Start the MCP server for AI agents
+full-example-json mcp
+```
+
+## AI Agent & MCP Integration
+
+`full-example-json` includes an integrated MCP server and agent skills out of the box:
+
+- **MCP server**: Run `full-example-json mcp` or register via `full-example-json configure install`.
+- **Agent skill**: See `skills/full-example-json/SKILL.md` for agent router instructions.
+
+## Documentation
+
+| Need | Resource |
+| --- | --- |
+| CLI reference | [docs/cli.md](docs/cli.md) or `full-example-json docs cli` |
+| MCP tools | [docs/mcp.md](docs/mcp.md) or `full-example-json docs mcp` |
+| HTTP API | [docs/http.md](docs/http.md) or `full-example-json docs http` |
+| Agent skill router | [skills/full-example-json/SKILL.md](skills/full-example-json/SKILL.md) |
+| CLI schema (JSON) | [docs/cli-schema.json](docs/cli-schema.json) |
 
-## Quick start
+## Development
 
-From a git checkout at this directory (requires [Homebrew](https://brew.sh), [just](https://just.systems), and [Bun](https://bun.sh)):
+Requires [Homebrew](https://brew.sh), [just](https://just.systems), and [Bun](https://bun.sh):
 
 ```bash
 brew install just bun
 just setup
-just schemagen   # after changing @sg types in src/
-just run status --json
-just run docs readme
+just schemagen   # after modifying @sg types in src/
+just check
+just test
 ```

package/examples/full-example-json/biome.json

@@ -14,9 +14,7 @@
   },
   "overrides": [
     {
-      "includes": ["**/*.json"],
-      "formatter": { "enabled": false },
-      "linter": { "enabled": false }
+      "includes": ["**/*.json"]
     }
   ]
 }

package/examples/full-example-json/bunfig.toml

@@ -0,0 +1,3 @@
+[install]
+# fetch package.json deps on first `bun src/index.ts` without manual `bun install`.
+auto = "fallback"