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>
This commit is contained in:
32
CLAUDE.md
32
CLAUDE.md
@@ -10,23 +10,21 @@ Django + React ships first. The protocol is language-agnostic (proven by mizan-t
|
||||
|
||||
## Package Layout
|
||||
|
||||
Two layers per side. Per-framework adapters wrap a single shared kernel; codegen targets the adapter.
|
||||
Tree organized by role. Per-framework adapters wrap a single shared kernel; codegen targets the adapter.
|
||||
|
||||
**Backend protocol adapters** — implement the wire protocol on a server stack:
|
||||
|
||||
- `mizan-django/` — Django adapter
|
||||
- `mizan-ts/` — TypeScript adapter (proves the protocol is language-agnostic)
|
||||
|
||||
**Frontend kernel + framework adapters** — kernel is the imperative client primitive set; each framework adapter wraps the kernel in its own idiomatic constructs:
|
||||
|
||||
- `mizan-runtime/` — 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
|
||||
|
||||
**SSR worker:**
|
||||
|
||||
- `mizan-ssr/` — Bun subprocess used by the Django template backend
|
||||
```
|
||||
backends/ server protocol adapters
|
||||
mizan-django/ Django adapter
|
||||
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)
|
||||
workers/ runtime workers / bridges
|
||||
mizan-ssr/ Bun subprocess used by the Django template backend
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
@@ -444,7 +442,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-runtime` kernel.
|
||||
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.
|
||||
|
||||
**What's in place:**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user