0febaa0f6f
Strip YAML properties (tags, anchors, in either order) before deciding whether a description scalar is quoted — testing the first character alone read `© "Counts # safely"` as unquoted and rejected a `#` the quotes make harmless. Count the positive-case floor by distinct prompt rather than by entry: the floor exists for breadth, so five copies of one prompt cleared it while exercising exactly the single trigger it is meant to look past. Compare on collapsed, case-folded text so trivial edits do not read as a new situation. Re-aim the two positive prompts that measured the wrong thing — the project-structure case now poses a concrete "which piece handles what" question, and the test-servers case names running a real MCP server. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SyBPs7caoMcyvnp9ArMBhV Signed-off-by: cliffhall <cliff@futurescale.com>
30 lines
990 B
JSON
30 lines
990 B
JSON
[
|
|
{
|
|
"prompt": "Something in the web client's Node backend needs changing but I do not know which piece handles what. How do I work that out?",
|
|
"expect": "project-structure"
|
|
},
|
|
{
|
|
"prompt": "I am adding a module that both the browser side and the Node side need to run. How do I decide where it goes in this repo?",
|
|
"expect": "project-structure"
|
|
},
|
|
{
|
|
"prompt": "Does browser-only transport code belong in core or in the web client?",
|
|
"expect": "project-structure"
|
|
},
|
|
{
|
|
"prompt": "I have a new file and I'm not sure where it goes. How do I decide in this repo?",
|
|
"expect": "project-structure"
|
|
},
|
|
{
|
|
"prompt": "I need to find where a feature is implemented but I do not know which client owns it. How do I work that out in this repo?",
|
|
"expect": "project-structure"
|
|
},
|
|
{
|
|
"prompt": "Convert this array of strings to uppercase.",
|
|
"expect": null
|
|
},
|
|
{
|
|
"prompt": "What is the capital of France?",
|
|
"expect": null
|
|
}
|
|
]
|