docs: address Copilot review round 7 on #2203

Strip YAML properties (tags, anchors, in either order) before deciding
whether a description scalar is quoted — testing the first character alone
read `&copy "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>

.claude/skills/project-structure/evals/evals.json

@@ -1,6 +1,6 @@
 [
   {
-    "prompt": "This repo has three clients over a shared core. How should I orient myself in it before changing anything?",
+    "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"
   },
   {

.claude/skills/test-servers/evals/evals.json

@@ -8,7 +8,7 @@
     "expect": "test-servers"
   },
   {
-    "prompt": "I need a real server to exercise this change against by hand. What do I run?",
+    "prompt": "I need to run a real MCP server locally to exercise this change by hand. Which one do I run, and how do I start it?",
     "expect": "test-servers"
   },
   {