A channel's message slots are named from the client, on every backend

The IR called them react-message and django-message, so a FastAPI channel had
to declare a DjangoMessage. They are client-message and server-message now,
and the direction words hold wherever a channel is declared: Params /
ClientMessage / ServerMessage, with mizan-core deriving <Pascal>Params and
friends so no backend names a type itself. Django's ReactChannel and
FastAPI's ReactChannel are both Channel.

mizan-fastapi never registered a channels extension, so build_ir() emitted no
channel at all and every payload type was invisible to codegen. It registers
one now. RegistryExtension is an ABC requiring all(), which is what the IR
reads — an extension that cannot enumerate its registrations no longer exists.

The gate that should have caught the rename could not: tests/afi registered no
channel because mizan-rust had no channel registry to register one in, so a
five-package rename of the wire contract passed byte-parity without a channel
byte crossing it. mizan-rust grows ChannelSlotKind, a CHANNELS slice, a
#[mizan::channel] macro, and KDL emission whose wire_to_pascal matches Python's
split; the AFI fixture now carries a channel with every slot and one with a
single slot, so all three backends prove the contract byte for byte.

MizanChannel held three Option<String> beside three has_*() predicates and
unwrapped them with defaults; it holds an ordered slot vector, so an absent
slot is absent rather than defaulted. The channels target emitted a React
hooks file that a stage1-only consumer could not compile — react emits that
now. The codegen's parity tests byte-compared emitted source against baselines
without ever compiling it: they compile the generated crate and run its tests,
import the generated Python package and call every method, and typecheck each
TypeScript target against a consumer.

Also fixed at source: app_visitor printed its import diagnostic to stdout, the
stream export_mizan_ir writes KDL to, so a failed import silently corrupted the
IR; the apps root was hardcoded to "apps"; _default_literal crashed build_ir on
any non-JSON-serializable field default; Django and mizan-core derived Pascal
names two different ways, disagreeing on every dotted channel name.

ir.py builds a document and renders templates/ir/document.kdl.j2 rather than
appending KDL strings with hand-tracked indentation, and named types resolve to
a fixed point — a model reachable only through a union branch was referenced by
a ref that no type block ever defined.

The rest is the write-gate's own classifiers run over the standing tree:
relative imports, silent swallows, Protocol contracts that should be ABCs,
emitters hand-rendering target source, catch-all arms over closed enums, and
comments narrating the project rather than the code.

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

cores/mizan-rust-ssr/tests/no_rsc.rs

@@ -1,29 +1,19 @@
-//! Guard — Mizan SSR is hand-rolled (bare renderer + AFI data injection +
-//! injected kernel). No frontend adapter imports an SSR runtime / meta-framework
-//! (Next, Nuxt, SvelteKit) or a server-functions layer (RSC / Flight).
-//!
-//! React Server Components and the Flight serialization protocol carry
-//! CVE-2025-55182 ("React2Shell" — unauthenticated remote code execution,
-//! CVSS 10.0): the server deserializes a client-supplied Flight payload and an
-//! attacker reaches prototype-pollution → RCE.
-//!
-//! Mizan renders **synchronously from props** — data is fetched server-side
-//! through the AFI and passed in, never deserialized from a client payload — so
-//! it sits structurally outside that attack surface. This test keeps it there:
-//! it goes red the instant any RSC / Flight / streaming surface enters the
-//! authored SSR source or its dependencies. Absence is not enough; this is the
-//! forcing function that makes re-entry loud.
+//! Scans the SSR fixture's authored JS for tokens that only appear when React
+//! Server Components, the Flight protocol, or a meta-framework SSR runtime is
+//! in play. The scan goes red the moment one of them enters the source.
+
+use std::path::Path;
 
 /// Tokens that only appear when RSC / Flight / streaming rendering is in play.
 const FORBIDDEN: &[&str] = &[
-    // React Server Components / Flight — CVE-2025-55182 (pre-auth RCE, CVSS 10.0)
+    // React Server Components / Flight
     "react-server-dom",
     "renderToReadableStream",
     "renderToPipeableStream",
     "createFromReadableStream",
     "createFromFetch",
     "use server",
-    // SSR runtimes / meta-frameworks — forbidden across every frontend adapter
+    // SSR runtimes / meta-frameworks
     "next/",
     "nuxt",
     "@sveltejs/kit",
@@ -39,15 +29,16 @@ const SCANNED: &[&str] = &[
 #[test]
 fn ssr_has_no_rsc_or_flight_surface() {
     for path in SCANNED {
-        let Ok(src) = std::fs::read_to_string(path) else {
-            continue; // a generated/optional file absent is fine; authored source is the point
-        };
+        assert!(
+            Path::new(path).is_file(),
+            "{path} is a tracked fixture this scan reads; it is missing",
+        );
+        let src = std::fs::read_to_string(path)
+            .unwrap_or_else(|e| panic!("reading {path} for the RSC scan: {e}"));
         for needle in FORBIDDEN {
             assert!(
                 !src.contains(needle),
-                "RSC/Flight surface {needle:?} found in {path} — forbidden. \
-                 RSC carries CVE-2025-55182 (unauth RCE, CVSS 10.0); Mizan SSR is \
-                 classic renderToString-family only, rendered synchronously from props.",
+                "{needle:?} found in {path}; this scan forbids it",
             );
         }
     }