rebrandlisted

# Rebrand Migrate an application's old brand/product identity to a new one across the entire repository. **Core principle:** this is a *controlled migration*, not a search-and-replace. Priorities, in order: 1. Preserve functionality 2. Avoid destructive changes 3. Remove unintended old branding 4. Maintain naming consistency 5. Validate the result ## When to use Use this for migrating a product or application's brand identity across a repository: display name, package metadata, source identifiers, config, docs, tests, deployment, and asset references. Do not use it for renaming a single variable or symbol, renaming a git branch, renaming a file, or refactoring unrelated to brand identity. Read [references/safety-rules.md](references/safety-rules.md) before editing and use [references/rebrand-manifest.md](references/rebrand-manifest.md) as the audit template. ## Inputs Invocation forms (Pi skill command; extra text is passed as arguments): ```text /skill:rebrand # infer names from the repo, ask if unclear /skill:rebrand OldName -> NewName # use these directly /skill:rebrand OldName to NewName # accept "->", "to", or "=>" ``` If either name cannot be reliably determined, ask exactly: ```text Old brand: New brand: ``` Never guess a new brand name. If the old brand is inferable from manifests (`discover.sh` prints candidates) but the new one is missing, ask only for the new brand. Stop and ask when the old and new brand are ident