From c7c4a57533aefd9996e5f5e6f1a90d0f11514d0c Mon Sep 17 00:00:00 2001 From: Timmy Date: Thu, 26 Mar 2026 11:03:43 +0000 Subject: [PATCH] storkit: create 399_story_cli_port_flag_with_project_toml_persistence --- ...port_flag_with_project_toml_persistence.md | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .storkit/work/1_backlog/399_story_cli_port_flag_with_project_toml_persistence.md diff --git a/.storkit/work/1_backlog/399_story_cli_port_flag_with_project_toml_persistence.md b/.storkit/work/1_backlog/399_story_cli_port_flag_with_project_toml_persistence.md new file mode 100644 index 00000000..9bd64644 --- /dev/null +++ b/.storkit/work/1_backlog/399_story_cli_port_flag_with_project_toml_persistence.md @@ -0,0 +1,23 @@ +--- +name: "CLI --port flag with project.toml persistence" +--- + +# Story 399: CLI --port flag with project.toml persistence + +## User Story + +As a developer, I want to set the server port via a --port CLI flag that persists to project.toml, so that I don't have to remember an environment variable on every run. + +## Acceptance Criteria + +- [ ] storkit --help shows a --port option +- [ ] storkit --port 4000 starts the server on port 4000 +- [ ] After first run with --port, the port is saved to project.toml +- [ ] On subsequent runs without --port, the port from project.toml is used +- [ ] CLI --port overrides the value in project.toml +- [ ] Default port is 3001 when neither --port nor project.toml port is set +- [ ] STORKIT_PORT env var continues to work as lowest-priority fallback + +## Out of Scope + +- TBD