feat: add devcontainer and refactor frontend routing

- Add devcontainer configuration for VS Code
- Implement page-based routing with HomePage and TestPage
- Refactor BoltService with improved formatting
- Update docker-compose with volume management
- Add application access documentation to README
- Update design doc with MCP server guidance
- Enhance gitignore for multiple node_modules scenarios

Author: alvagante

.devcontainer/README.md

@@ -0,0 +1,52 @@
+{
+  "name": "Bolt Execution Manager",
+  "dockerComposeFile": "../docker-compose.yml",
+  "service": "app",
+  "workspaceFolder": "/workspace",
+  
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "dbaeumer.vscode-eslint",
+        "esbenp.prettier-vscode",
+        "svelte.svelte-vscode",
+        "ms-azuretools.vscode-docker",
+        "editorconfig.editorconfig"
+      ],
+      "settings": {
+        "editor.formatOnSave": true,
+        "editor.defaultFormatter": "esbenp.prettier-vscode",
+        "editor.codeActionsOnSave": {
+          "source.fixAll.eslint": "explicit"
+        },
+        "[typescript]": {
+          "editor.defaultFormatter": "esbenp.prettier-vscode"
+        },
+        "[svelte]": {
+          "editor.defaultFormatter": "svelte.svelte-vscode"
+        }
+      }
+    }
+  },
+  
+  "forwardPorts": [3000, 5173],
+  "portsAttributes": {
+    "3000": {
+      "label": "Backend API",
+      "onAutoForward": "notify"
+    },
+    "5173": {
+      "label": "Frontend (Vite)",
+      "onAutoForward": "notify"
+    }
+  },
+  
+  "postCreateCommand": "npm install && cd backend && npm install && cd ../frontend && npm install",
+  
+  "remoteUser": "node",
+  
+  "features": {
+    "ghcr.io/devcontainers/features/git:1": {},
+    "ghcr.io/devcontainers/features/github-cli:1": {}
+  }
+}

.devcontainer/devcontainer.json

@@ -1,5 +1,7 @@
 # Dependencies
 node_modules/
+node_modules_mac/
+node_modules_cont/
 package-lock.json
 
 # Build outputs

.gitignore

@@ -582,7 +582,7 @@ docker run -d \
 4. What level of Bolt output verbosity should we capture?
    - **Decision**: Use `--format json` for structured output, capture stderr for errors
 
-## Documents
+## IMPORTANT: Documents and MCP servers
 
 Documentation for final users should always be placed in the docs/ directory.
 
@@ -593,4 +593,8 @@ and be named like YYYYMMDD-HHMM-DESCRIPTION.md. (For example .kiro/summaries/202
 
 If there are things left to do, like fixing tests or implement features which have not been completed in a session, they should be documented under .kiro/todos/ and named with the format YYYYMMDD-HHMM-DESCRIPTION.md
 
-Scripts useful for testing, troubleshooring, development or maintenance should be placed in appropriate subdirs in the scripts/ directory.
+Scripts useful for testing, troubleshooring, development or maintenance should be placed in appropriate subdirs in the scripts/ directory.
+
+MCP servers are available for SVELTE, use the get-documentation, svelte-autofixer, list-sections and playground-link tools to investigate Svelte related code activities.
+
+For TailWind CSS, use MCP tailwindcss-server and the related tools.

.kiro/specs/pabawi/design.md

@@ -40,6 +40,16 @@ npm run dev:backend
 npm run dev:frontend
 ```
 
+### Accessing the Application
+
+**Development Mode** (when running both servers separately):
+- **Frontend UI**: http://localhost:5173 (Main application interface)
+- **Backend API**: http://localhost:3000/api (API endpoints)
+
+**Production Mode** (Docker or built application):
+- **Application**: http://localhost:3000 (Frontend and API served together)
+- The backend serves the built frontend as static files
+
 ## Build
 
 ```bash
@@ -91,6 +101,8 @@ docker run -d \
   pabawi:latest
 ```
 
+Access the application at http://localhost:3000
+
 ### Running with Docker Compose
 
 ```bash
@@ -104,6 +116,8 @@ docker-compose logs -f
 docker-compose down
 ```
 
+Access the application at http://localhost:3000
+
 ### Environment Variables
 
 Copy `.env.example` to `.env` and configure as needed. Key variables: