fix: replace em dashes in CLAUDE.md context-mode section

The context-mode routing rules block used em dashes, which the Validate
workflow's content-quality check rejects. Swap all 16 em/en dashes for
hyphens per the repo's no-em-dash convention.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: TMHSDigital

CLAUDE.md

@@ -145,35 +145,35 @@ Do not hand-edit `plugin.json` `version`, the README badge, or the `**Version:**
 | `mcp-server/data/events.json` | Indexed canonical CFX event names and payloads |
 | `mcp-server/data/docs_index.json` | Indexed `docs.fivem.net` snippets for offline search |
 
-# context-mode — MANDATORY routing rules
+# context-mode - MANDATORY routing rules
 
-You have context-mode MCP tools available. These rules are NOT optional — they protect your context window from flooding. A single unrouted command can dump 56 KB into context and waste the entire session.
+You have context-mode MCP tools available. These rules are NOT optional - they protect your context window from flooding. A single unrouted command can dump 56 KB into context and waste the entire session.
 
-## BLOCKED commands — do NOT attempt these
+## BLOCKED commands - do NOT attempt these
 
-### curl / wget — BLOCKED
+### curl / wget - BLOCKED
 Any Bash command containing `curl` or `wget` is intercepted and replaced with an error message. Do NOT retry.
 Instead use:
 - `ctx_fetch_and_index(url, source)` to fetch and index web pages
 - `ctx_execute(language: "javascript", code: "const r = await fetch(...)")` to run HTTP calls in sandbox
 
-### Inline HTTP — BLOCKED
+### Inline HTTP - BLOCKED
 Any Bash command containing `fetch('http`, `requests.get(`, `requests.post(`, `http.get(`, or `http.request(` is intercepted and replaced with an error message. Do NOT retry with Bash.
 Instead use:
-- `ctx_execute(language, code)` to run HTTP calls in sandbox — only stdout enters context
+- `ctx_execute(language, code)` to run HTTP calls in sandbox - only stdout enters context
 
-### WebFetch — BLOCKED
+### WebFetch - BLOCKED
 WebFetch calls are denied entirely. The URL is extracted and you are told to use `ctx_fetch_and_index` instead.
 Instead use:
 - `ctx_fetch_and_index(url, source)` then `ctx_search(queries)` to query the indexed content
 
-## REDIRECTED tools — use sandbox equivalents
+## REDIRECTED tools - use sandbox equivalents
 
 ### Bash (>20 lines output)
 Bash is ONLY for: `git`, `mkdir`, `rm`, `mv`, `cd`, `ls`, `npm install`, `pip install`, and other short-output commands.
 For everything else, use:
-- `ctx_batch_execute(commands, queries)` — run multiple commands + search in ONE call
-- `ctx_execute(language: "shell", code: "...")` — run in sandbox, only stdout enters context
+- `ctx_batch_execute(commands, queries)` - run multiple commands + search in ONE call
+- `ctx_execute(language: "shell", code: "...")` - run in sandbox, only stdout enters context
 
 ### Read (for analysis)
 If you are reading a file to **Edit** it → Read is correct (Edit needs content in context).
@@ -184,11 +184,11 @@ Grep results can flood context. Use `ctx_execute(language: "shell", code: "grep
 
 ## Tool selection hierarchy
 
-1. **GATHER**: `ctx_batch_execute(commands, queries)` — Primary tool. Runs all commands, auto-indexes output, returns search results. ONE call replaces 30+ individual calls.
-2. **FOLLOW-UP**: `ctx_search(queries: ["q1", "q2", ...])` — Query indexed content. Pass ALL questions as array in ONE call.
-3. **PROCESSING**: `ctx_execute(language, code)` | `ctx_execute_file(path, language, code)` — Sandbox execution. Only stdout enters context.
-4. **WEB**: `ctx_fetch_and_index(url, source)` then `ctx_search(queries)` — Fetch, chunk, index, query. Raw HTML never enters context.
-5. **INDEX**: `ctx_index(content, source)` — Store content in FTS5 knowledge base for later search.
+1. **GATHER**: `ctx_batch_execute(commands, queries)` - Primary tool. Runs all commands, auto-indexes output, returns search results. ONE call replaces 30+ individual calls.
+2. **FOLLOW-UP**: `ctx_search(queries: ["q1", "q2", ...])` - Query indexed content. Pass ALL questions as array in ONE call.
+3. **PROCESSING**: `ctx_execute(language, code)` | `ctx_execute_file(path, language, code)` - Sandbox execution. Only stdout enters context.
+4. **WEB**: `ctx_fetch_and_index(url, source)` then `ctx_search(queries)` - Fetch, chunk, index, query. Raw HTML never enters context.
+5. **INDEX**: `ctx_index(content, source)` - Store content in FTS5 knowledge base for later search.
 
 ## Subagent routing
 
@@ -197,7 +197,7 @@ When spawning subagents (Agent/Task tool), the routing block is automatically in
 ## Output constraints
 
 - Keep responses under 500 words.
-- Write artifacts (code, configs, PRDs) to FILES — never return them as inline text. Return only: file path + 1-line description.
+- Write artifacts (code, configs, PRDs) to FILES - never return them as inline text. Return only: file path + 1-line description.
 - When indexing content, use descriptive source labels so others can `ctx_search(source: "label")` later.
 
 ## ctx commands