mythik 0.1.5 → 0.2.1

package/docs/wiki/compiled/concept-agent-context-protocol.md

@@ -0,0 +1,76 @@
+---
+id: concept-agent-context-protocol
+title: Mythik Agent Context and Agent Protocol
+kind: concept
+sources: [docs/consumer/ai-context.md#required-edit-loop-for-existing-specs, docs/consumer/ai-context.md#rule-100, docs/consumer/reference-doc.md#rule-297]
+---
+
+# Mythik Agent Context and Agent Protocol
+
+Mythik Agent Context is the project-specific operating map an AI agent
+reads before editing a Mythik app.
+
+Agent Protocol is the mandatory write discipline that keeps the agent
+on the validated Mythik workflow instead of drifting into full-spec
+rewrites, direct database edits, or stale local files.
+
+## Why it exists
+
+Fresh AI agents often know how to edit JSON but not how Mythik wants
+stored specs to be changed. The protocol makes the correct behavior
+local, explicit, and repeatable:
+
+- inspect stored structure with `manifest`
+- inspect exact target nodes with `elements`
+- write a small RFC 6902 patch file
+- apply with `patch --from-file --author`
+- validate
+- verify with `manifest`, `elements`, browser smoke, or Reveal
+
+## Store-backed source of truth
+
+For DB-backed Mythik projects, the active store is the source of
+truth. Local spec files are drafts, snapshots, migrations, backups, or
+fixtures. They are not the canonical document unless the project has
+intentionally configured a file store.
+
+This prevents the common failure where an agent patches the database
+correctly, then overwrites the result from an older local `spec.json`.
+
+## Strict write intent
+
+Persisted writes are strict by default:
+
+- Existing full-spec replacement requires `--replace`.
+- Normal persisted writes use `--author <name>`.
+- `--allow-unversioned` is only for intentionally unversioned stores.
+
+These guardrails preserve version history and make destructive writes
+explicit.
+
+## Relationship to Reveal
+
+Agent Protocol edits stored specs. Mythik Reveal inspects the running
+app.
+
+Use both:
+
+- `manifest` / `elements` / `patch` to change the stored contract.
+- `reveal current`, `reveal screen`, or `reveal element` to understand
+  runtime state, resolved props, warnings, render errors, and events
+  before guessing.
+
+## Related articles
+
+- [[@cli-agent]]
+- [[@cli-existing-spec-edit-loop]]
+- [[@cli-versioning-author]]
+- [[@cli-reveal]]
+- [[@concept-mythik-reveal]]
+- [[@concept-source-of-truth-references]]
+- [[@pattern-push-vs-patch]]
+
+## Sources
+
+- `docs/consumer/ai-context.md`
+- `docs/consumer/reference-doc.md`

package/docs/wiki/compiled/concept-component-variants.md

@@ -7,9 +7,17 @@ sources: [docs/consumer/ai-context.md#component-variants, docs/consumer/referenc
 
 # Component variants
 
-Token-driven component styling. Define variant definitions in
-`tokens.components.{primitiveType}.{variantName}`. The engine applies
-style, hover, active, focus, transition, animations automatically.
+Token-driven component styling. Define variant definitions in
+`tokens.components.{primitiveType}.{variantName}`. The engine applies
+style, hover, active, focus, transition, animations automatically.
+
+Use variants before copying the same visual style block into multiple
+elements. Variants are intentionally limited to primitive visual slots:
+`style`, `hover`, `active`, `focus`, `transition`, and `animations`.
+They do not carry arbitrary primitive props such as table `headerStyle`,
+table `rowStyle`, `columns`, `onRowClick`, action bindings, or child
+composition. Use [[@concept-templates-vs-variants]] when the repeated
+pattern needs those props.
 
 ## Defining
 
@@ -49,9 +57,28 @@ style, hover, active, focus, transition, animations automatically.
 `variant` is **universal** — any primitive can use it when defined in
 `tokens.components`.
 
-## Supported variant fields
-
-`style`, `hover`, `active`, `focus`, `transition`, `animations`.
+## Supported variant fields
+
+`style`, `hover`, `active`, `focus`, `transition`, `animations`.
+
+## Not supported inside primitive variants
+
+Do not put these in `tokens.components.{type}.{variant}` and expect the
+primitive to receive them:
+
+- `headerStyle` / `rowStyle` on `table`
+- `columns`, `pagination`, `selection`, `groupBy`, `onRowClick`
+- action bindings
+- composed children
+
+For reusable table chrome, put the surrounding card style in a `box`
+variant and wrap the `table` in an AppSpec template that passes
+`headerStyle`, `rowStyle`, `columns`, and actions through `$prop`.
+
+For filter chips composed from `touchable` + `text`, keep static shell
+and label styling in variants, then keep active `$state` / `$item`
+expressions on the actual elements. Variants do not evaluate render
+context expressions such as `$state`, `$item`, or `$prop` by themselves.
 
 ## `$path` references
 
@@ -70,10 +97,12 @@ Variant is base, element-level overrides — same as CSS class + inline
 override. Hover merges per-key (variant's `scale: 1.05` + element's
 `rotate: 5` both apply).
 
-## Constraints / Anti-patterns
-
-- **Place `variant` in `props`**, not as a top-level field. Top-level is
-  silently ignored. See [[@antipattern-element-variant-top-level]].
+## Constraints / Anti-patterns
+
+- **Place `variant` in `props`**, not as a top-level field. Top-level is
+  silently ignored. See [[@antipattern-element-variant-top-level]].
+- **Do not copy table chrome into every table.** Use a template for the
+  prop-bearing table defaults and a variant for the panel/card shell.
 
 ## Related concepts
 

package/docs/wiki/compiled/concept-mythik-reveal.md

@@ -0,0 +1,63 @@
+---
+id: concept-mythik-reveal
+title: Mythik Reveal - live runtime context for AI agents
+kind: concept
+sources: [docs/consumer/ai-context.md#mythik-reveal-live-context-for-ai-agents, docs/consumer/reference-doc.md#mythik-reveal--live-runtime-context-for-ai-agents]
+---
+
+# Mythik Reveal
+
+Mythik Reveal lets a running Mythik app expose its live contract, state,
+actions, diagnostics, environment, and render errors as structured
+context for AI agents.
+
+Reveal is for runtime truth. It complements the normal spec workflow:
+
+- `manifest` and `elements` read stored specs.
+- `lint` and `validate` check candidate specs.
+- `patch --from-file` writes validated changes.
+- Reveal reads the app that is actually running.
+
+Use Reveal before guessing when a runtime symptom is visible: a button
+does not fire, a screen renders the wrong branch, a dataSource fails,
+a render error appears, or React Native behaves differently from web.
+
+## What Reveal exposes
+
+Reveal context can include:
+
+- renderer and platform (`react`, `react-native`, `android`, etc.)
+- app and environment metadata
+- mounted spec summary
+- selected screen or element context
+- resolved public props and element dependency paths
+- selected state paths, with redaction
+- render errors and warnings
+- action, transaction, dataSource, navigation, lifecycle, and render
+  error events
+- patch target metadata when available
+- redaction and truncation metadata
+
+## Security contract
+
+Reveal is development tooling.
+
+- Do not enable it in production.
+- Do not commit or publish Reveal tokens.
+- Use narrow `includeStatePaths`.
+- Redact `/auth`, `/secrets`, tokens, passwords, API keys, and session
+  values.
+- Memoize React and React Native `reveal` config objects so bridge
+  clients stay stable across renders.
+
+## Related articles
+
+- [[@cli-reveal]]
+- [[@cli-existing-spec-edit-loop]]
+- [[@concept-debugging-runtime-pointers]]
+- [[@concept-render-error-visibility]]
+
+## Sources
+
+- `docs/consumer/ai-context.md`
+- `docs/consumer/reference-doc.md`

package/docs/wiki/compiled/concept-package-layout.md

@@ -13,12 +13,13 @@ sources: [docs/consumer/ai-context.md, docs/consumer/WHERE-TO-LOOK.md]
 |---|---|
 | `mythik` | Browser-safe core. State, expressions, validation, renderer engine, design, auth, data, security, and browser-safe spec stores |
 | `mythik/server` | Node-only spec stores, SQL drivers, and SQL DDL helpers: `FileSpecStore`, `SqlSpecStore`, `SqlVersionedSpecStore`, `SqlEnvironmentStore`, `createSqlDriver`, `getSqlStoreDdl`, and SQL Server compatibility stores |
-| `mythik-react` | React host, renderer, and web primitives |
-| `mythik-cli` | CLI package; installs the `mythik` command |
-| `mythik-cli/api` | Programmatic CLI API: `runPush`, `runPatch`, `runLint`, `parsePatchInput`, and types |
-| `mythik-server` | Express server runtime for ApiSpecs |
-
-React Native work lives in the repository as a preview track and is not part of the supported npm publish surface yet.
+| `mythik-react` | React host, renderer, and web primitives |
+| `mythik-react-native` | React Native and Expo renderer, public preview, with an explicit primitive support matrix |
+| `mythik-cli` | CLI package; installs the `mythik` command |
+| `mythik-cli/api` | Programmatic CLI API: `runPush`, `runPatch`, `runLint`, `parsePatchInput`, and types |
+| `mythik-server` | Express server runtime for ApiSpecs |
+
+`mythik-react-native` is published on the same version line as the rest of Mythik, but remains a public preview while native primitive parity and smoke coverage continue to expand.
 
 ## Browser vs server core entries
 

package/docs/wiki/compiled/concept-public-package-names.md

@@ -13,10 +13,11 @@ Mythik publishes unscoped npm packages. Do not generate scoped package imports f
 |---|---|
 | `mythik` | Browser-safe core runtime, state, expressions, validation, browser-safe stores |
 | `mythik/server` | Node-only stores, SQL drivers, and SQL DDL helpers exported from the core package subpath |
-| `mythik-react` | React host, renderer, and web primitives |
-| `mythik-cli` | CLI package; installs the `mythik` binary |
-| `mythik-cli/api` | Programmatic CLI API: `runPush`, `runPatch`, `runLint`, and related types |
-| `mythik-server` | Express server runtime for ApiSpecs |
+| `mythik-react` | React host, renderer, and web primitives |
+| `mythik-react-native` | React Native and Expo renderer, public preview, with an explicit primitive support matrix |
+| `mythik-cli` | CLI package; installs the `mythik` binary |
+| `mythik-cli/api` | Programmatic CLI API: `runPush`, `runPatch`, `runLint`, and related types |
+| `mythik-server` | Express server runtime for ApiSpecs |
 
 The `mythik` package also ships the AI documentation under `node_modules/mythik/docs`.
 Use [[@cli-docs]] to locate or copy it after install.
@@ -28,7 +29,10 @@ npm install mythik mythik-react
 npm install -D mythik-cli
 ```
 
-Add `mythik-server` only when building a Mythik-backed Node server. React Native work is a repository preview track, not part of the supported npm publish surface yet.
+Add `mythik-server` only when building a Mythik-backed Node server.
+For React Native and Expo, install `mythik mythik-react-native`; Expo
+apps should install native peer packages with `npx expo install ...`
+so Expo selects versions compatible with the app SDK.
 
 SQL adapters (`mssql`, `pg`, `mysql2`, `better-sqlite3`) are optional peer dependencies. Install only the selected database adapter:
 

package/docs/wiki/compiled/concept-shape-animations.md

@@ -29,8 +29,10 @@ useShapeAnimations(ref, animations, options)
 
 ## RN variant
 
-`packages/react-native/src/animation/useShapeAnimations.ts` — repository
-preview implementation. It is not part of the supported npm publish surface yet.
+`packages/react-native/src/animation/useShapeAnimations.ts` — internal
+implementation used by the public-preview native blob/background renderer.
+It is not exported from the `mythik-react-native` package root as a standalone
+public hook.
 
 ```ts
 useShapeAnimations(animations, options) → { animatedProps }

package/docs/wiki/compiled/concept-spec-store-interface.md

@@ -32,10 +32,13 @@ readers without breaking the consumer adapter contract.**
 
 ## Approved consumer paths (3 forms)
 
-Never call `SpecStore.save()` from app code. Use:
-- **Shell**: `mythik push <id> --from-file spec.json`
-- **Bulk**: `mythik push --from-dir <folder>`
-- **Programmatic**: `runPush` / `runPatch` from `mythik-cli/api`
+Never call `SpecStore.save()` from app code. Use:
+- **Shell**: `mythik push <id> --from-file spec.json --author <agent>` or `mythik patch <id> --from-file patch.json --author <agent>`
+- **Bulk**: `mythik push --from-dir <folder> --author <agent>`
+- **Programmatic**: `runPush` / `runPatch` from `mythik-cli/api` with `author`
+
+Existing full-spec replacement requires explicit `--replace`. Intentionally
+unversioned stores require explicit `--allow-unversioned`.
 
 See [[@cli-push]] + [[@antipattern-store-save-bypass]].
 

package/docs/wiki/compiled/concept-spec-store-layering.md

@@ -18,14 +18,14 @@ Understanding the layering prevents bypassing validation.
 | `store.saveVersion(id, doc, meta)` | **NO** | Versioned write. Writes to `screen_versions` and updates the current spec. |
 | `SpecEngine.patch(id, patches)` | **YES** | Applies RFC-6902 patches, validates through the document handler, and persists the patched document through `store.save`. |
 | `mythik push` / `runPush` | **YES** | Validates and writes through `saveVersion` when a versioned store + author are used. |
-| `mythik patch` / `runPatch` | **YES** | Uses `SpecEngine.patch` for patch application + validation. Without author, persists through `store.save`; with a versioned store + author, captures the patched document and writes once through `saveVersion`. |
+| `mythik patch` / `runPatch` | **YES** | Uses `SpecEngine.patch` for patch application + validation. With a versioned store + author, captures the patched document and writes once through `saveVersion`. Without author, persisted writes are rejected unless `--allow-unversioned` is explicit. |
 
 ## Consumer rule
 
-**Never call `store.save()` from application code.** Use:
-
-- `mythik push <id>` / `mythik patch <id> --from-file patch.json` for shell work.
-- `runPush` / `runPatch` from `mythik-cli/api` for programmatic work.
+**Never call `store.save()` from application code.** Use:
+
+- `mythik push <id> --from-file spec.json --author <agent>` / `mythik patch <id> --from-file patch.json --author <agent>` for shell work.
+- `runPush` / `runPatch` from `mythik-cli/api` with `author` for programmatic work.
 
 See [[@antipattern-store-save-bypass]] and [[@cli-lint]].
 

package/docs/wiki/compiled/concept-templates-vs-variants.md

@@ -11,19 +11,36 @@ Two underused reuse mechanisms. **Use them before duplicating style blocks.**
 
 ## Decision table
 
-| Situation | Pick |
-|---|---|
-| Same primitive type, different style set | `tokens.components.{type}.{variant}` |
-| Composite (custom type wrapping primitive + children slot) | `appSpec.templates` |
-| Style varies by state (hover/active/focus) | Variants (built-in state slots) |
-| Parametrized via props + children | Templates (with `$prop` + `$children`) |
+| Situation | Pick |
+|---|---|
+| Same primitive type, different style set | `tokens.components.{type}.{variant}` |
+| Primitive style plus repeated primitive props such as table `headerStyle` / `rowStyle` | `appSpec.templates` |
+| Composite (custom type wrapping primitive + children slot) | `appSpec.templates` |
+| Style varies by state (hover/active/focus) | Variants (built-in state slots) |
+| Parametrized via props + children | Templates (with `$prop` + `$children`) |
 
 ## Trade-off
 
-- **Variants are lightweight** and integrate natively with primitive
-  rendering. Prefer when you only vary style.
-- **Templates are more flexible** but more verbose. Use when you compose
-  structure (different children, parametrized props beyond style).
+- **Variants are lightweight** and integrate natively with primitive
+  rendering. Prefer when you only vary style, hover, active, focus,
+  transition, or animations.
+- **Templates are more flexible** but more verbose. Use when you compose
+  structure or need reusable primitive props beyond visual slots.
+
+## Important boundary
+
+`tokens.components` variants do not carry arbitrary primitive props.
+For example, a `table` variant is not the right place for `headerStyle`,
+`rowStyle`, `columns`, `pagination`, `selection`, `groupBy`, or
+`onRowClick`. Those are primitive props, not variant visual slots.
+
+Use a template when the repeated pattern needs those props:
+
+- `box.tableCard` variant for the shared panel shell.
+- `ops-table` template for the actual table with shared `headerStyle`
+  and `rowStyle`.
+- `$prop` pass-through for screen-specific `data`, `columns`, actions,
+  pagination, selection, grouping, and empty states.
 
 ## Example — variant (style-only)
 
@@ -60,9 +77,56 @@ Use: `{ "type": "button", "props": { "variant": "ctaPulse", "label": "..." } }`.
 }
 ```
 
-Use: `{ "type": "button-pulse-cta", "props": { "label": "Sign Up", "padding": "10px 20px" } }`.
-
-## Animations cascade across both
+Use: `{ "type": "button-pulse-cta", "props": { "label": "Sign Up", "padding": "10px 20px" } }`.
+
+## Example -> table chrome template
+
+```json
+{
+  "tokens": {
+    "components": {
+      "box": {
+        "tableCard": {
+          "style": {
+            "backgroundColor": "#FFFFFF",
+            "border": "1px solid #E2E8F0",
+            "borderRadius": 16,
+            "padding": 12
+          }
+        }
+      }
+    }
+  },
+  "templates": {
+    "ops-table": {
+      "type": "table",
+      "props": {
+        "data": { "$prop": "data" },
+        "columns": { "$prop": "columns" },
+        "headerStyle": { "minHeight": 44, "background": "#F8FAFC" },
+        "rowStyle": {
+          "base": { "minHeight": 43 },
+          "hover": { "backgroundColor": "#F8FAFC" }
+        },
+        "pagination": { "$prop": "pagination" },
+        "onRowClick": { "$prop": "onRowClick" }
+      }
+    }
+  }
+}
+```
+
+Use the card variant around the template:
+
+```json
+{
+  "type": "box",
+  "props": { "variant": "tableCard" },
+  "children": ["orders-table"]
+}
+```
+
+## Animations cascade across both
 
 `animations` declared at any of these levels merges via the cascade —
 identity → variant → elementDef → template → element. See

package/docs/wiki/compiled/concept-versioned-store.md

@@ -21,9 +21,11 @@ currentVersion(id): Promise<number>
 
 ## Activation
 
-`mythik push --author <name>` and `mythik patch --author <name>` activate
-versioning automatically. Without `--author`, commands work as before
-(no versioning).
+`mythik push --author <name>` and `mythik patch --author <name>` activate
+versioning automatically when the resolved store supports
+`saveVersion`. Without `--author`, persisted writes are rejected unless
+`--allow-unversioned` is explicit. Existing full-spec replacement
+requires `--replace`.
 
 ## Snapshots + patch chain
 
@@ -57,8 +59,9 @@ See `concept-customize-versioned-store.md` for the recipe.
 - [[@cli-versioning-author]]
 - [[@cli-history]]
 - [[@concept-rollback]]
-- [[@concept-environment-store]]
-- [[@concept-customize-versioned-store]]
+- [[@concept-environment-store]]
+- [[@concept-customize-versioned-store]]
+- [[@concept-agent-context-protocol]]
 
 ## Sources (raw)
 

package/docs/wiki/compiled/pattern-git-vs-db-versioning.md

@@ -9,12 +9,14 @@ sources: [docs/consumer/ai-context-runtime-semantics.md#62-git-backed-vs-db-vers
 
 Two history models — pick one per project.
 
-## Git-backed history
-
-- Specs in repo, `git log` + `git blame` serve as audit trail.
-- No `--author` flag needed on push/patch.
-- CLI writes via `store.save` (unversioned path).
-- **Best for**: single-env apps, dev-loop iteration, specs-as-code.
+## Git-backed history
+
+- Specs in repo, `git log` + `git blame` serve as audit trail.
+- Persisted CLI writes must still be explicit: use `--author <name>`
+  when the resolved store supports versioning, or `--allow-unversioned`
+  only when the project intentionally uses a non-versioned store.
+- CLI writes via `store.save` only on the explicit unversioned path.
+- **Best for**: single-env apps, dev-loop iteration, specs-as-code.
 
 ## DB-versioned history
 

package/docs/wiki/compiled/pattern-push-vs-patch.md

@@ -10,18 +10,19 @@ sources: [docs/consumer/ai-context-runtime-semantics.md#61-push-vs-patch--file-f
 Two paradigms for modifying specs. Pick one per project; mixing creates
 issues.
 
-## Push paradigm (file-first)
-
-- Specs live in git under `specs/*.json`.
-- Modify locally, then run `mythik push <id>`.
-- Diff-reviewable in CI through normal JSON file diffs.
-- Full-spec bandwidth cost per write.
-
-## Patch paradigm (DB-first)
-
-- Specs live in the DB; local files are optional working snapshots.
-- Modify via `mythik patch <id> --from-file patch.json` for shell-safe
-  surgical writes.
+## Push paradigm (file-first)
+
+- Specs live in git under `specs/*.json`.
+- Modify locally, lint, then run `mythik push <id> --from-file spec.json --author <agent>`.
+- Existing persisted specs require explicit `--replace` for full replacement.
+- Diff-reviewable in CI through normal JSON file diffs.
+- Full-spec bandwidth cost per write.
+
+## Patch paradigm (DB-first)
+
+- Specs live in the DB; local files are optional working snapshots.
+- Modify via `mythik patch <id> --from-file patch.json --author <agent>` for shell-safe
+  surgical writes.
 - Requires `mythik pull <id>` to refresh any local `specs/*.json` snapshot
   after a DB patch.
 

package/docs/wiki/compiled/pattern-reusable-components.md

@@ -12,12 +12,13 @@ style blocks.**
 
 ## Decision
 
-| Need | Pick |
-|---|---|
-| Same primitive type, different style set | `tokens.components.{type}.{variant}` |
-| Composite (custom type wrapping primitive + children slot) | `appSpec.templates` |
-| Style varies by state (hover/active/focus) | Variants (built-in state slots) |
-| Parametrized via props + children | Templates (with `$prop` + `$children`) |
+| Need | Pick |
+|---|---|
+| Same primitive type, different style set | `tokens.components.{type}.{variant}` |
+| Primitive style plus repeated primitive props such as table `headerStyle` / `rowStyle` | `appSpec.templates` |
+| Composite (custom type wrapping primitive + children slot) | `appSpec.templates` |
+| Style varies by state (hover/active/focus) | Variants (built-in state slots) |
+| Parametrized via props + children | Templates (with `$prop` + `$children`) |
 
 See [[@concept-templates-vs-variants]] for the full decision walk-through.
 
@@ -35,7 +36,22 @@ If the same rich style object appears in 2+ specs (or 2+ places in same
 spec), extract to a template or variant. Duplication inflates DB storage,
 breaks DRY, makes updates O(N).
 
-See [[@antipattern-style-block-duplication]].
+See [[@antipattern-style-block-duplication]].
+
+## Boundary: style reuse vs prop-bearing reuse
+
+Variants cover primitive visual slots only: `style`, `hover`, `active`,
+`focus`, `transition`, and `animations`. Do not use variants for table
+`headerStyle`, table `rowStyle`, `columns`, `onRowClick`, action bindings,
+or composed children.
+
+Use both mechanisms together when needed:
+
+- `tokens.components.box.tableCard` for a repeated table panel shell.
+- `appSpec.templates.ops-table` for the table itself, including shared
+  `headerStyle` / `rowStyle` and `$prop` pass-through.
+- static `touchable` / `text` variants for filter chip shell and label
+  style, with active `$state` / `$item` styling kept on the actual elements.
 
 ## Right approach — extract once
 
@@ -43,11 +59,25 @@ See [[@antipattern-style-block-duplication]].
 // appSpec.templates once
 { "templates": { "button-pulse-cta": { ...full definition... } } }
 
-// both screens
-{ "type": "button-pulse-cta", "props": { "label": "..." } }
-```
-
-## Animations cascade across BOTH mechanisms
+// both screens
+{ "type": "button-pulse-cta", "props": { "label": "..." } }
+```
+
+For repeated table chrome:
+
+```json
+// appSpec tokens once
+{ "tokens": { "components": { "box": { "tableCard": { "style": { "...": "..." } } } } } }
+
+// appSpec template once
+{ "templates": { "ops-table": { "type": "table", "props": { "headerStyle": { "...": "..." }, "rowStyle": { "...": "..." }, "columns": { "$prop": "columns" }, "data": { "$prop": "data" } } } } }
+
+// each screen
+{ "type": "box", "props": { "variant": "tableCard" }, "children": ["orders-table"] }
+{ "type": "ops-table", "props": { "data": { "$state": "/orders" }, "columns": [...] } }
+```
+
+## Animations cascade across BOTH mechanisms
 
 `animations` declared at any of these levels merges via the cascade —
 identity → variant → template → element — with per-trigger null semantics.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mythik",
-  "version": "0.1.5",
+  "version": "0.2.1",
   "description": "AI-first JSON-native core runtime for validated applications, APIs, editor sessions, state, actions, validation, and versioning.",
   "license": "Apache-2.0",
   "type": "module",