dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

Getting set for release

Browse Source
This commit is contained in:
Dave
2026-03-13 12:52:56 +00:00
parent 27d9d3a3a9
commit 3035dc2a7d
10 changed files with 134 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.story_kit/project.toml
View File

@@ -102,7 +102,7 @@ Read CLAUDE.md first, then .story_kit/README.md to understand the dev process.
- URL to visit in the browser
- Things to check in the UI
- curl commands to exercise relevant API endpoints
- Kill the test server when done: `pkill -f story-kit-server || true`
- Kill the test server when done: `pkill -f story-kit || true`
### 4. Produce Structured Report
Print your QA report to stdout before your process exits. The server will automatically run acceptance gates. Use this format:
@@ -179,7 +179,7 @@ Read CLAUDE.md first, then .story_kit/README.md to understand the dev process.
- URL to visit in the browser
- Things to check in the UI
- curl commands to exercise relevant API endpoints
- Kill the test server when done: `pkill -f story-kit-server || true`
- Kill the test server when done: `pkill -f story-kit || true`
### 4. Produce Structured Report
Print your QA report to stdout before your process exits. The server will automatically run acceptance gates. Use this format:

2
.story_kit/work/6_archived/208_bug_project_scaffold_does_not_write_mcp_json_to_project_root.md
View File

@@ -13,7 +13,7 @@ Additionally, there is no way for the user to trigger scaffolding from the CLI
## How to Reproduce
1. Create an empty directory or navigate to a project without `.story_kit/`
2. Run `story-kit-server`
2. Run `story-kit`
3. Open the project via the UI file chooser
4. Try to chat using the claude-code provider

8
.story_kit/work/6_archived/209_story_accept_optional_positional_path_argument_on_startup.md
View File

@@ -6,13 +6,13 @@ name: "Accept optional positional path argument on startup"
## User Story
As a user, I want to run `story-kit-server .` or `story-kit-server /path/to/project` to start the server with that directory as the project, so that I don't have to use the UI file chooser.
As a user, I want to run `story-kit .` or `story-kit /path/to/project` to start the server with that directory as the project, so that I don't have to use the UI file chooser.
## Acceptance Criteria
- [ ] Running `story-kit-server` with no args behaves as today (auto-detect from cwd)
- [ ] Running `story-kit-server .` opens the current directory as the project
- [ ] Running `story-kit-server /some/path` opens that path as the project
- [ ] Running `story-kit` with no args behaves as today (auto-detect from cwd)
- [ ] Running `story-kit .` opens the current directory as the project
- [ ] Running `story-kit /some/path` opens that path as the project
- [ ] If the path has no .story_kit/, it is scaffolded automatically
- [ ] Invalid paths produce a clear error message

2
.story_kit/work/6_archived/211_story_skip_selection_screen_when_cli_path_argument_provided.md
View File

@@ -6,7 +6,7 @@ name: "Skip selection screen when CLI path argument provided"
## User Story
As a user, I want the frontend to go straight to the project workspace when I start the server with an explicit path argument (e.g. `story-kit-server .`), so that I don't have to click through the selection screen for a project the server already opened.
As a user, I want the frontend to go straight to the project workspace when I start the server with an explicit path argument (e.g. `story-kit .`), so that I don't have to click through the selection screen for a project the server already opened.
## Acceptance Criteria