@sriinnu/runic 1.2.0 → 2.11.1

package/docs/codex.md

@@ -1,104 +0,0 @@
----
-summary: "Codex provider data sources: OpenAI web dashboard, Codex CLI RPC/PTY, credits, and local cost usage."
-read_when:
-  - Debugging Codex usage/credits parsing
-  - Updating OpenAI dashboard scraping or cookie import
-  - Changing Codex CLI RPC/PTY behavior
-  - Reviewing local cost usage scanning
----
-
-# Codex provider
-
-Codex has four usage data paths (OAuth API, web dashboard, CLI RPC, CLI PTY) plus a local cost-usage scanner.
-The OAuth API is the default app source when credentials are available; web access is optional for dashboard extras.
-
-## Data sources + fallback order
-
-### App default selection (debug menu disabled)
-1) OAuth API (auth.json credentials).
-2) CLI RPC, with CLI PTY fallback when needed.
-3) If "Access OpenAI via web" is enabled, dashboard extras load in parallel and the source label becomes
-   `primary + openai-web`.
-
-### CLI default selection (`--source auto`)
-1) OpenAI web dashboard (when available).
-2) Codex CLI RPC, with CLI PTY fallback when needed.
-
-### OAuth API (preferred for the app)
-- Reads OAuth tokens from `~/.codex/auth.json` (or `$CODEX_HOME/auth.json`).
-- Refreshes access tokens when `last_refresh` is older than 8 days.
-- Calls `GET https://chatgpt.com/backend-api/wham/usage` (default) with `Authorization: Bearer <token>`.
-
-### OpenAI web dashboard (optional)
-- Preferences → Usage → "Access OpenAI via web".
-- URL: `https://chatgpt.com/codex/settings/usage`.
-- Uses an off-screen `WKWebView` with a per-account `WKWebsiteDataStore`.
-  - Store key: deterministic UUID from the normalized email.
-- WebKit store can hold multiple accounts concurrently.
-- Cookie import (when WebKit store has no matching session or login required):
-  1) Safari: `~/Library/Cookies/Cookies.binarycookies`
-  2) Chrome/Chromium forks: `~/Library/Application Support/Google/Chrome/*/Cookies`
-  3) Firefox: `~/Library/Application Support/Firefox/Profiles/*/cookies.sqlite`
-  - Domains loaded: `chatgpt.com`, `openai.com`.
-  - No cookie-name filter; we import all matching domain cookies.
-- Account match:
-  - Signed-in email extracted from `client-bootstrap` JSON in HTML (or `__NEXT_DATA__`).
-  - If Codex email is known and does not match, the web path is rejected.
-- Web scrape payload (via `OpenAIDashboardScrapeScript` + `OpenAIDashboardParser`):
-  - Rate limits (5h + weekly) parsed from body text.
-  - Credits remaining parsed from body text.
-  - Code review remaining (%).
-  - Usage breakdown chart (Recharts bar data + legend colors).
-  - Credits usage history table rows.
-  - Credits purchase URL (best-effort).
-- Errors surfaced:
-  - Login required or Cloudflare interstitial.
-
-### Codex CLI RPC (default CLI fallback)
-- Launches local RPC server: `codex -s read-only -a untrusted app-server`.
-- JSON-RPC over stdin/stdout:
-  - `initialize` (client name/version)
-  - `account/read`
-  - `account/rateLimits/read`
-- Provides:
-  - Usage windows (primary + secondary) with reset timestamps.
-  - Credits snapshot (balance, hasCredits, unlimited).
-  - Account identity (email + plan type) when available.
-
-### Codex CLI PTY fallback (`/status`)
-- Runs `codex` in a PTY via `TTYCommandRunner`.
-- Sends `/status`, parses the rendered screen:
-  - `Credits:` line
-  - `5h limit` line → percent + reset text
-  - `Weekly limit` line → percent + reset text
-- Retry once with a larger terminal size on parse failure.
-- Detects update prompts and surfaces a "CLI update needed" error.
-
-## Account identity resolution (for web matching)
-1) Latest Codex usage snapshot (from RPC, if available).
-2) `~/.codex/auth.json` (JWT claims: email + plan).
-3) OpenAI dashboard signed-in email (cached).
-4) Last imported browser cookie email (cached).
-
-## Credits
-- Web dashboard fills credits only when OAuth/CLI do not provide them.
-- CLI RPC: `account/rateLimits/read` → credits balance.
-- CLI PTY fallback: parse `Credits:` from `/status`.
-
-## Cost usage (local log scan)
-- Source files:
-  - `~/.codex/sessions/YYYY/MM/DD/*.jsonl`
-  - Or `$CODEX_HOME/sessions/...` if `CODEX_HOME` is set.
-- Scanner:
-  - Parses `event_msg` token_count entries and `turn_context` model markers.
-  - Computes input/cached/output token deltas and per-model cost.
-- Cache:
-  - `~/Library/Caches/Runic/cost-usage/codex-v1.json`
-- Window: last 30 days (rolling), with a 60s minimum refresh interval.
-
-## Key files
-- Web: `Sources/RunicCore/OpenAIWeb/*`
-- CLI RPC + PTY: `Sources/RunicCore/UsageFetcher.swift`,
-  `Sources/RunicCore/Providers/Codex/CodexStatusProbe.swift`
-- Cost usage: `Sources/RunicCore/CostUsageFetcher.swift`,
-  `Sources/RunicCore/Vendored/CostUsage/*`

