Repository navigation
Two-surface drilldown & stacked-bar UX #15
Description
Question
Decide the overlay behavior for the two-surface taxonomy. Today BudgetOverlay (src/report-view.ts) has modes sections / drilldown / tools / skill-toggle / trace, and the stacked bar + legend iterate the flat parsed.sections. The top-level table will now show two rows (Combined System Prompt, Combined Tool Definitions), each drilling into contributor rows, some of which drill further (files, skills, tools).
Raise fidelity with /prototype — a rough TUI stub or ASCII mock of:
- The top-level table with 2 surfaces and the stacked-bar / legend treatment (2 segments, or a contributor-level breakdown within each surface?).
- 2-level drilldown: Surface → Contributor → Item (file / skill / tool). How do the existing
toolsandskill-togglemodes fold into a uniform nested drilldown? - Where Inactive Available Tools lives (collapsed counterfactual group, today in the tools view) and how Tool Envelope Overhead renders (leaf).
- Keyboard hints per level.
Decide the shape; do not implement the real overlay.
Output
A prototype artifact (linked) and a decision on the drilldown-mode structure, stacked-bar treatment, and how tools / skill-toggle integrate. Blocked by the data-model ticket.
Activity
Whamp commentedon Jul 9, 2026
Resolution
Prototype artifact: https://gist.github.com/Whamp/21a11f1b18bc9bb68ede159af1cff97d
Decision: use Variant A — Surface-first overview, scoped contributor bars.
toolsandskill-togglebehavior should become row capabilities inside that nested model rather than separate navigation worlds.eto view schema JSON.This resolves the stacked-bar treatment fog: top-level stays surface-only; contributor detail is scoped to surface drilldown.