Evaluate Liquid Glass visual pass separately

[shiny-code-bot]

Objective

Evaluate Liquid Glass, color, material, and visual backports for macOS 26-27 and visionOS/iOS after the companion mechanics are stable.

Finish Line

A separate visual pass decides what, if anything, should change mechanically or visually on macOS and companion clients, with screenshots and a reversible PR that does not carry platform extraction or sync changes.

Current Status

The product direction is to leave this decision for last. The user wants to avoid changing macOS UI and then struggling to revert because visual changes were mixed into mechanical companion work.

Scope

• Evaluate shared design tokens, colors, materials, density, and platform-specific affordances after extraction.
• Consider whether any Liquid Glass mechanics should flow back to macOS.
• Keep visual changes isolated from core, sync, and target scaffolding.
• Produce screenshot evidence across affected platforms before acceptance.

Acceptance Criteria

• Mechanical shared UI/sync/client support has already landed or is reviewable separately.
• Visual changes are confined to theme/layout/style layers where possible.
• macOS changes are reversible without removing companion support.
• Screenshots or native presentation evidence cover macOS and companion surfaces touched by the visual pass.
• The pass explicitly records accepted and rejected visual directions.

Next Action

Keep deferred until companion mechanics are stable enough to judge visuals on real surfaces.

Relationships

Parent: #163