merge: integrate main restructuring into dev

- Resolve 57 merge conflicts from codebase restructure
- Port dev feature code to new directory structure:
  * Update import paths to use @/ aliases
  * Add backward-compatible API signatures (createInstance, startInstance, deleteInstance)
  * Add missing type exports (ProjectWithRepos, InstanceHealth, Branch, BranchesResponse)
  * Extend Session and GitRepository types for dev features
  * Extend TerminalComponent props for mobile terminal wrapper
  * Add missing icon names (bell, drag, undo)

Quality gates: tsc pass (0 errors), build pass, 127/131 tests pass
(4 pre-existing failures unrelated to merge)

openspec/specs/frontend-foundation/spec.md

@@ -111,36 +111,23 @@ The system SHALL provide a dashboard overview.
   - Recent activity
   - Quick action buttons
 
-### Requirement: Tool Interface Type Dropdown
-The tool workshop SHALL provide a dropdown for selecting a single interface type.
+### Requirement: Projects Listing Page Layout
+The projects listing page SHALL display project cards with Settings, Delete, and Open Workspace actions, where Open Workspace is the rightmost action.
 
-#### Scenario: Interface type dropdown
-- GIVEN the tool workshop page
-- WHEN a user creates or edits a tool type
-- THEN the interface type field is a dropdown (not checkboxes)
-- AND the options are "web" and "terminal"
-- AND only one option can be selected
+#### Scenario: Project card action layout
+- GIVEN the projects listing page
+- WHEN project cards are rendered
+- THEN each card shows actions in order: Settings link, Delete button, Open Workspace button (rightmost)
 
-### Requirement: Conditional Port Fields
-The tool workshop SHALL conditionally show or hide port-related fields based on the selected interface type.
+#### Scenario: Navigate to project settings
+- GIVEN the projects listing page
+- WHEN a user clicks the Settings link
+- THEN they navigate to `/projects/:id/settings`
 
-#### Scenario: Web tool shows port fields
-- GIVEN a tool type with interface type "web"
-- WHEN the user views the tool editor
-- THEN the Default Port field is visible and required
-- AND port-related config fields are shown
-
-#### Scenario: Terminal tool hides port fields
-- GIVEN a tool type with interface type "terminal"
-- WHEN the user views the tool editor
-- THEN the Default Port field is hidden
-- AND port-related config fields are hidden or disabled
-
-#### Scenario: Changing interface type updates visibility
-- GIVEN a user changes interface type from "web" to "terminal"
-- WHEN the change is applied
-- THEN port fields are immediately hidden
-- AND any port value is preserved but not validated
+#### Scenario: No inline edit modal
+- GIVEN the projects listing page
+- WHEN a user views a project card
+- THEN no inline Edit button or modal dialog is available
 
 ## Dependencies
 

openspec/specs/project-management/spec.md

@@ -31,17 +31,38 @@ The system SHALL list projects owned by the authenticated user, including relate
 - WHEN one user requests their project list
 - THEN only that user's projects are returned
 
-### Requirement: Project Updates
-The system SHALL support updating project details for project owners only.
+### Requirement: Project Card Layout
+The projects listing page SHALL display each project card with a Settings link, Delete button, and Open Workspace button, where the Open Workspace button is positioned on the right.
 
-#### Scenario: Update project
-- GIVEN a project owner
-- WHEN they update the name or description
+#### Scenario: View project card actions
+- GIVEN the projects listing page
+- WHEN a project card is rendered
+- THEN it displays:
+  - A Settings link navigating to `/projects/:id/settings`
+  - A Delete button with confirmation
+  - An Open Workspace button positioned on the right side
+
+#### Scenario: Navigate to project settings
+- GIVEN the projects listing page
+- WHEN a user clicks the Settings link on a project card
+- THEN they are navigated to the project settings page
+
+#### Scenario: No inline edit on project cards
+- GIVEN the projects listing page
+- WHEN a project card is rendered
+- THEN no inline Edit button or modal dialog is present
+
+### Requirement: Project Updates
+The system SHALL support updating project details for project owners via the project settings page.
+
+#### Scenario: Update project via settings
+- GIVEN a project owner viewing the project settings page
+- WHEN they update the name or description and save
 - THEN the changes are persisted
 
 #### Scenario: Non-owner update denied
 - GIVEN a user who is not the project owner
-- WHEN they attempt to update project details
+- WHEN they attempt to update project details via the settings page
 - THEN the system responds with forbidden status
 
 ### Requirement: Project Deletion