chore(openspec): drop 9 superseded proposals + 11 stub archive files
Drop 9 batch proposals that are superseded by the boocode-lift-analysis (boocontext-audit, conductor upgrades, self-healing/verify-gate skills): add-3tier-memory, import-llm-evaluator, import-pregel-engine, plugin-platform, conductor-evolution, code-intelligence-upgrade, dev-workflow, ui-overhaul, agent-reliability. Delete 11 stub archive files (49-66B each, 'Status: Shipped. Archived.' only) that provide zero documentation value over the existing CHANGELOG.md + git tags.
This commit is contained in:
@@ -0,0 +1,45 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Nav button in sidebar
|
||||
|
||||
The sidebar (`ProjectSidebar.tsx`) SHALL include a "Token Analytics" button in the bottom-pinned section, positioned above the existing Settings button.
|
||||
|
||||
#### Scenario: Button renders above Settings
|
||||
|
||||
- **WHEN** the sidebar renders
|
||||
- **THEN** a "Token Analytics" button is visible in the bottom-pinned div
|
||||
- **AND** it is positioned above the "Settings" button
|
||||
|
||||
#### Scenario: Button navigates to /analytics
|
||||
|
||||
- **WHEN** the user clicks "Token Analytics"
|
||||
- **THEN** the app navigates to `/analytics`
|
||||
- **AND** the sidebar drawer closes on mobile
|
||||
|
||||
### Requirement: Button icon
|
||||
|
||||
The nav button SHALL use a visible icon alongside its label.
|
||||
|
||||
#### Scenario: Icon renders
|
||||
|
||||
- **WHEN** the sidebar renders
|
||||
- **THEN** the "Token Analytics" button displays an icon (use `BarChart3` or similar from lucide-react) and the label "Token Analytics"
|
||||
|
||||
### Requirement: Active route highlight
|
||||
|
||||
The nav button SHALL use the same active/hover styling as the Settings button.
|
||||
|
||||
#### Scenario: Active state
|
||||
|
||||
- **WHEN** the user is on the `/analytics` route
|
||||
- **THEN** the "Token Analytics" button has the same active background styling as other nav buttons
|
||||
|
||||
### Requirement: Mobile responsiveness
|
||||
|
||||
The nav button SHALL close the sidebar drawer on mobile after navigation, matching the Settings button behavior.
|
||||
|
||||
#### Scenario: Mobile navigation closes drawer
|
||||
|
||||
- **WHEN** the user is on mobile (sidebar is a slide-in drawer)
|
||||
- **AND** they click "Token Analytics"
|
||||
- **THEN** the sidebar drawer closes
|
||||
Reference in New Issue
Block a user