Design: KTW dashboard as a library shared with Maity
tsk-k0zz9s2sy5xd done Maity KTW Integrator (maity-ktw-integrator)
From Oliver's briefing to maity-ktw-integrator: make the KTW dashboard's views (timeline, graph, …) a library that both the KTW dashboard and Maity build on, in Maity's look, so a KTW update flows through to Maity.
This card is the design only, no code yet. Deliverable: a written proposal, reported with --no-code, covering:
- the lib boundary: which parts of
dashboard/ktw_dashboard/web/(app.js, lib.js) become the library, and what stays dashboard-only; - distribution: how Maity's web UI consumes it (npm package, vendored file, served from the export, …) and how versions are pinned. The dashboard today is plain JS, no build, no CDN; say what changes if that holds;
- theming: how Maity's look is applied without forking (CSS variables/tokens, …);
- constraints: the dashboard stays read-only and stores nothing (context/dashboard.md); release order linter → dashboard;
- the migration path in small PRs, each one shippable;
- the rejected alternatives and why.
Read context/dashboard.md first. Work in a keep-the-why clone of your own. Do not touch maity yet: the maity side is A's area and gets its own card once the design is agreed. Oliver decides on the proposal before anything is built.