Catch missed content edits from tree restructure

The fe39fcb commit captured the file moves (git mv stages those automatically)
but didn't catch the content edits I made afterward — npm package rename
(@mizan/runtime → @mizan/base), path updates in Makefile/Dockerfile/examples,
and doc updates were all left unstaged at commit time.

This commit lands those:
- npm rename: 3 frontend package.jsons (base/vue/svelte) + mizan-base/src/index.ts + 4 codegen templates
- path updates: Makefile, Dockerfile.test, two Gitea workflows, four example/harness configs
- doc updates: CLAUDE.md, ROADMAP.md, ISSUES.md, docs/AFI_ARCHITECTURE.md

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

ISSUES.md

@@ -24,7 +24,7 @@ Identified by domain expert review (Cloudflare, Serverless, Vercel, React Query,
 ## Remaining Critical
 
 ### C6. No loading/error/stale states in runtime
-**File:** `mizan-runtime/src/index.ts`
+**File:** `mizan-base/src/index.ts`
 The kernel stores only `{params, refetch}`. No `data`, `status`, `error`. Every adapter reinvents loading tracking. Blocks stale-while-revalidate.
 
 ## Remaining High
@@ -103,7 +103,7 @@ Context listeners called inside `setContextStore()` updater.
 
 ### A1. Legacy MizanProvider not yet removed
 **File:** `mizan-react/src/context.tsx` (~750 lines)
-Superseded by the kernel (`mizan-runtime`) + generated React adapter (`useSyncExternalStore`). Still exported as `MizanProvider`, `useMizan`, `useMizanContext`, etc. Must be deleted or replaced with thin shims that call `configure()` + delegate to the new generated hooks.
+Superseded by the kernel (`mizan-base`) + generated React adapter (`useSyncExternalStore`). Still exported as `MizanProvider`, `useMizan`, `useMizanContext`, etc. Must be deleted or replaced with thin shims that call `configure()` + delegate to the new generated hooks.
 
 ### A2. Allauth pending extraction
 **File:** `legacy/allauth/` (44 files)
@@ -131,7 +131,7 @@ Written before the kernel rewrite. References to MizanProvider responsibilities
 ## Test Coverage Gaps
 
 ### T1. No tests for C6 kernel state machine
-**File:** `mizan-runtime/` has no `tests/` directory at all
+**File:** `mizan-base/` has no `tests/` directory at all
 The state-owning kernel has zero unit tests. No coverage of:
 - `registerContext` returning `getState/subscribe/refetch/unregister`
 - Status transitions: idle → loading → success/error