Internal names are Overlight's too #24

Merged
alex merged 1 commit from rename-internals into main 2026-10-29 21:19:53 +01:00
Owner

With no plugin written against the SDK yet and one user, the internal names follow the product now, before anything depends on them.

Renamed

  • Packages: @kanbot/* → @overlight/*, the root package is overlight; KanbotPlugin → OverlightPlugin, startKanbot()/kanbot() → startOverlight()/overlight(), and the other Kanbot* types and components.
  • Paths and files: server/kanbot → server/overlight, kanbot-plugin.json → overlight-plugin.json, the manifest's kanbot range → overlight.
  • What you type or configure: KANBOT_* → OVERLIGHT_*, kanbot-hub/kanbot-node → overlight-hub/overlight-node, .kanbot/settings.json → .overlight/settings.json, the compose service and volume (overlight, overlight-data).
  • Internals: cookies, headers, the hub's mDNS type, Context.Service ids, the agent's MCP tool prefix, lint rule names, CLAUDE.md, the docs and CI.
  • Desktop: the app id is app.overlight.desktop, and its first start moves an existing <appData>/Kanbot folder to Overlight's, so a board, pairing and settings from before carry over.

Kept on purpose

  • taskmaster.db and the kanbot_migrations table: renaming them needs a migration for nothing anyone sees.
  • The "Lessons learned (Kanbot)" heading, which CLAUDE.md files written before keep receiving lessons under.

After merging

Nothing reads the old names any more:

  • rename KANBOT_* in any .env or shell profile, and a committed .kanbot/settings.json in a repository;
  • a Docker hub's data is in the old kanbot-data volume: copy it to overlight-data before upgrading;
  • paired browsers and devices sign in again (the cookies changed);
  • a new desktop build installs beside the old Kanbot app (new app id): its data moves over on first start, then delete the old app;
  • publish the SDK once as @overlight/plugin-sdk.

Checks

  • CI run #193 is fully green: lint, typecheck, tests, the SDK pack as @overlight/plugin-sdk, Storybook.
  • A fresh boot of the renamed app keeps its data under OVERLIGHT_DATA_DIR and loads all four plugins active.
  • The desktop app was not built or launched here.

🤖 Generated with Claude Code

With no plugin written against the SDK yet and one user, the internal names follow the product now, before anything depends on them. ## Renamed - **Packages**: `@kanbot/*` → `@overlight/*`, the root package is `overlight`; `KanbotPlugin` → `OverlightPlugin`, `startKanbot()`/`kanbot()` → `startOverlight()`/`overlight()`, and the other `Kanbot*` types and components. - **Paths and files**: `server/kanbot` → `server/overlight`, `kanbot-plugin.json` → `overlight-plugin.json`, the manifest's `kanbot` range → `overlight`. - **What you type or configure**: `KANBOT_*` → `OVERLIGHT_*`, `kanbot-hub`/`kanbot-node` → `overlight-hub`/`overlight-node`, `.kanbot/settings.json` → `.overlight/settings.json`, the compose service and volume (`overlight`, `overlight-data`). - **Internals**: cookies, headers, the hub's mDNS type, `Context.Service` ids, the agent's MCP tool prefix, lint rule names, `CLAUDE.md`, the docs and CI. - **Desktop**: the app id is `app.overlight.desktop`, and its first start moves an existing `<appData>/Kanbot` folder to Overlight's, so a board, pairing and settings from before carry over. ## Kept on purpose - `taskmaster.db` and the `kanbot_migrations` table: renaming them needs a migration for nothing anyone sees. - The "Lessons learned (Kanbot)" heading, which `CLAUDE.md` files written before keep receiving lessons under. ## After merging Nothing reads the old names any more: - rename `KANBOT_*` in any `.env` or shell profile, and a committed `.kanbot/settings.json` in a repository; - a Docker hub's data is in the old `kanbot-data` volume: copy it to `overlight-data` before upgrading; - paired browsers and devices sign in again (the cookies changed); - a new desktop build installs beside the old Kanbot app (new app id): its data moves over on first start, then delete the old app; - publish the SDK once as `@overlight/plugin-sdk`. ## Checks - CI run #193 is fully green: lint, typecheck, tests, the SDK pack as `@overlight/plugin-sdk`, Storybook. - A fresh boot of the renamed app keeps its data under `OVERLIGHT_DATA_DIR` and loads all four plugins active. - The desktop app was not built or launched here. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Internal names are Overlight's too
All checks were successful
CI / check (push) Successful in 1m45s
CI / check (pull_request) Successful in 2m6s
c9233e85ea
With no plugin written against the SDK yet and one user, the internal
names follow the product before anything depends on them:

- packages @kanbot/* → @overlight/* (the root package is overlight),
  KanbotPlugin → OverlightPlugin, startKanbot/kanbot() → startOverlight/
  overlight(), and the other Kanbot* types and components;
- server/kanbot → server/overlight, kanbot-plugin.json →
  overlight-plugin.json, the manifest's `kanbot` range → `overlight`;
- KANBOT_* variables → OVERLIGHT_*, kanbot-hub/kanbot-node →
  overlight-hub/overlight-node, .kanbot/settings.json →
  .overlight/settings.json, the compose service and volume;
- cookies, headers, the hub's mDNS type, Context.Service ids, the agent's
  MCP tool prefix, lint rule names, CLAUDE.md, the docs and CI.

The desktop app's id is app.overlight.desktop, and its first start moves
an existing <appData>/Kanbot folder to Overlight's, so a board, pairing and
settings from before carry over.

Kept on purpose: taskmaster.db and the kanbot_migrations table (renaming
them needs a migration for nothing anyone sees), and "Lessons learned
(Kanbot)", which CLAUDE.md files written before keep receiving lessons under.

Nothing reads the old names any more: an .env, a repository's
.kanbot/settings.json or a hub's kanbot-data volume has to be renamed, and
paired browsers and devices sign in again (the cookies changed).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
alex merged commit a8d6c15bd7 into main 2026-10-29 21:19:53 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Overlight/App!24
No description provided.