From 4bb8f1229db3b99ad343ef211145627452445b3f Mon Sep 17 00:00:00 2001 From: ZTatman Date: Wed, 10 Jun 2026 17:00:20 -0400 Subject: [PATCH] docs(agents): record session architecture decisions Document the Forgejo service layer, tokens.py credential boundary, the app-settings dependency trio, the main.py composition-root split, the debug-gated dev tooling, and the FastAPI TYPE_CHECKING-forward-ref + Depends gotcha that turned a dependency into a query param. --- agents.md | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/agents.md b/agents.md index dc64b83..2089ba3 100644 --- a/agents.md +++ b/agents.md @@ -145,3 +145,57 @@ This file is the single source of truth for codebase obstacles, oddities, and th **Obstacle:** Theme switching and persisted localStorage theme state conflicted with the current Firebreak brand pass, especially on the cinematic landing page. **Solution/Workaround:** Force the root document to use the `.dark` token set and remove the theme toggle UI/scripts. **Preference:** Keep semantic dark tokens; only reintroduce theme switching after the dark Firebreak identity is stable. + +### Landing hero styles belong in tokenized CSS +**Area:** web/app/templates/index.html, web/app/static/css/input.css +**Obstacle:** Inline hero gradients, shadows, and hardcoded OKLCH values made the landing page harder to tune without drifting away from the Firebreak design token system. +**Solution/Workaround:** Keep landing hero structure in `index.html`, but define overlays, logo effects, proof chips, and panel styling in `input.css` using hero-specific tokens. +**Preference:** Use semantic hero/component classes for cinematic landing styling; avoid inline `