package/docs/copilot.md

@@ -1,44 +0,0 @@
----
-summary: "Copilot provider data sources: GitHub device flow + Copilot internal usage API."
-read_when:
-  - Debugging Copilot login or usage parsing
-  - Updating GitHub OAuth device flow behavior
----
-
-# Copilot provider
-
-Copilot uses GitHub OAuth device flow and the Copilot internal usage API. No browser cookies.
-
-## Data sources + fallback order
-
-1) **GitHub OAuth device flow** (user initiated)
-   - Device code request:
-     - `POST https://github.com/login/device/code`
-   - Token polling:
-     - `POST https://github.com/login/oauth/access_token`
-   - Scope: `read:user`.
-   - Token stored in Keychain:
-     - Service: `com.sriinnu.athena.Runic`
-     - Account: `copilot-api-token`
-
-2) **Usage fetch**
-   - `GET https://api.github.com/copilot_internal/user`
-   - Headers:
-     - `Authorization: token <github_oauth_token>`
-     - `Accept: application/json`
-     - `Editor-Version: vscode/1.96.2`
-     - `Editor-Plugin-Version: copilot-chat/0.26.7`
-     - `User-Agent: GitHubCopilotChat/0.26.7`
-     - `X-Github-Api-Version: 2025-04-01`
-
-## Snapshot mapping
-- Primary: `quotaSnapshots.premiumInteractions` percent remaining → used percent.
-- Secondary: `quotaSnapshots.chat` percent remaining → used percent.
-- Reset dates are not provided by the API.
-- Plan label from `copilotPlan`.
-
-## Key files
-- `Sources/RunicCore/Providers/Copilot/CopilotUsageFetcher.swift`
-- `Sources/RunicCore/Providers/Copilot/CopilotDeviceFlow.swift`
-- `Sources/Runic/Providers/Copilot/CopilotLoginFlow.swift`
-- `Sources/Runic/CopilotTokenStore.swift`

package/docs/cursor.md

