fix: PLUGIN_VERSION drifted from package.json, and config omitted defaults.color

[motin]

Two loose ends spotted while installing the published tabby-cctabs 0.1.4 on a real fleet.

PLUGIN_VERSION drifted, again

Published tabby-cctabs@0.1.4 ships with PLUGIN_VERSION = '0.1.5', so /api/health — and therefore cctabs doctor — reports a version that was never published:

$ npm pack tabby-cctabs@0.1.4 && grep -o "PLUGIN_VERSION = '[^']*'" package/dist/index.js
PLUGIN_VERSION = '0.1.5'

My colour PR set both to 0.1.5 consistently; the renumber down to 0.1.4 caught package.json and missed the constant. Entirely my kind of mistake to have set up, so: fixed, plus a guard.

Behaviourally harmless — plugin features are feature-detected through capabilities, never compared by version, so nothing breaks. That is exactly why it has now drifted twice and survived review both times (once a release behind, per the note in CLAUDE.md; now once ahead). Nothing fails, so nobody notices.

Hence a test rather than a third note asking the next person to remember:

expect(PLUGIN_VERSION).toBe(pkg.version)

It lives in src/ because that's where npm test looks (bun test src/), which does mean a CLI test reaching into tabby-plugin/. I think the trade is worth it for an invariant that's now failed twice, but it's the one part of this PR I'd understand you dropping — the alternative is a plugin-side test setup that doesn't exist yet.

cctabs config omitted defaults.color

It printed claude.flags, defaults.workspace and defaults.prefix, so the one command whose job is "show me what my config is" silently left out a setting it was honouring. Concretely, with color = "orange" set and working:

$ cctabs config
claude.flags       = [...]
defaults.workspace = (none)
defaults.prefix    = (none)

which reads as "the colour wasn't picked up" when in fact it resolves fine. My omission in the colour PR.

Testing

npm test — 226 pass, 0 fail. npm run typecheck and npm run build clean. The guard test deliberately uses fileURLToPath(new URL(...)) rather than Bun's import.meta.dir, so typecheck passes without depending on @types/bun resolving.

Verified on a live 53-tab fleet: CLI 0.5.1 from npm has both features, plugin 0.1.4 installed via cctabs install-tabby-plugin --no-restart (the --no-restart flag is genuinely useful here — restarting Tabby under 53 tabs is not a casual act), and [backends.enterprise] color = "blue" + [defaults] color = "orange" resolves to #0275d8 / #f0ad4e as intended.

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying cctabs with    Cloudflare Pages

Latest commit:	60305b0
Status:	✅  Deploy successful!
Preview URL:	https://7338e608.cctabs.pages.dev
Branch Preview URL:	https://fix-plugin-version-drift.cctabs.pages.dev

View logs