peter
a41e8dcfa5
Design issue capturing the request to let users customize document-artifact colors and switch between theme variants, instead of everyone getting one forced theme. Notes the two separable pieces (structure/skin split via CSS variables as a prerequisite — the themes currently hardcode colors — and a switching mechanism), the preset-vs-raw-CSS security tradeoff, dark-mode interaction, and deck as the concrete trigger. References the existing planning docs on theme variants/palettes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 007-handover-to-llm-test-2026-09-02.md | ||
| 013-handover-to-llm-test-round-2.md | ||
| 014-stored-xss-in-rendered-text-artifacts.md | ||
| 015-deeply-nested-json-recursionerror-500.md | ||
| 016-csv-ragged-rows-silent-data-loss-in-render.md | ||
| 017-customizable-document-theme-variants.md | ||
| README.md | ||
Issues
One file per issue: NNN-short-slug.md, numbered sequentially. Each file
has a title, status (Open / Fixed / By design), description, and resolution
once closed. Numbering keeps climbing — archived numbers are never reused.
Resolved issues are moved to _archive_/ to keep this directory focused on
what's open. That subdirectory is gitignored (it matches the repo-wide
_archive_/ rule), so archived issues stay on local disk and in git
history but are not carried in the committed tree. This directory is read
by the sibling AGENT_DAYBOOK__LLM_TEST project via its local path, so it
still sees the archived files.