Corrected agent confabulations

README.md

@@ -52,7 +52,7 @@ The surface every Mizan adapter implements.
 | Invalidation — JSON body | ✅ | ✅ | ✅ | ✅ | ✅ |
 | Invalidation auto-scoping (three-tier) | ✅ | ✅ | ✅ | ✅ | ✅ |
 | Function discovery / registration | ✅ | ✅ | ✅ | ✅ | ✅ |
-| Codegen IR export (KDL) | ✅ | ✅ | ✅ ⁶ | ✅ ⁶ | — ⁸ |
+| Codegen IR export (KDL) | ✅ | ✅ | ✅ ⁶ | ✅ ⁶ | ❌ ⁸ |
 | File uploads (multipart, `Upload` type) | ✅ | ✅ | ❌ ⁹ | ❌ ⁹ | — ¹⁰ |
 
 ### Edge, cache & enforcement
@@ -107,12 +107,14 @@ target stack calls for them.
    rather than fetching over HTTP.
 7. FastAPI and Rust/Axum expose `GET /session/` returning a null CSRF token for wire
    parity; CSRF is Django-only.
-8. TypeScript is an edge/protocol-reference adapter (HMAC cache, manifest, PSR), not a
-   codegen source — it demonstrates the cache + invalidation protocol is
-   language-agnostic.
-9. The IR carries the `upload` type and the codegen emits the field across targets, but
-   multipart dispatch binding is wired for Django and FastAPI only; Rust/Axum and Tauri
-   parse the IR node but do not yet bind uploads.
+8. `mizan-ts` emits the Edge manifest (JSON) but has no KDL IR emitter, so it can't yet
+   feed the codegen — an unbuilt gap. A TypeScript backend still needs the generated
+   client (types + `callXxx`/`fetchXxx` + framework hooks); same language doesn't remove
+   the need for it.
+9. The `mizan-codegen` crate parses the `upload` KDL node and emits the field across
+   targets (the Rust target lowers it to `Vec<u8>`). Multipart dispatch binding is wired
+   for Django and FastAPI only; the Rust/Axum and Tauri *adapters* have no upload concept
+   at dispatch yet.
 10. The TypeScript column is the `mizan-ts` backend adapter, which has no upload
     dispatch. The matching client side lives in the kernel (`@mizan/base`): `mizanCall`
     auto-switches to `multipart/form-data` when any argument is a `File`.