trm/docs
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

log: TRM design handoff imported, adoption deferred to SPA phase 3.8

Browse Source
This commit is contained in:
Julian Çuni
2026-05-02 19:10:34 +02:00
parent 67e3a4939f
commit 875327bed7
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
log.md
+8
View File
@@ -157,6 +157,14 @@ Updated [[processor-ws-contract]] §"Auth handshake" to drop the explicit "(mode
Processor Phase 1.5 is fully shipped (`c07ea0e` 1.5.4, `f4b50ca` 1.5.5, `2f2cf5c` 1.5.6) — six tasks, 178/178 unit tests, 6 integration scenarios. The cookie-mode language in the processor's planning task files (1.5.2 in particular) is left as-is — it's the historical spec the implementation landed against; the implementation itself is mode-agnostic.
## [2026-05-02] note | TRM design handoff imported (deferred to SPA Phase 3.8)
User generated a design system via claude.ai/design and dropped the handoff bundle into `trm/spa/TRM_Design_System-handoff/`. Bloomberg/F1-pit-wall aesthetic — ink-on-paper base, race-flag red `#E8412B` accent, square-edged everything, sharp printed offset shadows (no blur), mono numerics for changing values, Goldplay (real licensed font, three weights) + JetBrains Mono + Inter. Four surfaces designed: dashboard / leaderboard / mobile / marketing — SPA scope covers the first two.
Adoption deferred to SPA Phase 3.8 ("Visual brand pass") because applying it now would either delay dogfood-blocking Phase 1/2 work or land partial styling that gets reworked. The bundle is committed in-tree (`trm/spa/9e6b361`) and Phase 3's README spells out the recommended approach: retheme shadcn via CSS-variable overrides + Tailwind 4 `@theme` block, don't replace primitives. Source-of-truth files for the future implementer: `colors_and_type.css` (tokens), `chats/chat1.md` (intent), the bundle's READMEs (specs), `ui_kits/` (HTML prototypes per surface).
No wiki updates yet — design system isn't part of the architectural model and the surface-level styling isn't worth a wiki entity. If/when 3.8 lands and the brand becomes a stable fixture, a brief mention in `[[react-spa]]` is the right home.
## [2026-05-02] note | trm/spa planning landed
User created `trm/spa` repo on Gitea and seeded a minimal Vite 8 + React 19 + TypeScript 6 scaffold (App.tsx returns "SPA"). Wrote the full planning structure mirroring the conventions established by `trm/processor` and `trm/directus`.