The Events page offers the same three destinations through two full navigation affordances stacked one above the other.
The numbered step strip (Capture → Map → Bind, with counts) is a clickable <ol> of buttons, and directly beneath it the Tabs list repeats the same three panels as Inspector | Mappings | Bindings, with the same counts from the same counts source. Both drive the same ?tab= query parameter through the same show(), so the page renders one control set twice under two different label vocabularies for the same three things.
This is deliberate rather than a regression — counts.ts documents it ('The three-step strip and the tab chips both show one number per step'), and EventsPage.vue wires both to the one handler. It is filed because the result reads as a duplicated wizard, and because the two vocabularies (Capture/Map/Bind vs Inspector/Mappings/Bindings) name the same three panels differently in the same view.
Deciding which one survives is a design call, not a code one: dropping the strip makes the chain the tab list and loses the numbered-flow framing; dropping the tab list leaves the strip as the only control and makes the current tab legible only through the strip's own highlight.
Imported from beads archie-core-xt6b · GitHub #1240 · type bug · priority P3 · created 2026-10-05
The Events page offers the same three destinations through two full navigation affordances stacked one above the other.
The numbered step strip (`Capture → Map → Bind`, with counts) is a clickable `<ol>` of buttons, and directly beneath it the `Tabs` list repeats the same three panels as `Inspector | Mappings | Bindings`, with the same counts from the same `counts` source. Both drive the same `?tab=` query parameter through the same `show()`, so the page renders one control set twice under two different label vocabularies for the same three things.
This is deliberate rather than a regression — `counts.ts` documents it ('The three-step strip and the tab chips both show one number per step'), and `EventsPage.vue` wires both to the one handler. It is filed because the result reads as a duplicated wizard, and because the two vocabularies (Capture/Map/Bind vs Inspector/Mappings/Bindings) name the same three panels differently in the same view.
Deciding which one survives is a design call, not a code one: dropping the strip makes the chain the tab list and loses the numbered-flow framing; dropping the tab list leaves the strip as the only control and makes the current tab legible only through the strip's own highlight.
---
_Imported from beads `archie-core-xt6b` · GitHub #1240 · type bug · priority P3 · created 2026-10-05_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The Events page offers the same three destinations through two full navigation affordances stacked one above the other.
The numbered step strip (
Capture → Map → Bind, with counts) is a clickable<ol>of buttons, and directly beneath it theTabslist repeats the same three panels asInspector | Mappings | Bindings, with the same counts from the samecountssource. Both drive the same?tab=query parameter through the sameshow(), so the page renders one control set twice under two different label vocabularies for the same three things.This is deliberate rather than a regression —
counts.tsdocuments it ('The three-step strip and the tab chips both show one number per step'), andEventsPage.vuewires both to the one handler. It is filed because the result reads as a duplicated wizard, and because the two vocabularies (Capture/Map/Bind vs Inspector/Mappings/Bindings) name the same three panels differently in the same view.Deciding which one survives is a design call, not a code one: dropping the strip makes the chain the tab list and loses the numbered-flow framing; dropping the tab list leaves the strip as the only control and makes the current tab legible only through the strip's own highlight.
Imported from beads
archie-core-xt6b· GitHub #1240 · type bug · priority P3 · created 2026-10-05