docs(code-review): clarify fuzzy matching for story identification

- Changed priority 1 from exact to resembles: handles format variations (1 2, 1.2, one-two, one thirty two)
- Explicitly prevents false matches: 1-33 does not match 1-32
- Updated priority 3-4 to use resembles instead of contains: supports typos and TTS errors (paiment, passwd)
- Added examples for number variations and compound spoken formats
- Tested with agent validation: handles typos, format variations, misspellings correctly

src/modules/bmm/workflows/4-implementation/code-review/steps/step-01-load-story.md

@@ -35,10 +35,10 @@ If input resolves to an existing file:
 
 **Search sprint_status** (if input is not a direct file):
 Search for stories with status `review` or `done`. Match by priority:
-1. Exact story number (e.g., "1-2")
+1. Story number resembles input closely enough (e.g., "1-2" matches "1 2", "1.2", "one dash two", "one two"; "1-32" matches "one thirty two"). Do NOT match if numbers differ (e.g., "1-33" does not match "1-32")
 2. Exact story name/key (e.g., "1-2-user-auth-api")
-3. Story name/title contains input
+3. Story name/title resembles input closely enough
-4. Story description contains input
+4. Story description resembles input closely enough
 
 **Resolution:**
 - **Single match**: Confident. Set `story_path`, proceed to substep 2