2 Commits

Author	SHA1	Message	Date
Ryth Azhur	8aa20111b4	Add X-Mizan-Invalidate header (second invalidation transport) ... Mutation responses now carry invalidation via two transports: 1. JSON body: {"result": ..., "invalidate": ["user"]} 2. HTTP header: X-Mizan-Invalidate: user, notifications Both are set on every mutation response. The JSON body is consumed by the client runtime (mizanCall). The header is consumed by Edge for CDN cache purging and by XHR responses for htmx-style apps. Header format: comma-separated contexts, semicolon-separated params. X-Mizan-Invalidate: user;user_id=5, notifications Also: _resolve_invalidation and _format_invalidate_header extracted as reusable helpers for when return-type branching adds HttpResponse support (view-path mutations will only use the header transport). Updated ROADMAP.md with full v1 plan including both transports, return-type branching, affects_params, and Edge manifest. 270 Django tests pass. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-06 15:41:31 -04:00
Ryth Azhur	f4d7c64e3c	Add CDN-ready headers, ROADMAP, fold runtime into mizan-react ... CDN headers on context GETs (Edge-ready): - Cache-Control: public, max-age=0, stale-while-revalidate=300 - Vary: Authorization, Cookie - Deterministic JSON (sorted keys) for consistent cache keys - Error responses: Cache-Control: no-store - Mutation POSTs: Cache-Control: no-store ROADMAP.md documents v1 deliverables and Mizan Cloud (Edge, Render, Deploy) as closed-source products built on the open-source protocol. mizan-runtime folded into mizan-react/src/runtime/ — framework-agnostic split deferred until a second frontend adapter exists. 268 Django + 33 React tests pass. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-06 15:41:31 -04:00