Two different programs are both called brmbh (wp brmbh vs the Node CLI)

[Schmandarine]

There are two different programs called brmbh, and the docs put them next to each other without ever saying they are unrelated.

Invocation	What it actually is	Where it lives
wp brmbh scaffold / wp brmbh tokens	a WP-CLI subcommand, PHP, runs inside WordPress	this theme, inc/cli.php
brmbh create / brmbh dev / brmbh doctor	the Node CLI, separate npm package	brmbh/cli

Different languages, different runtimes, different install mechanisms, different repos. Same word.

Where they collide in the docs

AGENTS/sync-tokens.md has a section literally titled "When to use this vs wp brmbh tokens" with a comparison table — good, that one is careful. But AGENTS.md lists wp brmbh scaffold and wp brmbh tokens in the same tables that describe agent capabilities, while skills/wordpress/SKILL.md documents brmbh doctor, brmbh create, brmbh add block. Nothing states that the leading wp is load-bearing.

Why it matters here specifically

This is a codebase whose entire premise is that agents drive it. An agent that drops the wp prefix gets "unknown command"; one that adds it gets a WP-CLI error. Both are recoverable, but both burn a turn and some confidence, and neither failure explains the real cause.

The risk grows with #6, where npx brmbh becomes the recommended in-theme invocation — at that point both forms are correct in the same directory, for different things.

Options

1. Document the distinction and move on. A short table at the top of AGENTS.md: "two commands share the brmbh name — wp brmbh … is this theme's WP-CLI plugin, brmbh …/npx brmbh … is the Node CLI." Cheapest, probably sufficient.
2. Rename the WP-CLI namespace (e.g. wp brmbh-theme …). Cleaner long term, but it is a breaking change to documented commands and appears throughout inc/cli.php and the skill docs.
3. Have the Node CLI proxy it — brmbh scaffold shells out to wp brmbh scaffold. One name, one entry point. But it makes the Node CLI a hard requirement for something that currently works without it, which cuts against Support two install paths — make the theme-first (direct download) route first-class #6.

Recommend 1 now, and consider 2 before the first tagged release — while there are no external users to break.

Acceptance

AGENTS.md states the distinction before either command appears, and no doc lists both forms in the same table without labelling which is which.

Related: #6