Files

T

Serhii DziupinandSerhii Dziupin 86e6a2ae76 Remove verified dead declarations (#2714 )

* chore: remove verified dead declarations

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* chore: narrow unused internal exports

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* chore: remove newly exposed dead helpers

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* chore: remove unused deep-link serializer

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: drop two tests that assert on copies of the code

mainLayoutMobileSidebarMount read MainLayout.tsx and SessionSidebar.tsx as
strings and asserted on source substrings down to exact indentation, so it
failed on formatting rather than behaviour. useProjectSessionSelection.test
reimplemented the hook's visitNodes logic inside the test file and asserted
against that copy, so it could not observe the hook at all.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: repair sync suites that had rotted while unrunnable

No runner executed packages/ui, so these drifted from the source unnoticed:
two imported helpers that are no longer exported, one directory-store stub
predated the session field routeMessage reads, and the WebSocket fake missed
the mandatory url-token mint plus the close event the socket wrapper reads.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: stop the web suite failing on timeouts and a hand-copied mock

The Git suites drive a real git binary, so the 5s default made a valid suite
fail differently per run. The gitApiHttp mock listed ~70 export names by hand
and fell behind the source; it now derives every stub from the real module,
which the added shared-UI aliases make resolvable.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: run every suite from one command and in CI

packages/ui (232 files) and packages/vscode (22) had no test script at all, CI
ran neither, and 9 vscode files could never run because Node cannot resolve
their extensionless TypeScript imports. Three electron files sat outside every
script list, one of them importing vitest, which that package does not depend
on. A runner gives each file its own process, since these suites keep
module-level singletons and fail by load order when sharing one.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* chore: delete a superseded repro harness and a completed plan

The issue-2638 harness needed lsof, overrode process.platform and spawned real
servers, and nothing referenced it; event-stream/rebind.test.js now covers the
same hub-pinned-to-the-old-port behaviour. The pairing v2 plan described relay
and the pairing UI as out of scope, both of which shipped.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* docs: point at the theme tools and record the github barrel invariant

convert-vscode-theme and harmonize-theme were referenced nowhere, so the
theme-authoring reference now names them. The github barrel is loaded through
await import('./index.js') and destructured per route, which no static report
can see; documenting that is what stops the next cleanup from deleting it.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: repair merge drift in bridge and route-registry mocks

upstream/main gained upsertProviderConfig on bridge-system-runtime and a
PATCH scheduled-task route after this branch forked. Their test doubles
were never updated to match:
- bridge-system-runtime.test.js: add upsertProviderConfig to the
  opencodeConfig mock so the import resolves.
- sse-routes.test.js: add app.patch to the route registry stub.

---------

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

2026-08-13 15:30:54 +03:00

1.5 KiB

Raw Blame History

title

title
Adding Themes

Adding Themes

Custom Themes (User)

Drop a JSON file into ~/.config/openchamber/themes/. No rebuild needed.

Create theme file (e.g., my-theme.json)
In app: Settings → Theme → Reload themes
Select from dropdown

See docs/CUSTOM_THEMES.md for full format reference.

Built-in Themes (Development)

1. Create JSON Files

Add to packages/ui/src/lib/theme/themes/:

<id>-light.json
<id>-dark.json

Use existing themes (e.g., flexoki-dark.json) as reference for the full structure.

2. Register in presets.ts

import mytheme_light_Raw from './mytheme-light.json';
import mytheme_dark_Raw from './mytheme-dark.json';

export const presetThemes: Theme[] = [
  // ... existing themes
  mytheme_light_Raw as Theme,
  mytheme_dark_Raw as Theme,
];

3. Validate

bun run type-check && bun run lint && bun run build

Authoring Tools

Both do the mechanical work of steps 1–2 and are run by hand:

node scripts/convert-vscode-theme.cjs <vscode-theme.json> converts a VS Code theme into this format and registers it in presets.ts.
node scripts/harmonize-theme.mjs <theme.json> [--write] aligns accent roles to one chroma/lightness target in OKLCH so borrowed colors read as one family.

Key Files

Theme types: packages/ui/src/types/theme.ts
Presets: packages/ui/src/lib/theme/themes/presets.ts
Example: packages/ui/src/lib/theme/themes/flexoki-dark.json
Custom themes doc: docs/CUSTOM_THEMES.md

1.5 KiB Raw Blame History Unescape Escape