Files
skills/docs/requirements/017-legend-toggle.md
T
Kevin Veen-BirkenbachandClaude Opus 5.5 27b376819c docs(requirements): add 015 rates time range, 016 agents controls row, 017 legend toggle
Operator request 2026-11-17: the time range slider, replay and rate unit move
into the Rates per period panel with every rate over the chosen window and a
chip of 2 to 9 metrics (015); Priority, Day/Night and Status join the agents
view row (016); an info button hides a chart legend per Home tile and per view
(017). All three are implemented after the other open skills requirements.

🎯 Fix: 95 %
💥 Break: 1 %
💸 Tokens: 100 %
⏱️ Velocity: 100 %
🛡️ Security: 100 %
🏆 Score: 94
🚦 Gate: ✅ 90/5, tokens and velocity <= 100, security 100 %

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 09:45:34 +00:00

2.9 KiB
Raw Blame History

017 - Legend Toggle

User Story

As the operator, I want to hide and show a chart's legend on its Home tile and in its view, so that a small tile shows the chart instead of its legend.

Decisions (operator-confirmed 2026-11-17; do not re-litigate)

  1. Info button: a button with the info icon (bi-info-circle) and aria-pressed shows or hides the legend; on a Home tile it sits left of the Open button, in a view next to the star. Only panels whose content holds a legend get it, among them Tasks burndown and burnup, Tokens and Hardware resources.
  2. Per tile and per view, in the hub store: each Home pin and each view keeps its own state in the hub view store, shared by every browser; the default is shown. Rejected: one global switch, a per-browser state.
  3. The chart takes the room: a hidden legend frees its space for the chart; series switched off in legend chips stay off while the chips are hidden.
  4. Timing: implemented after every other open skills requirement.

Approach

flowchart TD
    subgraph P["🧭 0 · Preparation"]
        P1["📋 Write requirement"] --> P2{"✅ Operator approves?"}
        P2 -- "✏️ corrections" --> P1
    end
    P2 -- "🤖 yes, after the other requirements" --> A1
    subgraph A["🗄️ A · State"]
        A1["🧮 View store keys for tile and view legends"] --> A2{"🧪 Unit green?"}
        A2 -- "🔴 no: fix" --> A1
    end
    A2 -- "🟢 yes" --> B1
    subgraph B["ℹ️ B · Buttons"]
        B1["🧩 Info button on tiles and views"] --> B2{"🧪 E2E green?"}
        B2 -- "🔴 no: fix" --> B1
        B2 -- "🟢 yes" --> BF{"💬 Operator feedback on screenshots?"}
        BF -- "✏️ changes" --> B1
    end
    BF -- "👍 fits" --> D1["🏁 Review, commit with operator OK, hand-over"]

Acceptance Criteria

Button

  • A DOM scan of Home and every view finds the info button exactly on the tiles and views whose content holds a .legend.
  • On a tile it is the head button left of Open; in a view it sits next to the star.
  • A click hides the legend and the chart's height grows; a second click shows it again.

State

  • The state survives a reload and shows in a second browser.
  • Hiding the legend on the Tokens tile leaves the Tokens view's legend shown, and the reverse.
  • With the IAM series switched off and the Tokens legend hidden, the chart still leaves IAM out.
  • The view store refuses an unknown panel key and a non-boolean value with a 400.

Tests

  • Unit: view store validation and defaults of the legend keys.
  • Integration: the hub keeps the legend state across a restart from its view file.
  • E2E: Chromium and Firefox at 1920, 1366 and 390: the scan, hide and show on a tile and in a view, persistence across a reload and a second browser; screenshots for the checkpoint.