diff --git a/.story_kit/work/1_upcoming/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md b/.story_kit/work/1_upcoming/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md deleted file mode 100644 index d3676ba..0000000 --- a/.story_kit/work/1_upcoming/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -name: "Work item creation does not quote YAML special characters or include front matter" -test_plan: pending ---- - -# Bug 72: Work item creation does not quote YAML special characters or include front matter - -## Description - -Two related issues in server-side work item creation: - -1. **create_story** writes the `name` value into YAML front matter without quoting. If the name contains YAML-special characters like colons, the resulting front matter is invalid YAML and fails to parse. - -2. **create_bug** does not write YAML front matter at all (no `---` block with `name` and `test_plan`). The UI/parser expects front matter on all work items in the pipeline, so bug files show parse errors. - -## How to Reproduce - -### Issue 1 (create_story) -1. Call create_story with a name containing a colon, e.g. "Server-owned agent completion: remove report_completion dependency" -2. Open the generated .md file -3. Observe the front matter parser rejects it: "mapping values are not allowed in this context" - -### Issue 2 (create_bug) -1. Call create_bug with any name -2. Open the generated .md file -3. Observe there is no YAML front matter block — just a markdown heading - -## Actual Result - -- create_story: Invalid front matter when name contains colons -- create_bug: No front matter at all - -## Expected Result - -- All work item creation methods should write valid YAML front matter with quoted `name` values -- create_bug should include `---` front matter block with `name` and `test_plan` fields, consistent with create_story - -## Acceptance Criteria - -- [ ] create_story quotes name values containing YAML-special characters -- [ ] create_bug writes YAML front matter with name and test_plan fields -- [ ] Existing tests updated to cover special character handling diff --git a/.story_kit/work/2_current/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md b/.story_kit/work/2_current/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md index ad2a633..d3676ba 100644 --- a/.story_kit/work/2_current/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md +++ b/.story_kit/work/2_current/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md @@ -1,28 +1,42 @@ --- -name: "Story creation does not quote YAML special characters in name" +name: "Work item creation does not quote YAML special characters or include front matter" test_plan: pending --- -# Bug 72: Story creation does not quote YAML special characters in name +# Bug 72: Work item creation does not quote YAML special characters or include front matter ## Description -The create_story MCP tool writes the name value into YAML front matter without quoting. If the name contains YAML-special characters like colons, the resulting front matter is invalid YAML and fails to parse. +Two related issues in server-side work item creation: + +1. **create_story** writes the `name` value into YAML front matter without quoting. If the name contains YAML-special characters like colons, the resulting front matter is invalid YAML and fails to parse. + +2. **create_bug** does not write YAML front matter at all (no `---` block with `name` and `test_plan`). The UI/parser expects front matter on all work items in the pipeline, so bug files show parse errors. ## How to Reproduce +### Issue 1 (create_story) 1. Call create_story with a name containing a colon, e.g. "Server-owned agent completion: remove report_completion dependency" 2. Open the generated .md file -3. Observe the front matter parser rejects it +3. Observe the front matter parser rejects it: "mapping values are not allowed in this context" + +### Issue 2 (create_bug) +1. Call create_bug with any name +2. Open the generated .md file +3. Observe there is no YAML front matter block — just a markdown heading ## Actual Result -Invalid front matter: mapping values are not allowed in this context +- create_story: Invalid front matter when name contains colons +- create_bug: No front matter at all ## Expected Result -The name value should be quoted in the front matter so special characters are safe, e.g. name: "My story: with colons" +- All work item creation methods should write valid YAML front matter with quoted `name` values +- create_bug should include `---` front matter block with `name` and `test_plan` fields, consistent with create_story ## Acceptance Criteria -- [ ] Bug is fixed and verified +- [ ] create_story quotes name values containing YAML-special characters +- [ ] create_bug writes YAML front matter with name and test_plan fields +- [ ] Existing tests updated to cover special character handling diff --git a/.story_kit/work/3_qa/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md b/.story_kit/work/3_qa/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md new file mode 100644 index 0000000..ad2a633 --- /dev/null +++ b/.story_kit/work/3_qa/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md @@ -0,0 +1,28 @@ +--- +name: "Story creation does not quote YAML special characters in name" +test_plan: pending +--- + +# Bug 72: Story creation does not quote YAML special characters in name + +## Description + +The create_story MCP tool writes the name value into YAML front matter without quoting. If the name contains YAML-special characters like colons, the resulting front matter is invalid YAML and fails to parse. + +## How to Reproduce + +1. Call create_story with a name containing a colon, e.g. "Server-owned agent completion: remove report_completion dependency" +2. Open the generated .md file +3. Observe the front matter parser rejects it + +## Actual Result + +Invalid front matter: mapping values are not allowed in this context + +## Expected Result + +The name value should be quoted in the front matter so special characters are safe, e.g. name: "My story: with colons" + +## Acceptance Criteria + +- [ ] Bug is fixed and verified