Symptom

Project-family chip and row labels (Project, Camera, Journal, Task List) rendered in primary blue with TextDecoration.Underline, making them look like tappable navigation links. All other node types (Trigger, Executor, Server, Filter, DataPoint) rendered their chip labels in onSurface/onSecondaryContainer white-gray — visually jarring inconsistency.

Root cause

When the Project-family composables were written, the chip title Text was given an explicit color = MaterialTheme.colorScheme.primary and textDecoration = TextDecoration.Underline. This likely came from a design where project nodes were intended to be navigable links, but the interaction was never wired up. All other chip implementations (e.g. BackupChip, ButtonChip) either use TitledChip (which uses onSecondaryContainer) or rely on LocalContentColor inherited from NodeChipScaffold’s Surface(color = secondaryContainer). The Project family bypassed both patterns.

Fix

Removed color = MaterialTheme.colorScheme.primary and textDecoration = TextDecoration.Underline from the chip/row title Text in EditProject.kt, EditJournal.kt, EditTaskList.kt, and CameraRow.kt. The title text now inherits LocalContentColor from its parent: onSecondaryContainer inside NodeChipScaffold (chips), onSurface in list rows — matching every other node type’s chip label.

Prevention

• Chip title text should never carry an explicit color. Rely on LocalContentColor from NodeChipScaffold’s Surface or use TitledChip directly.
• TextDecoration.Underline on a non-clickable Text is a UX contract violation — only use it with a Modifier.clickable or equivalent interaction.
• The nightly UX audit (Roborazzi catalog screenshots + Kraken analysis) is the main regression detector for chip visual consistency. No unit test can assert color values without screenshot comparison.