Rename the app to Denpa #25

New issue

Closed

opened 2026-07-29 17:46:22 +00:00 by aiko · 1 comment

aiko commented

2026-07-29 17:46:22 +00:00

Owner

What to build

The app is now called Denpa (電波). Carry the name through every place the old one is baked in, in one pass, before the redesign slices land on top of it.

package.json name, and anything derived from it in the build
Tauri productName, window titles, and the tray/menu entries
The web index.html title and any PWA manifest name
User-visible copy and i18n strings that say the old product name
Repo README

The Tauri bundle identifier is the one to think about, not just rename. Changing it makes the OS treat the build as a different application: new config/data directory, a separate installed entry alongside the old one, and any persisted state (endpoint, token, pal scale per monitor) is orphaned rather than migrated. Either keep the existing identifier and rename only the display name, or change it and migrate the old config directory on first run. Pick one deliberately and say which in the PR.

Not in scope here: the Forgejo repo rename and the design-doc wording, both already done separately.

Acceptance criteria

No user-visible surface still shows the old product name
Desktop build installs and launches under the new name on Windows
Android build's app label and package identity are consistent with the decision above
Bundle-identifier decision is stated explicitly; if it changed, existing settings survive an upgrade
npm run typecheck, npm run lint and the test suite pass

Blocked by

None - can start immediately

## What to build The app is now called **Denpa** (電波). Carry the name through every place the old one is baked in, in one pass, before the redesign slices land on top of it. - `package.json` name, and anything derived from it in the build - Tauri `productName`, window titles, and the tray/menu entries - The web `index.html` title and any PWA manifest name - User-visible copy and i18n strings that say the old product name - Repo README **The Tauri bundle identifier is the one to think about, not just rename.** Changing it makes the OS treat the build as a different application: new config/data directory, a separate installed entry alongside the old one, and any persisted state (endpoint, token, pal scale per monitor) is orphaned rather than migrated. Either keep the existing identifier and rename only the display name, or change it and migrate the old config directory on first run. Pick one deliberately and say which in the PR. Not in scope here: the Forgejo repo rename and the design-doc wording, both already done separately. ## Acceptance criteria - [ ] No user-visible surface still shows the old product name - [ ] Desktop build installs and launches under the new name on Windows - [ ] Android build's app label and package identity are consistent with the decision above - [ ] Bundle-identifier decision is stated explicitly; if it changed, existing settings survive an upgrade - [ ] `npm run typecheck`, `npm run lint` and the test suite pass ## Blocked by None - can start immediately

aiko added the

ready-for-agent

label

2026-07-29 17:46:22 +00:00

aiko commented

2026-07-30 13:33:00 +00:00

Author

Owner

Shipped. Merged to main at f796efa (phase D — rename), 13 string literals, review verdict clean. The Tauri bundle identifier works.aiko.ollvt was proven byte-identical, and no localStorage key, config path or data directory moved.

Closing with two acceptance boxes never observed, recorded here rather than quietly ticked:

"Desktop build installs and launches under the new name"
The Android launcher label

Both were asserted from config, not from a running build. They are covered by the v1 proof-of-done — a real conversation on desktop, tablet and phone — tracked on the wayfinder map aiko/denpa#41. If either turns out wrong, it surfaces there.

Closed as part of reconciling the board with main: the autonomous run's policy was not to auto-close, so shipped work stayed open. That policy is now reversed — issues close when they land.

Shipped. Merged to `main` at `f796efa` (phase D — rename), 13 string literals, review verdict clean. The Tauri bundle identifier `works.aiko.ollvt` was proven byte-identical, and no localStorage key, config path or data directory moved. **Closing with two acceptance boxes never observed**, recorded here rather than quietly ticked: - "Desktop build installs and launches under the new name" - The Android launcher label Both were asserted from config, not from a running build. They are covered by the v1 proof-of-done — a real conversation on desktop, tablet and phone — tracked on the wayfinder map [aiko/denpa#41](https://git.aiko.works/aiko/denpa/issues/41). If either turns out wrong, it surfaces there. Closed as part of reconciling the board with `main`: the autonomous run's policy was not to auto-close, so shipped work stayed open. That policy is now reversed — issues close when they land.

aiko closed this issue

2026-07-30 13:33:00 +00:00