docs(wiki): bump compat doc to Hermes v0.11.0 + v2.5 targets

Hermes-Version-Compatibility.md

@@ -4,7 +4,7 @@ Scarf reads Hermes's SQLite database directly and parses CLI output from `hermes
 
 ## Currently targeted
 
-**Scarf 2.3.x targets Hermes v0.10.0 (v2026.4.16)**, bumped from Scarf 2.2's v0.9.0 target. v0.10.0 is the recommended minimum to get every feature working — the **Tool Gateway** surface (Nous Portal in the model picker, subscription detection, per-task Nous routing, in-app sign-in, Credential Pools auth-type gating) is sourced from the `HERMES_OVERLAYS` table in `hermes-agent/hermes_cli/providers.py`, which is only populated in v0.10.0+. On earlier Hermes releases, Scarf 2.3 still runs — you just won't see Nous Portal in the picker and the Tool Gateway Health card won't have subscription data to show. ACP `session/fork` / `session/list` / `session/resume` used by remote chat also need v0.10.0.
+**Scarf 2.5.x targets Hermes v0.11.0 (v2026.4.23)**, bumped from Scarf 2.3's v0.10.0 target. v0.11.0 is the recommended minimum to get every feature working — the new `/steer` slash command, the `messages.reasoning_content` / `sessions.api_call_count` columns, the SKILL.md frontmatter chips (`allowed_tools` / `related_skills` / `dependencies`), and the `hermes memory reset` toolbar action all require v0.11.0+. On earlier Hermes releases, Scarf 2.5 still runs — `/steer` is harmless on older agents (they treat it as an unknown command), v0.11 DB columns silently degrade to nil/0 via `HermesDataService.hasV011Schema`, and the new skills (`design-md`, `spotify`) only appear if they're actually installed on the host.
 
 ## Verified versions
 
@@ -14,11 +14,12 @@ Scarf reads Hermes's SQLite database directly and parses CLI output from `hermes
 | v0.7.0 | 2026-04-03 | Verified |
 | v0.8.0 | 2026-04-08 | Verified |
 | v0.9.0 | 2026-04-13 | Verified |
-| v0.10.0 | 2026-04-16 | **Verified — current target (Tool Gateway requires this)** |
+| v0.10.0 | 2026-04-16 | Verified (Tool Gateway introduced) |
+| v0.11.0 | 2026-04-23 | **Verified — current target** |
 
 ## How compatibility is maintained
 
-**SQLite schema detection.** [`HermesDataService`](Core-Services) probes for v0.7+ columns (`reasoning_tokens`, `actual_cost_usd`, `cost_status`, `billing_provider`) at open time. When absent, the model fields stay nil and the views render placeholders. Older databases keep working; newer columns light up automatically once the database has them.
+**SQLite schema detection.** [`HermesDataService`](Core-Services) probes for v0.7+ columns (`reasoning_tokens`, `actual_cost_usd`, `cost_status`, `billing_provider`) and v0.11+ columns (`sessions.api_call_count`, `messages.reasoning_content`) at open time. The v0.11 flag (`hasV011Schema`) only flips true when both new columns are present — partial-migration DBs (sessions migrated, messages not yet) stay on the v0.7 path to avoid runtime "no such column" errors. When absent, model fields stay nil/0 and the views render placeholders. Older databases keep working; newer columns light up automatically once the database has them.
 
 **Log line format.** Hermes log lines may carry an optional `[session_id]` tag between the level and the logger name. [`HermesLogService.parseLine`](Core-Services) treats the tag as an optional capture group, so older untagged lines still parse.
 
@@ -50,4 +51,4 @@ If a new Hermes release breaks something in Scarf, please file an issue includin
 - The relevant log snippet from `~/.hermes/logs/errors.log` (filter sensitive content first).
 
 ---
-_Last updated: 2026-04-24 — Scarf v2.3.0_
+_Last updated: 2026-04-25 — Scarf v2.5.0 + Hermes v0.11.0_