docs: sweep em/en dashes in README and LLM_PROVIDERS, add reranker-eval note (#172)

* docs: sweep em/en dashes in README and LLM_PROVIDERS, add reranker-eval note

- README.md: replace two en-dashes in the env-var table with `--` so the public-doc
  em-dash gate passes; add a brief evaluation note for the cross-encoder reranker
  knob (now reachable via MemoryEngine.create(rerank_model=...)) and document the
  measured ~15ms per-query cost on the bundled retrieval gates
- docs/LLM_PROVIDERS.md: replace one em-dash in the Windows note with `--`

These are the only doc changes shipped in this round; the rest of the work is in
PR1 (core + MCP + integration).

* fix(docs): replace unverified reranker benchmark with reproduction pointer

The previous paragraph quoted model-specific MRR@5 / hit@5 / ~15 ms numbers
for the optional cross-encoder reranker without identifying the model,
revision, hardware, exact command, or evidence artifact. Per AGENTS.md
L177-L178 ("Prove 'better' with a number. No retrieval/quality claim ships
without an eval."), such numbers must not ship until the evidence is
registered.

The README now contains a short note that reranker benchmarks are
intentionally unpublished and points operators at the local reproduction
commands (`python -m eval.ablation`, `python -m eval.reinforcement`).

Co-authored-by: CommandCodeBot <noreply@commandcode.ai>

* fix(docs): drop the last em-dash so the public-docs gate is green

PR #172 introduced a single em-dash on README.md:751 inside the new
reranker-eval blockquote. The repo's no-em-dashes-in-public-docs policy
(tests/test_benchmark_evidence.py::test_public_facing_docs_do_not_use_em_dashes)
blocks on every Python matrix plus the core floor and coverage gate jobs.
Replace U+2014 with --, mirroring the convention used elsewhere in the
same blockquote.

* docs: correct ablation benchmark description

---------

Co-authored-by: CommandCodeBot <noreply@commandcode.ai>

Author: Coding-Dev-Tools

README.md

@@ -721,8 +721,8 @@ file. It never searches the working directory for `.env`, and explicit process v
 | `ENGRAPHIS_ALLOW_AUTOMATIC_CRITICAL_RETENTION` | `false` | Opt in only when an LLM supervisor may automatically assign the long-lived `critical` class; explicit user-selected critical retention is unaffected |
 | `ENGRAPHIS_WHISPER_MODEL` | Not set | Enables local faster-whisper audio/video transcription |
 | `ENGRAPHIS_POSTGRES_DSN` | Not set | CLI-only PostgreSQL source; used for the connection and never stored |
-| `ENGRAPHIS_POSTGRES_CONNECT_TIMEOUT` | `10` | PostgreSQL introspection connection timeout in seconds (bounded to 1–120) |
-| `ENGRAPHIS_POSTGRES_STATEMENT_TIMEOUT_MS` | `30000` | Per-introspection PostgreSQL statement timeout in milliseconds (bounded to 1–300000) |
+| `ENGRAPHIS_POSTGRES_CONNECT_TIMEOUT` | `10` | PostgreSQL introspection connection timeout in seconds (bounded to 1--120) |
+| `ENGRAPHIS_POSTGRES_STATEMENT_TIMEOUT_MS` | `30000` | Per-introspection PostgreSQL statement timeout in milliseconds (bounded to 1--300000) |
 | `ENGRAPHIS_GRAPH_TOKEN` | Not set | Bearer token for `engraphis-graph-server`; required off-loopback |
 | `ENGRAPHIS_GRAPH_HOST` / `ENGRAPHIS_GRAPH_PORT` | `127.0.0.1` / `8720` | Read-only graph/recall server bind address |
 | `ENGRAPHIS_LLM_PROVIDER` | `openai` | `openai \| anthropic \| google \| openrouter \| custom` |
@@ -747,6 +747,12 @@ See `.env.example` for the full variable inventory. Supply those values through
 environment or the trusted config file above; copying it to an arbitrary `./.env` does not make
 Engraphis load it.
 
+> **Ablation fixture:** `python -m eval.ablation` is an offline deterministic check that prints
+> `recall@5` comparisons for vector-only and hybrid retrieval, multi-hop graph arms, and
+> retrieval policies, plus ordinary-recall age and semantic-confidence checks. It does not
+> produce MRR, hit@5, or ms/query results. Use `python -m eval.reinforcement` for retention
+> trajectories, and register evidence before quoting any benchmark results.
+
 ---
 
 ## Project structure

docs/LLM_PROVIDERS.md

@@ -223,6 +223,13 @@ server, replacing the path with the one from initialization:
 cmd mcp add --scope local --env ENGRAPHIS_DB_PATH=/absolute/path/to/engraphis.db engraphis -- engraphis-mcp
 ```
 
+Windows: `cmd` may resolve to `cmd.exe` (the built-in Windows command interpreter)
+instead of the Command Code CLI. If `cmd mcp list` opens a Windows command-prompt window or
+prints `'mcp' is not recognized`, the wrong `cmd` was found on `PATH`. Run `where cmd` and
+ensure the Command Code CLI's install directory appears before `C:\Windows\System32`;
+otherwise invoke the CLI by its absolute path (e.g.
+`C:\Users\you\AppData\Roaming\Python\Scripts\cmd.exe`).
+
 All Command Code options precede the server name, and `--` separates the name from the stdio
 command. `engraphis-mcp` runs locally over stdio; normal local use needs no HTTP endpoint or
 Engraphis API key.
@@ -244,6 +251,9 @@ cmd mcp list
 cmd mcp get engraphis
 ```
 
+(If these commands open a Windows command prompt instead of listing MCP servers, follow the
+Windows note above -- `cmd` resolved to `cmd.exe`.)
+
 Start a normal Command Code session with `cmd`, open `/mcp`, and confirm that `engraphis` is
 connected and exposes tools. Then ask Command Code: "Call `engraphis_stats` and show me the
 result." A response with memory counts confirms the end-to-end connection.