Project creation is workign

.story_kit/specs/functional/PROJECT_MANAGEMENT.md

@@ -12,7 +12,7 @@ The application operates in two primary states regarding project context:
 
 ## 2. Selection Logic
 *   **Trigger:** User initiates "Open Project".
-*   **Mechanism:** Native OS Directory Picker (via `tauri-plugin-dialog`).
+*   **Mechanism:** Path entry in the selection screen.
 *   **Validation:**
     *   The backend receives the selected path.
     *   The backend verifies:
@@ -20,7 +20,18 @@ The application operates in two primary states regarding project context:
         2.  Path is a directory.
         3.  Path is readable.
     *   If valid -> State transitions to **Active**.
-    *   If invalid -> Error returned to UI, State remains **Idle**.
+    *   If invalid because the path does not exist:
+        *   The backend creates the directory.
+        *   The backend scaffolds the Story Kit metadata under the new project root:
+            *   `.story_kit/README.md`
+            *   `.story_kit/specs/README.md`
+            *   `.story_kit/specs/00_CONTEXT.md`
+            *   `.story_kit/specs/tech/STACK.md`
+            *   `.story_kit/specs/functional/` (directory)
+            *   `.story_kit/stories/archive/` (directory)
+        *   If scaffolding succeeds -> State transitions to **Active**.
+        *   If scaffolding fails -> Error returned to UI, State remains **Idle**.
+    *   If invalid for other reasons -> Error returned to UI, State remains **Idle**.
 
 ## 3. Security Boundaries
 *   Once a project is selected, the `SessionState` struct in Rust locks onto this path.

.story_kit/stories/25_auto_scaffold_story_kit.md

@@ -0,0 +1,24 @@
+# Story 25: Auto-Scaffold Story Kit Metadata on New Projects
+
+## User Story
+As a user, I want the app to automatically scaffold the `.story_kit` directory when I open a path that doesn't exist, so new projects are ready for the Story Kit workflow immediately.
+
+## Acceptance Criteria
+- When I enter a non-existent project path and press Enter/Open, the app creates the directory.
+- The app also creates the `.story_kit` directory under the new project root.
+- The `.story_kit` structure includes:
+  - `README.md` (the Story Kit workflow instructions)
+  - `specs/`
+    - `README.md`
+    - `00_CONTEXT.md`
+    - `tech/STACK.md`
+    - `functional/` (created, even if empty)
+  - `stories/`
+    - `archive/`
+- The project opens successfully after scaffolding completes.
+- If any scaffolding step fails, the UI shows a clear error message and does not open the project.
+
+## Out of Scope
+- Creating any `src/` files or application code.
+- Populating project-specific content beyond the standard Story Kit templates.
+- Prompting the user for metadata (e.g., project name, description, stack choices).