mythik 0.1.5 → 0.2.0

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-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/package.json

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