Stale pre-migration repo URLs: THEME_REPO relies on a redirect, README clone URL is dead

[Schmandarine]

Both repos have moved to the brmbh org, but the README and src/registry.js still carry pre-migration URLs. One is dead, one survives only on a GitHub redirect.

The two repos and how they connect

	Repo	Role
CLI	github.com/brmbh/cli	this repo — published as @brmbh/cli / create-brmbh
Theme	github.com/brmbh/wordpress	the starter theme create clones

They are coupled in both directions:

• CLI → theme: THEME_REPO (src/registry.js:13) hardcodes the clone URL used by create.
• Theme → CLI: the theme's skills/wordpress/SKILL.md tells users to run npx create-brmbh and npm install -g @brmbh/cli.

Verified state of every URL

Where	Value	Status
git remote (this repo)	brmbh/cli	—
package.json → repository.url	brmbh/cli	✅ correct
package.json → homepage	brmbh/wordpress	✅ correct — this is the theme repo
src/registry.js:13 → THEME_REPO	Schmandarine/brmbh-agentic-wp-suite	⚠️ works, but only via GitHub's transfer redirect to brmbh/wordpress
README.md → local-dev clone command	Schmandarine/brmbh-cli	❌ dead — repo does not exist, git ls-remote fails
README.md → intro link (theme)	Schmandarine/brmbh-agentic-wp-suite	⚠️ redirect only

What to fix

1. THEME_REPO → https://github.com/brmbh/wordpress.git. create is not broken today: GitHub keeps a redirect after a repo transfer, so the old URL still clones. But that redirect is not a guarantee — it disappears the moment anyone creates a new repo at Schmandarine/brmbh-agentic-wp-suite, and the constant is baked into every published version of the CLI. This is the one with real consequences.

2. README local-dev clone URL → brmbh/cli. Currently dead; anyone following the contributing instructions hits a 404.

3. README intro link → brmbh/wordpress.

4. package.json repository and homepage are both already correct — no change needed. (An earlier revision of this issue called homepage into question; it is right, it points at the theme, which is the useful landing page for the npm listing.)

Why now

The package is at 0.1.0 and unpublished. THEME_REPO is a hardcoded constant, so once npm create brmbh@latest is live, every released version carries whatever URL it shipped with. If the old redirect ever lapses, older CLI versions break permanently and there is no way to patch them. Cheapest moment to get this right is before the first publish.

Acceptance

• THEME_REPO, the README, and package.json all reference brmbh/cli and brmbh/wordpress — no Schmandarine/ URLs remain anywhere in the repo (grep -rn "Schmandarine" . --exclude-dir=node_modules --exclude-dir=.git).
• node bin/brmbh.js create smoke-test --skip-install clones successfully from the new URL.

[Schmandarine]

Correction — the package IS published. The body says "still at 0.1.0 and unpublished". Wrong:

npm view @brmbh/cli → version 0.1.0, created 2026-06-22T11:32:35Z

That makes this issue worse, not milder. The published 0.1.0 tarball already contains THEME_REPO = Schmandarine/brmbh-agentic-wp-suite, and a published version cannot be retroactively patched. Anyone running that version depends on GitHub's transfer redirect surviving indefinitely. Fixing it locally only protects future versions.

Also worth recording: create-brmbh is not published as its own package (npm view create-brmbh → 404). It only exists as a second bin entry inside @brmbh/cli, and npx <name> does not search other packages' bin fields — so the headline npx create-brmbh my-theme has 404'd for real users since publish day. Only npx -y -p @brmbh/cli create-brmbh my-theme works. Tracked in the vault Alignment Plan as item 1; relevant here because both are symptoms of the same unfinished migration.

Pending #8, which may make this moot.

[Schmandarine]

Partially dissolved by brmbh/wordpress#8. THEME_REPO disappears entirely — once the CLI lives inside the theme repo, create copies from its own package rather than cloning a remote, so there is no hardcoded clone URL to go stale.

What survives: the published @brmbh/cli@0.1.0 on npm still contains the old URL and still depends on the GitHub redirect. That is not fixable retroactively — it is resolved by publishing 1.0.0 from the new location and deprecating the old entry (both in the brmbh/wordpress#8 checklist).

The dead README clone URL (Schmandarine/brmbh-cli) is being fixed now regardless, since a stale command in a public README is wrong today.

[Schmandarine]

Fixed in 37bece2, pushed.

• THEME_REPO → https://github.com/brmbh/wordpress.git (was riding the post-transfer redirect, which brmbh create depended on)
• README local-dev clone URL → brmbh/cli (the old one, Schmandarine/brmbh-cli, never existed)
• Also found: the live landing page linked to the old repo in 9 places across site/index.html and site/docs.html, including the LICENSE link. Fixed in the same commit — those are user-facing on https://brombach.de/wordpress-suite/ and were not part of this issue as originally written.

Verified: git ls-remote https://github.com/brmbh/wordpress.git resolves, main at a3b4512.

grep -rn Schmandarine now returns nothing in either repo.

Not fixed, and not fixable here: published @brmbh/cli@0.1.0 still contains the old constant. Resolved by publishing from the new location — brmbh/wordpress#8.