Establish a Consistent Heartwood Visual Identity

[PSchmiedmayer]

Problem

Heartwood does not yet use one recognizable, accessible visual identity across documentation, CLI, browser, and repository assets.

Solution

• Define one canonical mark with documented source and redistribution terms.
• Produce maintained light, dark, monochrome, compact, and terminal-safe variants.
• Define shared presentation tokens that extend Zensical and Stanford Spezi without creating another component library.
• Apply the identity to documentation, CLI startup and progress, browser surfaces, and suitable repository assets.
• Preserve ASCII fallbacks, contrast, alternative text, and reduced-motion behavior.
• Add focused visual regression coverage.

Acceptance Criteria

• One documented source of truth generates or governs all variants.
• Documentation, CLI, and browser use the same identity consistently.
• Accessibility checks pass in light, dark, terminal, and reduced-motion contexts.
• Assets do not duplicate design-system controls or institutional marks.

Code of Conduct

• I agree to follow this project's Code of Conduct and Contributing Guidelines