Internal names are Overlight's too #24
Loading…
Reference in a new issue
No description provided.
Delete branch "rename-internals"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
With no plugin written against the SDK yet and one user, the internal names follow the product now, before anything depends on them.
Renamed
@kanbot/*→@overlight/*, the root package isoverlight;KanbotPlugin→OverlightPlugin,startKanbot()/kanbot()→startOverlight()/overlight(), and the otherKanbot*types and components.server/kanbot→server/overlight,kanbot-plugin.json→overlight-plugin.json, the manifest'skanbotrange →overlight.KANBOT_*→OVERLIGHT_*,kanbot-hub/kanbot-node→overlight-hub/overlight-node,.kanbot/settings.json→.overlight/settings.json, the compose service and volume (overlight,overlight-data).Context.Serviceids, the agent's MCP tool prefix, lint rule names,CLAUDE.md, the docs and CI.app.overlight.desktop, and its first start moves an existing<appData>/Kanbotfolder to Overlight's, so a board, pairing and settings from before carry over.Kept on purpose
taskmaster.dband thekanbot_migrationstable: renaming them needs a migration for nothing anyone sees.CLAUDE.mdfiles written before keep receiving lessons under.After merging
Nothing reads the old names any more:
KANBOT_*in any.envor shell profile, and a committed.kanbot/settings.jsonin a repository;kanbot-datavolume: copy it tooverlight-databefore upgrading;@overlight/plugin-sdk.Checks
@overlight/plugin-sdk, Storybook.OVERLIGHT_DATA_DIRand loads all four plugins active.🤖 Generated with Claude Code