1# Implementation Plan: Browser Controls UI
2
3**Branch**: `002-browser-controls-ui` | **Date**: 2025-09-09 | **Spec**: [spec.md](./spec.md)
4**Input**: Feature specification from `/home/brice/dev/projects/dumb-browser/specs/002-browser-controls-ui/spec.md`
5
6## Execution Flow (/plan command scope)
7```
81. Load feature spec from Input path
9   → If not found: ERROR "No feature spec at {path}"
102. Fill Technical Context (scan for NEEDS CLARIFICATION)
11   → Detect Project Type from context (web=frontend+backend, mobile=app+api)
12   → Set Structure Decision based on project type
133. Evaluate Constitution Check section below
14   → If violations exist: Document in Complexity Tracking
15   → If no justification possible: ERROR "Simplify approach first"
16   → Update Progress Tracking: Initial Constitution Check
174. Execute Phase 0 → research.md
18   → If NEEDS CLARIFICATION remain: ERROR "Resolve unknowns"
195. Execute Phase 1 → contracts, data-model.md, quickstart.md, agent-specific template file (e.g., `CLAUDE.md` for Claude Code, `.github/copilot-instructions.md` for GitHub Copilot, or `GEMINI.md` for Gemini CLI).
206. Re-evaluate Constitution Check section
21   → If new violations: Refactor design, return to Phase 1
22   → Update Progress Tracking: Post-Design Constitution Check
237. Plan Phase 2 → Describe task generation approach (DO NOT create tasks.md)
248. STOP - Ready for /tasks command
25```
26
27**IMPORTANT**: The /plan command STOPS at step 7. Phases 2-4 are executed by other commands:
28- Phase 2: /tasks command creates tasks.md
29- Phase 3-4: Implementation execution (manual or via tools)
30
31## Summary
32Implement keyboard and mouse navigation controls for the Wails-based browser: zoom in/out with Ctrl+/-, back/forward navigation with mouse buttons, URL copying with Ctrl+Shift+C, and dynamic window title updates. This feature enhances user experience with standard browser controls while maintaining the application's speed-first principle and single-binary architecture.
33
34## Technical Context
35**Language/Version**: Go 1.25.1  
36**Primary Dependencies**: Wails v3-alpha.28 (WebView), Cobra (CLI), Viper (config), SQLite3  
37**Storage**: SQLite3 database for history/zoom persistence  
38**Testing**: Go standard testing, manual verification with keyboard/mouse controls  
39**Target Platform**: Linux desktop (Wayland native, tiling WM compatible)
40**Project Type**: single (desktop application with embedded frontend)  
41**Performance Goals**: <500ms startup, <100MB baseline memory, <50ms history search  
42**Constraints**: Single binary, no external runtime deps, WebKit2GTK system integration  
43**Scale/Scope**: Single user desktop app, ~12 functional requirements, 5 new keyboard/mouse controls
44
45## Constitution Check
46*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
47
48**Simplicity**:
49- Projects: 1 (single desktop app with embedded frontend) ✓
50- Using framework directly? Yes (direct Wails v3 integration, no wrappers) ✓
51- Single data model? Yes (existing browser state, minimal zoom state addition) ✓
52- Avoiding patterns? Yes (direct service calls, no unnecessary abstractions) ✓
53
54**Architecture**:
55- EVERY feature as library? Yes (keyboard/mouse controls as separate service methods) ✓
56- Libraries listed: BrowserService (navigation/zoom), ConfigService (persistence)
57- CLI per library: Existing CLI structure maintained, no new commands needed ✓
58- Library docs: N/A (internal desktop app, not library distribution)
59
60**Testing (NON-NEGOTIABLE)**:
61- RED-GREEN-Refactor cycle enforced? Yes (will create failing tests first) ✓
62- Git commits show tests before implementation? Yes (test commits before feature commits) ✓
63- Order: Contract→Integration→E2E→Unit strictly followed? Yes ✓
64- Real dependencies used? Yes (real SQLite, real Wails WebView) ✓
65- Integration tests for: Keyboard event handling, zoom persistence, clipboard integration ✓
66- FORBIDDEN: Implementation before test, skipping RED phase ✓
67
68**Observability**:
69- Structured logging included? Yes (existing slog usage maintained) ✓
70- Frontend logs → backend? Yes (Wails provides unified logging) ✓
71- Error context sufficient? Yes (proper Go error handling) ✓
72
73**Versioning**:
74- Version number assigned? Using existing versioning (0.1.0 → 0.1.1) ✓
75- BUILD increments on every change? Yes (patch version bump) ✓
76- Breaking changes handled? None expected (additive feature only) ✓
77
78## Project Structure
79
80### Documentation (this feature)
81```
82specs/[###-feature]/
83├── plan.md              # This file (/plan command output)
84├── research.md          # Phase 0 output (/plan command)
85├── data-model.md        # Phase 1 output (/plan command)
86├── quickstart.md        # Phase 1 output (/plan command)
87├── contracts/           # Phase 1 output (/plan command)
88└── tasks.md             # Phase 2 output (/tasks command - NOT created by /plan)
89```
90
91### Source Code (repository root)
92```
93# Option 1: Single project (DEFAULT)
94src/
95├── models/
96├── services/
97├── cli/
98└── lib/
99
100tests/
101├── contract/
102├── integration/
103└── unit/
104
105# Option 2: Web application (when "frontend" + "backend" detected)
106backend/
107├── src/
108│   ├── models/
109│   ├── services/
110│   └── api/
111└── tests/
112
113frontend/
114├── src/
115│   ├── components/
116│   ├── pages/
117│   └── services/
118└── tests/
119
120# Option 3: Mobile + API (when "iOS/Android" detected)
121api/
122└── [same as backend above]
123
124ios/ or android/
125└── [platform-specific structure]
126```
127
128**Structure Decision**: Option 1 (Single project) - Desktop application with embedded frontend, existing structure maintained
129
130## Phase 0: Outline & Research
1311. **Extract unknowns from Technical Context** above:
132   - For each NEEDS CLARIFICATION → research task
133   - For each dependency → best practices task
134   - For each integration → patterns task
135
1362. **Generate and dispatch research agents**:
137   ```
138   For each unknown in Technical Context:
139     Task: "Research {unknown} for {feature context}"
140   For each technology choice:
141     Task: "Find best practices for {tech} in {domain}"
142   ```
143
1443. **Consolidate findings** in `research.md` using format:
145   - Decision: [what was chosen]
146   - Rationale: [why chosen]
147   - Alternatives considered: [what else evaluated]
148
149**Output**: research.md with all NEEDS CLARIFICATION resolved
150
151## Phase 1: Design & Contracts
152*Prerequisites: research.md complete*
153
1541. **Extract entities from feature spec** → `data-model.md`:
155   - Entity name, fields, relationships
156   - Validation rules from requirements
157   - State transitions if applicable
158
1592. **Generate API contracts** from functional requirements:
160   - For each user action → endpoint
161   - Use standard REST/GraphQL patterns
162   - Output OpenAPI/GraphQL schema to `/contracts/`
163
1643. **Generate contract tests** from contracts:
165   - One test file per endpoint
166   - Assert request/response schemas
167   - Tests must fail (no implementation yet)
168
1694. **Extract test scenarios** from user stories:
170   - Each story → integration test scenario
171   - Quickstart test = story validation steps
172
1735. **Update agent file incrementally** (O(1) operation):
174   - Run `/scripts/update-agent-context.sh [claude|gemini|copilot]` for your AI assistant
175   - If exists: Add only NEW tech from current plan
176   - Preserve manual additions between markers
177   - Update recent changes (keep last 3)
178   - Keep under 150 lines for token efficiency
179   - Output to repository root
180
181**Output**: data-model.md, /contracts/*, failing tests, quickstart.md, agent-specific file
182
183## Phase 2: Task Planning Approach
184*This section describes what the /tasks command will do - DO NOT execute during /plan*
185
186**Task Generation Strategy**:
187- Load `/templates/tasks-template.md` as base
188- Generate tasks from Phase 1 design docs (contracts, data model, quickstart)
189- Each contract → contract test task [P]
190- Each entity → model creation task [P] 
191- Each user story → integration test task
192- Implementation tasks to make tests pass
193
194**Ordering Strategy**:
195- TDD order: Tests before implementation 
196- Dependency order: Models before services before UI
197- Mark [P] for parallel execution (independent files)
198
199**Estimated Output**: 25-30 numbered, ordered tasks in tasks.md
200
201**IMPORTANT**: This phase is executed by the /tasks command, NOT by /plan
202
203## Phase 3+: Future Implementation
204*These phases are beyond the scope of the /plan command*
205
206**Phase 3**: Task execution (/tasks command creates tasks.md)  
207**Phase 4**: Implementation (execute tasks.md following constitutional principles)  
208**Phase 5**: Validation (run tests, execute quickstart.md, performance validation)
209
210## Complexity Tracking
211*Fill ONLY if Constitution Check has violations that must be justified*
212
213| Violation | Why Needed | Simpler Alternative Rejected Because |
214|-----------|------------|-------------------------------------|
215| [e.g., 4th project] | [current need] | [why 3 projects insufficient] |
216| [e.g., Repository pattern] | [specific problem] | [why direct DB access insufficient] |
217
218
219## Progress Tracking
220*This checklist is updated during execution flow*
221
222**Phase Status**:
223- [x] Phase 0: Research complete (/plan command)
224- [x] Phase 1: Design complete (/plan command)
225- [x] Phase 2: Task planning complete (/plan command - describe approach only)
226- [ ] Phase 3: Tasks generated (/tasks command)
227- [ ] Phase 4: Implementation complete
228- [ ] Phase 5: Validation passed
229
230**Gate Status**:
231- [x] Initial Constitution Check: PASS
232- [x] Post-Design Constitution Check: PASS
233- [x] All NEEDS CLARIFICATION resolved
234- [x] Complexity deviations documented (none required)
235
236---
237*Based on Constitution v2.1.1 - See `/memory/constitution.md`*