From 37fef66fa1f5d0a9cf3d3130c4429a0926973e8a Mon Sep 17 00:00:00 2001 From: Dave Date: Mon, 23 Feb 2026 14:34:01 +0000 Subject: [PATCH] story-kit: start 72_bug_story_creation_does_not_quote_yaml_special_characters_in_name --- ...t_quote_yaml_special_characters_in_name.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 .story_kit/work/2_current/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md 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 new file mode 100644 index 0000000..ad2a633 --- /dev/null +++ b/.story_kit/work/2_current/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