Stale pre-migration repo URLs and package name after move to brmbh/wordpress

[Schmandarine]

This repo moved from Schmandarine/brmbh-agentic-wp-suite to brmbh/wordpress, but the old name is still baked into the theme's own files and into the CLI that clones it.

Verified state

Where	Value	Status
git remote	brmbh/wordpress	—
package.json → name	brmbh-agentic-wp-suite	stale
package.json → repository / homepage	Schmandarine/brmbh-agentic-wp-suite	⚠️ redirect only
style.css → Theme URI	Schmandarine/brmbh-agentic-wp-suite	⚠️ redirect only
skills/wordpress/SKILL.md → offline --from example	brmbh-agentic-wp-suite	stale
brmbh/cli src/registry.js:13 → THEME_REPO	Schmandarine/brmbh-agentic-wp-suite.git	⚠️ redirect only

The old URL still resolves — git ls-remote succeeds and gh repo view Schmandarine/brmbh-agentic-wp-suite reports brmbh/wordpress — because GitHub keeps a redirect after a repo transfer.

Why that redirect is not good enough

brmbh create clones this repo through the hardcoded THEME_REPO constant, so the redirect is currently load-bearing for the CLI's main feature. It disappears the moment anyone creates a new repo at Schmandarine/brmbh-agentic-wp-suite. And because the constant ships inside each published CLI version, older versions cannot be patched afterwards — they would break permanently.

The CLI is still at 0.1.0 and unpublished. This is the cheap moment to fix it.

Tasks

• package.json → repository, homepage → brmbh/wordpress
• style.css → Theme URI → brmbh/wordpress
• Decide whether the package/theme name stays brmbh-agentic-wp-suite or becomes something shorter now that the repo is brmbh/wordpress — coordinate with Theme should declare its own scaffold contract so the CLI can personalize it #4, which proposes declaring the text domain in a manifest. Renaming it later is a breaking change for every scaffolded site, so decide once, now.
• Confirm Stale pre-migration repo URLs: THEME_REPO relies on a redirect, README clone URL is dead cli#4 lands the THEME_REPO change in the same pass

Note

Do not rename the text domain casually. It is the identifier WordPress uses to group a theme's translatable strings, and it appears 65 times across 25 files here (see #4). If it changes, it must change everywhere at once.

Related: brmbh/cli#4, #4

[Schmandarine]

URLs fixed in a3b4512, pushed. homepage, repository.url, and the style.css Theme URI now point at brmbh/wordpress. No Schmandarine references remain in either repo (the CLI side, including 9 links on the live landing page, is brmbh/cli#4 — now closed).

Still open: the name. package.json name, style.css Theme Name, and the brmbh-agentic-wp-suite text domain (65 occurrences, 25 files) are unchanged pending a decision. Keeping this issue open for that.

Relevant context for the call: the scaffold personalization step (#4) will rewrite the text domain per project anyway, so the starter's own name mostly matters for (a) this repo's identity and (b) anyone who clones it directly and never personalizes. Existing derivatives like brmbh-megaherz are independent copies and are unaffected either way.

[Schmandarine]

Done — closed by a3b4512 (URLs) and 1588056 (rename).

Decision: the theme is now brmbh. Text domain brmbh, Theme Name brmbh, package brmbh. 61 replacements across 28 files.

Two things worth recording:

It fixed a pre-existing mismatch. AGENTS/create-block.md already instructed agents to write "textdomain": "brmbh" into every new block, while the theme itself used brmbh-agentic-wp-suite. Every block the skill generated disagreed with the theme it lived in. They now match.

Deliberately not renamed: the wp brmbh WP-CLI namespace and the BRMBH_* PHP constants — both already short and correct. (The wp brmbh vs brmbh name collision is a separate concern, #7.)

Verified before pushing: php -l clean on all changed PHP, npm run build green (webpack + both Sass entries).

Breaking change flagged in the commit: translation files keyed to the old domain stop resolving. Themes already scaffolded from this starter are independent copies and are unaffected.