Docs carry the shape of the system, not its status

MIZAN.md's phase-numbered implementation order, PRODUCT_ARCHITECTURE's
"Deferred until Render revenue funds it" and "Shipped in", PSR_VS_EDGE's
current-state section, and the READMEs' passing-test counts were all reporting
where the work stood rather than what the system is. OWED_SURFACE keeps its
subject — surface that is specified but unbuilt — stated as the shape each unit
owes.

The channel sections follow the renamed slots: Params / ClientMessage /
ServerMessage, and Channel as the base class on both backends.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

backends/mizan-tauri/README.md

@@ -215,11 +215,11 @@ const greeting = await callGreet({ name: "world" });
 console.log(greeting.message);
 ```
 
-For framework hooks generated by Stage 2 (`useGreet()` etc., wrapping the
-imperative `callGreet` with `isPending`/`error` state), wrap your tree
-with `<MizanContext>` at the root — same as the HTTP-transport setup. The
-generated provider is transport-agnostic; it reads from `config.transport`
-the kernel is using.
+For the framework hooks the `react` target generates (`useGreet()` etc.,
+wrapping the imperative `callGreet` with `isPending`/`error` state), wrap
+your tree with `<MizanContext>` at the root — same as the HTTP-transport
+setup. The generated provider is transport-agnostic; it reads from
+`config.transport` the kernel is using.
 
 ### tsconfig / vite preserve symlinks
 
@@ -273,12 +273,6 @@ Errors flow through Tauri's `Promise.reject` path; `@mizan/tauri-transport`
 re-wraps them into the same `MizanError` shape the HTTP transport
 produces, so consumer code is identical regardless of transport.
 
-## Reference application
-
-`claude-manage` is the production reference — Tauri + React + Pydantic
-schema + Mizan RPC. See `~/dev/claude-manage/mizan.toml` and
-`~/dev/claude-manage/src-tauri/src/commands.rs` for a full migrated app.
-
 ## Architecture
 
 mizan-tauri shares `cores/mizan-rust` with `mizan-rust-axum`. Both