- artifacts/tx-os/src/lib/notes-api.ts: extended NOTE_COLORS so each
entry carries an `accent` Tailwind class alongside `bg`/`ring`
(default→amber, red→red, orange→orange, yellow→yellow, green→green,
teal→teal, blue→sky, purple→purple, pink→pink, gray→slate; all *-500
for visibility in light + dark). Added a `colorAccent(id)` helper
that resolves to a literal accent-* class, falling back to the
default amber for unknown/null ids. The class strings are written
out as literals so Tailwind v4's source scanner emits all of them
into the generated CSS — no dynamic class names, no safelist needed.
- artifacts/tx-os/src/pages/notes.tsx: ChecklistView gained an optional
`noteColor?: string | null` prop and now resolves its checkbox
accent via `colorAccent(noteColor)` instead of the hard-coded
`accent-amber-500`. Updated all four call sites (NoteCard, received
list, sent list, thread dialog) to pass `note.color` / `n.color` /
`thread.color`.
- artifacts/tx-os/src/components/notes/incoming-note-popup.tsx:
PopupChecklistPreview gained the same optional `noteColor` prop and
uses `colorAccent` for the checkbox className. Call site now passes
`current.color` from the popup queue.
- Unchecked boxes still render with the neutral browser default; only
the checked accent (the filled tint) follows the note color. The
default (white/card) note keeps amber for visibility against the
neutral surface in both themes.
- Verified: `pnpm exec tsc --noEmit` is clean and the
`tests/notes-popup-on-receive.spec.mjs` regression suite (incl. the
Task #433 checklist popup case) still passes 3/3.
- Pre-existing failing `test` workflow (api-server tsc errors in
executive-meetings.ts) is unrelated and out of scope.
riyadhafraa
11439abd39