docs: add Table of Contents to README (AAA+ B-axis, ORDRE 32)

README is 260 lines with 13 content H2 sections beyond Install/
Requirements -- long enough that a reader has to scroll blind to find
the section they need. Mirrors config-audit/README.md's TOC pattern:
flat list, placed after Install/Requirements, anchors validated
mechanically against actual headings.

README.md

@@ -48,6 +48,22 @@ Installing does not activate it — see [Activate](#activate).
 
 ---
 
+## Table of Contents
+
+- [The problem](#the-problem)
+- [What it does](#what-it-does)
+- [Before / after](#before--after)
+- [Getting more detail](#getting-more-detail)
+- [Activate](#activate)
+- [How it works](#how-it-works)
+- [Non-goals](#non-goals)
+- [Cross-plugin use](#cross-plugin-use)
+- [Compatibility](#compatibility)
+- [Forking this](#forking-this)
+- [Versioning and stability](#versioning-and-stability)
+- [Changelog](#changelog)
+- [License](#license)
+
 ## The problem
 
 Default Claude Code output is engineering output. Long absolute paths. Raw `git` invocations. JSON dumps. Stack traces. Bullet lists for everything. That is fine for a developer running terminal commands — it is the lingua franca of CLI work. It is also the wrong register when: