feat: mobile tool workshop with list-detail pattern

- Add mobile viewport detection to ToolWorkshopPage
- Implement mobile list view with MobileListView component
- Implement mobile detail view with MobileDetailView component
- Implement mobile edit view with MobileEditView component
- Add MobileFAB for creating new tool types
- Fix IconName type issues in mobile components
- TypeScript check passes, build succeeds

openspec/changes/mobile-pages-overhaul/proposal.md

@@ -0,0 +1,28 @@
+## Why
+
+The current mobile experience for complex pages (Tool Workshop, Config Profiles, Repo Workspace) is broken or unusable. Tool Workshop and Config Profiles use desktop split-pane layouts that don't work on small screens, and Config Profiles isn't even accessible from mobile navigation. The Repo Workspace shows a file tree and editor side-by-side, making both unusable on phones. We need mobile-first designs for these critical configuration and workspace pages.
+
+## What Changes
+
+- **Mobile Navigation**: Group "Tool Workshop" and "Config Profiles" under a single "Tools" bottom nav item that opens a bottom sheet with sub-options
+- **Mobile Tool Workshop**: Replace split-pane with list→detail navigation pattern (iOS Settings style)
+- **Mobile Config Profiles**: Replace split-pane with list→detail navigation pattern with read-first detail view
+- **Mobile Repo Workspace**: File tree as primary view with bottom tabs for Editor, Git, and Terminal
+- **Desktop**: No changes to existing layouts or navigation
+
+## Capabilities
+
+### New Capabilities
+- `mobile-tools-navigation`: Bottom sheet navigation grouping Tool Workshop and Config Profiles
+- `mobile-list-detail`: List→detail navigation pattern for complex configuration pages
+- `mobile-repo-workspace`: File-tree-primary workspace layout with tabbed secondary views
+
+### Modified Capabilities
+- `mobile-navigation`: Add "Tools" group with bottom sheet sub-navigation
+
+## Impact
+
+- Frontend: New mobile-specific components and page layouts
+- Navigation: Mobile bottom nav structure changes
+- No API changes required
+- No database changes required