Sidebar Generation

Requirement: generateSidebarFromSpec returns grouped sidebar structure

generateSidebarFromSpec() SHALL return SidebarItem[] where each item is a tag group containing child operation items, replacing the previous flat list of operation links.

Return value is an array of group objects

• WHEN generateSidebarFromSpec({ spec: './petstore.yaml', outDir: 'api' }) is called
• THEN the return value is an array where each element has { text: string, collapsed: boolean, items: SidebarItem[] }

Child items link to individual endpoint pages

• WHEN an endpoint GET /pets is tagged pets
• THEN the pets group's items array contains { text: 'GET /pets', link: '/api/pets/get-pets' }

Requirement: Index page includes summary table

generateIndexMarkdown() SHALL include a Markdown table with columns Method, Path, and Summary listing all operations, sorted by tag then path.

Summary table present in index output

• WHEN generateIndexMarkdown() is called for a spec with multiple endpoints
• THEN the output contains a Markdown table with | Method | Path | Summary | header row

Table rows sorted by tag then path

• WHEN a spec has endpoints across multiple tags
• THEN table rows are grouped by tag (alphabetically) and within each tag sorted by path alphabetically

Requirement: Sidebar text for spec and change items uses humanized labels

The text field of sidebar items for capability specs and changes MUST use the humanized label (Title Case) derived from the kebab-case name, not the raw kebab-case name.

Spec sidebar item uses Title Case

• WHEN generateOpenSpecSidebar() is called and a spec named nav-integration exists
• THEN the sidebar item has text: 'Nav Integration'

Change sidebar item uses Title Case

• WHEN generateOpenSpecSidebar() is called and a change named readable-sidebar-labels exists
• THEN the change group has text: 'Readable Sidebar Labels'