diff --git a/.storkit/work/1_backlog/429_story_interactive_project_setup_wizard_for_new_storkit_projects.md b/.storkit/work/1_backlog/429_story_interactive_project_setup_wizard_for_new_storkit_projects.md
deleted file mode 100644
index c92f9b7c..00000000
--- a/.storkit/work/1_backlog/429_story_interactive_project_setup_wizard_for_new_storkit_projects.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-name: "Interactive project setup wizard for new storkit projects"
-agent: coder-opus
----
-
-# Story 429: Interactive project setup wizard for new storkit projects
-
-## User Story
-
-As a developer adopting storkit on an existing project, I want a guided setup process that scaffolds the .storkit directory and has an agent generate project-specific configuration files, so that I can get up and running without manually writing specs and scripts.
-
-## Acceptance Criteria
-
-- [ ] storkit init scaffolds .storkit/ directory structure, project.toml, and .mcp.json without clobbering any existing files (especially CLAUDE.md)
-- [ ] Setup wizard tracks progress through ordered steps, resumable if interrupted
-- [ ] Step 1: scaffold .storkit/ directory structure and project.toml
-- [ ] Step 2: agent reads codebase and generates specs/00_CONTEXT.md, user confirms or requests revision
-- [ ] Step 3: agent reads tech stack and generates specs/tech/STACK.md, user confirms or requests revision
-- [ ] Step 4: agent creates script/test that runs the project's actual test suite, user runs it to verify, then confirms
-- [ ] Step 5: agent creates script/release tailored to the project's deployment, user confirms
-- [ ] Step 6: agent creates script/test_coverage if the stack supports it, user confirms
-- [ ] Each step gates on user confirmation before advancing to the next
-- [ ] Existing CLAUDE.md is preserved — storkit appends its content or leaves it untouched
-
-## Out of Scope
-
-- TBD
diff --git a/.storkit/work/1_backlog/430_bug_status_command_traffic_light_dots_not_coloured_in_matrix.md b/.storkit/work/1_backlog/430_bug_status_command_traffic_light_dots_not_coloured_in_matrix.md
new file mode 100644
index 00000000..d769f08f
--- /dev/null
+++ b/.storkit/work/1_backlog/430_bug_status_command_traffic_light_dots_not_coloured_in_matrix.md
@@ -0,0 +1,27 @@
+---
+name: "Status command traffic light dots not coloured in Matrix"
+---
+
+# Bug 430: Status command traffic light dots not coloured in Matrix
+
+## Description
+
+The traffic light dots in the status command use plain Unicode characters (○ ● ◑ ✗) which render without colour in Matrix. The HTML formatted_body should use data-mx-color to colour them green/yellow/red.
+
+## How to Reproduce
+
+Send the status command to the bot in Matrix. Observe the dots are monochrome.
+
+## Actual Result
+
+Dots render as plain monochrome Unicode characters.
+
+## Expected Result
+
+Dots render in colour: green (● running), yellow (◑ throttled), red (✗ blocked), grey (○ idle). Use font tag with data-mx-color attribute for Matrix HTML formatted_body.
+
+## Acceptance Criteria
+
+- [ ] HTML formatted_body uses <font data-mx-color="#colour">dot</font> for each traffic light state
+- [ ] Green (#00cc00) for running, yellow (#ffaa00) for throttled, red (#cc0000) for blocked, grey (#888888) for idle
+- [ ] Plain text fallback remains unchanged (Unicode dots for non-HTML transports)