Move codegen out of mizan-django: protocol/mizan-generate/

The codegen consumes a schema from any backend and emits typed client
code for any frontend — it doesn't belong inside a backend adapter.
That placement was historical sediment from when there was only a
Django backend; it predates the AFI generalization.

New top-level slot: `protocol/` for protocol-level tooling. Tree is
now:

  backends/    server protocol adapters
  frontends/   client kernel + per-framework adapters
  cores/       shared language-level primitives
  protocol/    protocol-level tooling
  workers/     runtime workers / bridges

Codegen moves to `protocol/mizan-generate/`. Same file layout under
`generator/` (cli.mjs, lib/), preserved via git mv.

Package metadata cleaned up:
- name: "generate" (placeholder) → "mizan-generate"
- description filled in
- type: module (cli.mjs is .mjs ESM, was previously declared "commonjs")
- bin entry added so `npx mizan-generate --config <config.mjs>` works
  once the package is published, instead of `node path/to/cli.mjs`.

Path-reference fixups:
- backends/mizan-django/README.md: `node path/to/...` → `npx mizan-generate`
- backends/mizan-fastapi/README.md: same
- ISSUES.md: file paths in three issue entries
- CLAUDE.md: codegen description + Package Layout section refreshed
  (added protocol/, mizan-fastapi entry, mizan-python entry)
- docs/AFI_ARCHITECTURE.md: Package Layout refreshed identically

Verified codegen runs from new location: regenerated the FastAPI
example harness's api/ output, identical to pre-move.

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

CLAUDE.md

@@ -15,13 +15,17 @@ Tree organized by role. Per-framework adapters wrap a single shared kernel; code
 ```
 backends/         server protocol adapters
     mizan-django/    Django adapter
+    mizan-fastapi/   FastAPI adapter (RPC + context + invalidation; AFI-common scope)
     mizan-ts/        TypeScript adapter (proves the protocol is language-agnostic)
 frontends/        client kernel + per-framework adapters
     mizan-base/      framework-agnostic kernel; owns data, status, error; adapters subscribe
     mizan-react/     React contexts + hooks over the kernel
     mizan-vue/       Vue composables over the kernel
     mizan-svelte/    Svelte stores/runes over the kernel
-cores/            shared language-level primitives (currently empty; mizan-python forthcoming)
+cores/            shared language-level primitives
+    mizan-python/    @client decorator, registry, MWT, HMAC cache keys; consumed by both Python backends
+protocol/         protocol-level tooling
+    mizan-generate/  codegen — fetches schema from any backend, emits typed React/Vue/Svelte client
 workers/          runtime workers / bridges
     mizan-ssr/       Bun subprocess used by the Django template backend
 ```
@@ -442,7 +446,7 @@ urlpatterns = [
 
 ## Codegen — Current State
 
-The codegen is two-stage and per-framework. Stage 1 (in `mizan-django/generate/`) emits the framework-agnostic protocol layer (`callXxx` for mutations, `fetchXxx` for context bundles, types). Stage 2 emits per-framework hooks/composables/stores that subscribe to the `mizan-base` kernel.
+The codegen is `protocol/mizan-generate/` — framework-agnostic, two-stage. Stage 1 emits the protocol layer (`callXxx` for mutations, `fetchXxx` for context bundles, types). Stage 2 emits per-framework hooks/composables/stores that subscribe to the `mizan-base` kernel.
 
 **What's in place:**