kvm2: user guide, appendix column and section, architecture and README entries

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/plans-executions/2026-09-16-1333-kvm2-provider.md

@@ -11,7 +11,7 @@ Plan: [docs/plans/2026-09-16-1333-kvm2-provider.md](../plans/2026-09-16-1333-kvm
 - [x] Step 6 — The four contract methods
 - [x] Step 7 — Checker and the CRD comment
 - [x] Step 8 — Deployment files, Makefile, integration test
-- [ ] Step 9 — Documentation
+- [x] Step 9 — Documentation
 - [ ] Step 10 — Milestone review
 - [ ] Step 11 — Real-host validation, changelog, MR
 
@@ -318,3 +318,23 @@ make -n test-integration-kvm2
 ```
 
 All clean. Attestation: "files read outside the allowed set: none".
+
+## Step 9 — Documentation
+
+2026-09-16 19:54. Eighth subagent step: `docs/kvm2-provider.md` (sixteen
+sections modelled on the kvm guide), a `kvm2` column in the three tables of
+`docs/providers-existing.md` plus a kvm2 section and renumbering, the
+components row, §5 block, §10 span bullet, §11 row and eight Decisions
+bullets in `docs/architecture.md`, a README row and paragraph, and the
+guide in the `docs/providers.md` index. The agent verified each claim
+against the package rather than the spec and dropped a draft sentence
+claiming kvm and kvm2 share the base-image cache, because checking it would
+have meant reading v1's volume names.
+
+Checks re-run by the orchestrator: no em-dash in the guide, no line
+references, each of the 19 axis codes appears once in the appendix table
+with seven cells, every link and anchor across the seven touched documents
+resolves. The one added em-dash is the `Leader-elected` cell of the new
+components-table row, where the table's own convention wins.
+
+Attestation: "files read outside the allowed set: none".