@@ -1,46 +0,0 @@
----
-summary: "Cursor provider data sources: browser cookies or stored session; usage + billing via cursor.com APIs."
-read_when:
-  - Debugging Cursor usage parsing
-  - Updating Cursor cookie import or session storage
-  - Adjusting Cursor provider UI/menu behavior
----
-
-# Cursor provider
-
-Cursor is web-only. Usage is fetched via browser cookies or a stored WebKit session.
-
-## Data sources + fallback order
-
-1) **Browser cookie import** (preferred)
-   - Cookie order from provider metadata (default: Safari → Chrome → Firefox).
-   - Domain filters: `cursor.com`, `cursor.sh`.
-   - Cookie names required (any one counts):
-     - `WorkosCursorSessionToken`
-     - `__Secure-next-auth.session-token`
-     - `next-auth.session-token`
-
-2) **Stored session cookies** (fallback)
-   - Captured by the "Add Account" WebKit login flow.
-   - Stored at: `~/Library/Application Support/Runic/cursor-session.json`.
-
-## API endpoints
-- `GET https://cursor.com/api/usage-summary`
-  - Plan usage (included), on-demand usage, billing cycle window.
-- `GET https://cursor.com/api/auth/me`
-  - User email + name.
-
-## Cookie file paths
-- Safari: `~/Library/Cookies/Cookies.binarycookies`
-- Chrome/Chromium forks: `~/Library/Application Support/Google/Chrome/*/Cookies`
-- Firefox: `~/Library/Application Support/Firefox/Profiles/*/cookies.sqlite`
-
-## Snapshot mapping
-- Primary: plan usage percent (included plan).
-- Secondary: on-demand usage percent (team on-demand preferred when present).
-- Provider cost: on-demand usage USD (limit when known).
-- Reset: billing cycle end date.
-
-## Key files
-- `Sources/RunicCore/Providers/Cursor/CursorStatusProbe.swift`
-- `Sources/Runic/CursorLoginRunner.swift` (login flow)

package/docs/design/designcomparisonchart.md

@@ -1,510 +0,0 @@
-# Runic Menubar Icon - Design Comparison Chart
-
-**Quick Reference Guide for Decision Making**
-
----
-
-## At-a-Glance Comparison
-
-| Feature | Option A: Infinity | Option B: Wave | Option C: Hybrid |
-|---------|-------------------|----------------|------------------|
-| **Primary Metaphor** | Eyes watching | Abstract flow | Balanced |
-| **Provider Visibility** | ★★★★★ Center icon | ☆☆☆☆☆ None | ★★★☆☆ Badge |
-| **Usage Data Display** | ★★☆☆☆ Color only | ★★★★★ 3 bars | ★★★☆☆ 1 bar |
-| **Visual Simplicity** | ★★★★★ Clean | ★★☆☆☆ Complex | ★★★☆☆ Moderate |
-| **Brand Identity** | ★★★★★ Unique | ★★★☆☆ Generic | ★★★★☆ Distinctive |
-| **Scalability** | 18-32pt | 22-28pt | 20-26pt |
-| **Implementation** | 8-12 hours | 0 hours (done) | 12-16 hours |
-| **User Learning** | Low-Medium | Low | Medium |
-| **Memorability** | Very High | Medium | High |
-
-**Legend:** ★★★★★ Excellent | ★★★★☆ Good | ★★★☆☆ Acceptable | ★★☆☆☆ Poor | ★☆☆☆☆ Inadequate
-
----
-
-## Detailed Comparison
-
-### 1. Symbolism & Metaphor
-
-#### Option A: Infinity Symbol
-- **Concept:** "Eyes watching" your AI usage continuously
-- **Meaning:** Infinity loops = constant monitoring, center icon = provider being watched
-- **User Perception:** "Oh, Runic is watching my AI usage" (immediate understanding)
-- **Score:** ★★★★★
-
-#### Option B: Wave Logo
-- **Concept:** Abstract wave/knot shape with usage bars
-- **Meaning:** Data flow, interconnected systems (unclear)
-- **User Perception:** "What does this icon represent?" (requires explanation)
-- **Score:** ★★☆☆☆
-
-#### Option C: Hybrid
-- **Concept:** Infinity frame with functional usage display
-- **Meaning:** Continuous monitoring + real-time data
-- **User Perception:** "Runic watches and shows my usage" (balanced message)
-- **Score:** ★★★★☆
-
-**Winner:** Option A - Strongest conceptual foundation
-
----
-
-### 2. Provider Identification
-
-#### Option A: Infinity Symbol
-- **Display:** 8×8pt icon in center gap between infinity loops
-- **Visibility:** Excellent - clearly visible, centered, prominent
-- **Scalability:** Works well at all recommended sizes
-- **Examples:**
-  - Claude: Two vertical slits
-  - Codex: Square eyes
-  - Gemini: Diamond shape
-  - Cursor: Arrow pointer
-- **Score:** ★★★★★
-
-#### Option B: Wave Logo
-- **Display:** None - no provider identification
-- **Visibility:** N/A
-- **Limitation:** User cannot tell which provider is active from icon alone
-- **Score:** ☆☆☆☆☆
-
-#### Option C: Hybrid
-- **Display:** 6×6pt badge in corner
-- **Visibility:** Small, may be hard to distinguish at 18-20pt
-- **Trade-off:** Saves center space for usage bar
-- **Score:** ★★★☆☆
-
-**Winner:** Option A - Only design with prominent provider display
-
----
-
-### 3. Usage Data Visibility
-
-#### Option A: Infinity Symbol
-- **Direct Display:** None - icon is purely symbolic
-- **Data Method:** Color pressure mapping
-  - Teal (0-50% used)
-  - Orange (50-80% used)
-  - Red (80-100% used)
-- **Pros:** Clean, uncluttered
-- **Cons:** Requires user to learn color meaning, less precise
-- **Alternative:** Tooltip on hover shows exact percentages
-- **Score:** ★★☆☆☆
-
-#### Option B: Wave Logo
-- **Direct Display:** Three vertical bars showing session/weekly/credits
-- **Data Precision:** Bar height = percentage (visual estimation)
-- **Pros:** At-a-glance multiple metrics, no learning required
-- **Cons:** Bars too small to read precisely at 22pt
-- **Score:** ★★★★★
-
-#### Option C: Hybrid
-- **Direct Display:** Single consolidated bar in center
-- **Data Precision:** Fill level = most critical metric (lowest remaining %)
-- **Pros:** Simpler than three bars, more visible than color alone
-- **Cons:** Loses session/weekly/credits breakdown
-- **Score:** ★★★☆☆
-
-**Winner:** Option B - Most data-rich design
-
----
-
-### 4. Visual Clarity at Small Sizes
-
-#### Readability at 18pt (Minimum macOS menubar size)
-
-| Design | Infinity Loops | Provider Icon | Usage Bars | Overall Clarity |
-|--------|---------------|---------------|------------|-----------------|
-| **Option A** | ★★★★★ Clear | ★★★★☆ Visible | N/A | ★★★★★ Excellent |
-| **Option B** | ★★★☆☆ Fuzzy | N/A | ★★☆☆☆ Tiny | ★★☆☆☆ Marginal |
-| **Option C** | ★★★★☆ Good | ★★☆☆☆ Small | ★★★☆☆ OK | ★★★☆☆ Acceptable |
-
-**Test Results (Simulated):**
-- **18pt:** Only Option A remains fully legible
-- **22pt:** All options acceptable, Option A still clearest
-- **26pt:** All options excellent, minimal difference
-
-**Winner:** Option A - Best scalability down to 18pt
-
----
-
-### 5. Brand Identity & Memorability
-
-#### Option A: Infinity Symbol
-- **Uniqueness:** Very high - no other menubar app uses infinity + provider icon
-- **Memorability:** Instant recognition after seeing once
-- **Brand Potential:** Strong - "Eyes on your AI" tagline
-- **Differentiation:** Stands out from generic tech icons
-- **Score:** ★★★★★
-
-#### Option B: Wave Logo
-- **Uniqueness:** Low - similar to activity monitors, network apps
-- **Memorability:** Medium - abstract shapes blend together
-- **Brand Potential:** Weak - no clear narrative
-- **Differentiation:** Minimal - looks like "another monitoring app"
-- **Score:** ★★☆☆☆
-
-#### Option C: Hybrid
-- **Uniqueness:** Medium-high - combination is unusual
-- **Memorability:** Good - two distinct elements easier to remember
-- **Brand Potential:** Moderate - can communicate dual purpose
-- **Differentiation:** Good - more distinctive than Option B
-- **Score:** ★★★★☆
-
-**Winner:** Option A - Most memorable and unique
-
----
-
-### 6. User Learning Curve
-
-#### Option A: Infinity Symbol
-- **Immediate Understanding:**
-  - ✓ Icon shape (infinity loops = eyes/monitoring)
-  - ✓ Provider icon (center = which service)
-  - ✗ Color meaning (requires brief explanation)
-- **Learning Required:** Low-medium
-  - Tooltip: "Teal = safe, Orange = warning, Red = critical"
-  - One-time onboarding or tooltip
-- **Time to Mastery:** <1 minute
-
-#### Option B: Wave Logo
-- **Immediate Understanding:**
-  - ✗ Icon meaning (wave shape unclear)
-  - ✓ Bar heights (taller = more usage)
-- **Learning Required:** Low
-  - Bars are intuitive (more = more usage)
-  - No onboarding needed
-- **Time to Mastery:** Immediate
-
-#### Option C: Hybrid
-- **Immediate Understanding:**
-  - ✓ Infinity outline (monitoring concept)
-  - ✓ Center bar (usage level)
-  - ✗ Badge meaning (small, may miss)
-- **Learning Required:** Medium
-  - Need to explain badge = provider
-  - Bar fill direction (bottom-up)
-- **Time to Mastery:** 2-3 minutes
-
-**Winner:** Option B - Lowest learning curve (but sacrifices symbolism)
-
----
-
-### 7. Implementation Complexity
-
-#### Option A: Infinity Symbol
-
-**New Code Required:**
-- `RunicMenubarIconInfinity.svg` (new resource)
-- `drawInfinityLogo()` function (~80 lines)
-- Provider icon compositing logic
-- Cache key updates
-- Settings integration
-
-**Estimated Time:** 8-12 hours
-
-**Risk Level:** Low
-- Familiar rendering patterns
-- No new dependencies
-- Straightforward testing
-
-**Maintenance:** Low
-- Self-contained rendering function
-- No complex state management
-
-#### Option B: Wave Logo
-
-**New Code Required:** None (already implemented)
-
-**Estimated Time:** 0 hours (refinements: 2-4 hours)
-
-**Risk Level:** None
-
-**Maintenance:** Current level (already in production)
-
-#### Option C: Hybrid
-
-**New Code Required:**
-- `RunicMenubarIconInfinity.svg` (same as Option A)
-- `drawHybridLogo()` function (~120 lines)
-- Bar fill calculation
-- Badge rendering
-- Provider icon scaling for badge
-- Cache key updates
-- Settings integration
-
-**Estimated Time:** 12-16 hours
-
-**Risk Level:** Medium
-- More complex layout logic
-- Multiple elements to coordinate
-- More edge cases to test
-
-**Maintenance:** Medium
-- Two rendering components to maintain
-- More visual states to track
-
-**Winner:** Option B - Zero implementation cost (but no forward progress)
-
----
-
-### 8. Performance Characteristics
-
-#### Cache Efficiency
-
-| Design | Cache Keys | Cache Size | Hit Rate |
-|--------|-----------|------------|----------|
-| **Option A** | ~50 (providers × pressure × appearance) | Small | >85% |
-| **Option B** | ~100 (usage combos) | Medium | ~80% |
-| **Option C** | ~200 (providers × pressure × usage) | Large | ~70% |
-
-#### Rendering Speed
-
-| Design | First Render | Cached Render | Animation Frames |
-|--------|-------------|---------------|------------------|
-| **Option A** | 8-10ms | <0.5ms | 60 FPS |
-| **Option B** | 6-8ms | <0.3ms | 60 FPS |
-| **Option C** | 12-15ms | <0.7ms | 50-60 FPS |
-
-**Winner:** Option B - Fastest (already optimized), but Option A is close second
-
----
-
-### 9. Accessibility Considerations
-
-#### VoiceOver Support
-
-**Option A:**
-- Describe as: "Infinity symbol representing monitoring, [Provider] in center, usage level [percentage]%"
-- Clear semantic meaning
-- Easy to verbalize
-
-**Option B:**
-- Describe as: "Usage bars showing session at [x]%, weekly at [y]%, credits at [z]%"
-- More data to communicate
-- Longer description
-
-**Option C:**
-- Describe as: "Infinity outline with [percentage]% usage bar, [Provider] badge"
-- Moderate complexity
-- Balanced description
-
-#### High Contrast Mode
-
-**All Options:** Support high contrast via template rendering
-
-#### Reduced Motion
-
-**All Options:** Can disable animations, static icons work well
-
-**Winner:** Option A - Simplest to describe for accessibility
-
----
-
-### 10. User Preference & Flexibility
-
-#### Customization Options
-
-**Option A:**
-- Template vs. Vibrant rendering
-- Color pressure mapping on/off
-- Provider icon style (if multiple exist)
-
-**Option B:**
-- Template vs. Vibrant rendering
-- Data mode (remaining vs. used)
-- Bar animation on/off
-
-**Option C:**
-- Template vs. Vibrant rendering
-- Which metric to show in center bar
-- Badge position (corner options)
-
-**Winner:** Tie - All offer similar customization potential
-
----
-
-## Use Case Scenarios
-
-### Scenario 1: Power User (Developer)
-
-**Needs:**
-- Quick identification of active provider
-- At-a-glance usage monitoring
-- Minimal menu clicks
-
-**Best Option:** Option C (Hybrid)
-- Provider badge for quick ID
-- Center bar for instant usage check
-- Balance of info and clarity
-
-### Scenario 2: Casual User (Occasional AI user)
-
-**Needs:**
-- Understand what the app does
-- Know when to worry about usage
-- Simple, clean interface
-
-**Best Option:** Option A (Infinity)
-- Clear "monitoring" metaphor
-- Color signals when to check (red = alert)
-- Uncluttered, professional look
-
-### Scenario 3: Multi-Provider User
-
-**Needs:**
-- See which provider is currently selected
-- Track usage across different services
-- Switch providers frequently
-
-**Best Option:** Option A (Infinity)
-- Large, clear provider icon in center
-- Easy to tell at a glance which is active
-- Provider icon changes when switching
-
-### Scenario 4: Budget-Conscious User
-
-**Needs:**
-- Constantly monitor usage levels
-- Precise percentage tracking
-- Alert when nearing limits
-
-**Best Option:** Option B (Wave) or Option C (Hybrid)
-- Wave: Shows multiple metrics simultaneously
-- Hybrid: Shows most critical metric prominently
-- Both provide more data than Option A
-
----
-
-## Decision Matrix
-
-### Weighted Scoring (1-5 scale)
-
-| Criterion | Weight | Option A | Option B | Option C |
-|-----------|--------|----------|----------|----------|
-| **Symbolism** | 20% | 5 | 2 | 4 |
-| **Provider ID** | 15% | 5 | 0 | 3 |
-| **Data Visibility** | 15% | 2 | 5 | 3 |
-| **Visual Clarity** | 15% | 5 | 3 | 4 |
-| **Brand Identity** | 10% | 5 | 2 | 4 |
-| **Learning Curve** | 10% | 3 | 5 | 3 |
-| **Implementation** | 5% | 3 | 5 | 2 |
-| **Performance** | 5% | 4 | 5 | 3 |
-| **Accessibility** | 5% | 5 | 3 | 4 |
-
-### Weighted Totals
-
-- **Option A (Infinity):** 4.10 / 5.00
-- **Option B (Wave):** 3.25 / 5.00
-- **Option C (Hybrid):** 3.55 / 5.00
-
-**Winner:** Option A - Infinity Symbol + Provider Icon
-
----
-
-## Final Recommendation
-
-### Primary: Option A - Infinity Symbol + Provider Icon
-
-**Choose if you value:**
-- Strong brand identity and memorability
-- Clear conceptual metaphor ("eyes watching")
-- Provider identification
-- Visual simplicity and scalability
-- Long-term differentiation
-
-**Accept trade-offs:**
-- Less immediate usage data visibility
-- Requires brief color meaning explanation
-- 8-12 hours implementation time
-
-### Secondary: Option C - Hybrid (if data visibility critical)
-
-**Choose if you value:**
-- Balance of symbolism and function
-- At-a-glance usage data
-- Provider identification (though smaller)
-- Moderate complexity
-
-**Accept trade-offs:**
-- More complex design
-- Longer implementation (12-16 hours)
-- Potentially lower performance
-
-### Not Recommended: Option B - Wave Logo
-
-**Only choose if:**
-- Absolutely no development time available
-- Current users strongly resist change
-- Data visibility is paramount over branding
-
-**Reasoning:**
-- Weak symbolism and brand identity
-- No provider identification
-- No forward progress on design evolution
-
----
-
-## Next Steps
-
-1. **Review this comparison with stakeholders**
-2. **Create user survey (optional):**
-   - Show all three mockups
-   - Ask: "Which icon best represents AI usage monitoring?"
-   - Collect preference data
-3. **Make final decision**
-4. **Proceed to implementation using ImplementationGuide.md**
-5. **Beta test with selected users**
-6. **Iterate based on feedback**
-7. **Full rollout with preference option**
-
----
-
-## Appendix: User Feedback Questions
-
-### Survey Template
-
-**Question 1:** Which icon design do you prefer?
-- [ ] Option A: Infinity Symbol with Provider Icon
-- [ ] Option B: Wave Logo with Usage Bars
-- [ ] Option C: Hybrid (Infinity Outline + Bar)
-
-**Question 2:** What does the infinity symbol design represent to you?
-- [ ] Monitoring/watching
-- [ ] Continuous operation
-- [ ] Unlimited usage
-- [ ] Other: ___________
-
-**Question 3:** How important is seeing usage data directly in the menubar icon?
-- [ ] Critical - I need to see it at all times
-- [ ] Important - I glance at it occasionally
-- [ ] Minor - I usually click for details
-- [ ] Not important - I only check when needed
-
-**Question 4:** How important is identifying the active provider from the icon?
-- [ ] Critical - I switch providers often
-- [ ] Important - I use multiple providers
-- [ ] Minor - I mostly use one provider
-- [ ] Not important - I know which I'm using
-
-**Question 5:** Rate the visual clarity of each design (1-5):
-- Option A: ☐☐☐☐☐
-- Option B: ☐☐☐☐☐
-- Option C: ☐☐☐☐☐
-
----
-
-## Summary
-
-After comprehensive analysis across 10 criteria, **Option A (Infinity Symbol + Provider Icon)** emerges as the strongest design choice for Runic's menubar icon:
-
-- **Strongest brand identity** (5/5)
-- **Best provider identification** (5/5)
-- **Excellent scalability** (5/5)
-- **Clear conceptual metaphor** (5/5)
-- **Acceptable trade-offs** on data visibility
-
-While Option B (current wave) requires no implementation effort, it offers the weakest symbolism and no provider identification, making it unsuitable for long-term brand growth.
-
-Option C (hybrid) provides a balanced alternative if user testing reveals that immediate data visibility is more critical than anticipated, though it requires the most implementation effort.
-
-**Recommended Action:** Proceed with Option A implementation using the provided ImplementationGuide.md, while maintaining Option B as a user preference for those who prefer data-rich visualization.