Add planned tickets page (draft/backlog/todo)

## Code Review ### Spec Pattern Search (REQUIRED) - Searched for existing spec patterns: `find spec -name "*spec.rb" | sort` - Found existing spec files: - spec/views/dashboard_views_spec.rb ✓ - spec/features/dashboard_spec.rb ✓ - spec/features/kanban_board_spec.rb ✓ - spec/features/approvals_spec.rb ✓ - Similar patterns found: View specs for dashboard components exist in spec/views/dashboard_views_spec.rb ### Test Results - Test suite run: `bundle exec rspec` - Results: 701 examples, 2 failures, 7 pending - View specs for planning page: 21 examples, 0 failures ✓ - **Note:** The 2 failing tests (spec/features/dashboard_spec.rb) are pre-existing failures unrelated to this PR - verified they fail on both main and PR branch ### Spec Coverage Check - Files changed: - app/controllers/dashboard_controller.rb - Added planning action - app/views/dashboard/planning.html.haml - New view (162 lines) - app/views/layouts/application.html.haml - Navigation link - config/routes.rb - Added planning route - spec/views/dashboard_views_spec.rb - Specs added (69 lines) ✓ - Required specs found: - spec/views/dashboard_views_spec.rb - PRESENT ✓ (tests planning page rendering, empty state, ticket display, status legend) - Missing specs: - spec/features/planning_spec.rb - NOT ADDED (feature spec would be ideal for user interaction testing, but view specs provide good coverage) ### Findings - **Code quality:** Clean implementation, follows existing patterns (similar to kanban action) - **Security:** No issues detected - uses proper ActiveRecord includes, archived_at filtering - **Implementation:** Matches ticket requirements: - New `/planning` page ✓ - Displays draft, backlog, todo tickets ✓ - Table/list format (not kanban) ✓ - Navigation link added ✓ - Project selector for all/single projects ✓ - Shows key ticket info (ID, title, status, priority, type, subtasks, comments, age) ✓ - Epics shown separately ✓ - Status legend ✓ - **Breaking changes:** None ### Decision **PASS** - Code is well-tested with view specs, implements all ticket requirements, and introduces no new regressions. The 2 failing tests in the suite are pre-existing issues unrelated to this PR.