feat/tui: theme and shared chrome unification (hybrid base)

[anandh8x]

Unify zeroTheme + zeroline palette and V1 header/input for hybrid V1+timeline per design PR1. No default behavior change. Tests + snapshots pass.

Summary by CodeRabbit

• New Features

  • Added support for optimized display rendering on narrow terminals (≤80 columns).

• Style

  • Updated color palette for unified visual consistency across display themes.

• Documentation

  • Enhanced internal documentation and code comments for improved clarity and maintainability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c7ebf36b-b210-407c-ac8e-532a8a0d6670

📥 Commits

Reviewing files that changed from the base of the PR and between 58e209d and d436c08.

📒 Files selected for processing (7)

• internal/cli/zeroline.go
• internal/tui/startup.go
• internal/tui/theme.go
• internal/tui/view.go
• internal/tui/zeroline_view.go
• internal/zeroline/render.go
• internal/zeroline/theme.go

---

Walkthrough

This PR documents and enables hybrid V1+V4 visual chrome unification by adding narrow-display responsive helpers, updating the Cyan theme palette to match a unified color spec, and clarifying how V1 header/status chrome reuse across the rendering pipeline.

Changes

Hybrid V1+V4 Chrome Unification

Layer / File(s)	Summary
80-column responsive width helpers internal/tui/startup.go	Introduces eightyCol(w) to detect widths ≤80 columns and narrowFor80(w, full, collapsed) to return collapsed chrome strings in narrow mode, enabling responsive V1 chrome reuse for tight terminal widths.
Palette unification for hybrid V1+V4 colors internal/zeroline/theme.go, internal/tui/theme.go	Cyan theme palette updated to cyan/green/amber/red/dim-muted colors matching zeroTheme spec; block comments explain the V1+V4 aliasing strategy and references to hybrid design doc sections.
Chrome rendering documentation for V1 reuse internal/cli/zeroline.go, internal/tui/view.go, internal/tui/zeroline_view.go, internal/zeroline/render.go	Comments clarify that snapshot home-page, header bar, status line, and zerolineView use reusable V1 chrome for the hybrid timeline execution phase, with palette consistency notes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Gitlawb/zero#114: Earlier PR introduced the Cyan theme palette definitions that this PR updates to the unified zeroTheme color spec.

Suggested reviewers

• gnanam1990
• Vasanthdev2004

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main changes: unifying theme and shared chrome for hybrid design support, matching the core objectives across all file modifications.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch execute-plan/f8110197-pr-1-feat-tui-theme-and-shared-chrome-unification

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[anandh8x]

Deleting work per user request. This was exploratory implementation for local testing only - no PRs wanted yet.