@zenera/faker 1.1.14 → 1.1.16

package/README.md

@@ -4,6 +4,7 @@
   <img src="https://raw.githubusercontent.com/andreyryabov/ZeneraNeo/main/docs/imgs/banner-faker-light.svg" alt="ZENERA FAKER" width="837">
 </picture>
 
+[![npm](https://img.shields.io/npm/v/@zenera/faker.svg)](https://www.npmjs.com/package/@zenera/faker)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/andreyryabov/ZeneraNeo/blob/main/LICENSE)
 [![Node](https://img.shields.io/badge/node-%E2%89%A524-brightgreen.svg)](https://nodejs.org)
 
@@ -12,7 +13,7 @@
 # @zenera/faker
 
 **A mock HTTP server for swagger/OpenAPI documents. Point it at a spec and it
-serves it — the response bodies are written, once, by a model.**
+serves it - the response bodies are written, once, by a model.**
 
 > Part of [ZeneraNeo](https://github.com/andreyryabov/ZeneraNeo). It ships no
 > binary of its own: installing it adds a `faker` **subcommand** to
@@ -59,7 +60,7 @@ zen faker cache clear                # throw it away
 ## How a body is produced
 
 The first time an operation is called, the faker asks a model to write a
-**Python generator** for it — one file, taking a JSON input path and a JSON
+**Python generator** for it - one file, taking a JSON input path and a JSON
 output path. That file is then run against sample requests it makes up, and
 judged twice: against the operation's response schema, and against the echo
 rule, which says that where a path or query parameter shares a name with a
@@ -70,7 +71,7 @@ and is still wrong.
 If it fails, the diagnostics go back to the model and it tries again, up to
 `--attempts`. If it passes, the generator is kept in this machine's shared cache
 under `~/.zenera/neo/cache/faker-generator/`, keyed by the operation's shape, and
-every later request is just `podman exec python3 gen.py in.json out.json` — no
+every later request is just `podman exec python3 gen.py in.json out.json` - no
 model, no tokens. The store is the machine's, so the same document served from
 another directory costs nothing the second time.
 
@@ -81,7 +82,7 @@ Generators run in a container with **no network**, on an image baked once with
 
 A list endpoint is the one place a mock can hang a real client. Given
 `?cursor=abc`, the honest-looking answer is a body that validates, echoes
-nothing it shouldn't, and hands back `abc` again — so the client asks for the
+nothing it shouldn't, and hands back `abc` again - so the client asks for the
 same page forever.
 
 The faker reads the document for this. Where an operation has a paging
@@ -90,13 +91,13 @@ that carries the next one (`next`, `next_cursor`, `has_more`, …), three things
 happen, all in the operation's own names:
 
 - the model is told to fabricate **three pages** in total, to build the token
-  out of the paging parameter rather than the seed, and to end the list — null,
+  out of the paging parameter rather than the seed, and to end the list - null,
   absent, or `has_more: false` where the schema leaves no other room;
 - the generator is then **walked**: the faker calls it with no cursor, follows
   the token it gets back, and rejects the file if the token repeats, cycles, or
   never runs out. The diagnostics say which, and the model gets another go;
-- at request time a token identical to the one just sent is **cut** — nulled or
-  dropped, whichever the schema allows — and the request line says so. Nothing
+- at request time a token identical to the one just sent is **cut** - nulled or
+  dropped, whichever the schema allows - and the request line says so. Nothing
   is invented in its place; a generator written before this rule existed is
   still cached, and a cache is not rebuilt because a rule changed.
 
@@ -105,8 +106,8 @@ are written again on first use; everything else keeps the key it had.
 `GET /__faker/routes` reports the shape that was recognised, per operation.
 
 Plenty of documents describe the envelope and never write down the parameter
-that reads it back. The first two steps cannot help there — nothing static can
-see a parameter that is not declared — but the cut still applies: it takes the
+that reads it back. The first two steps cannot help there - nothing static can
+see a parameter that is not declared - but the cut still applies: it takes the
 paging parameter from the request itself, since a client only sends `?cursor=X`
 because a body handed it X.
 
@@ -141,9 +142,9 @@ Environment variables still win over the keyring, exactly as they do for `zen`.
 
 | Package                                                                                     | What it is                                           |
 | ------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
-| [`@zenera/cli`](https://github.com/andreyryabov/ZeneraNeo/blob/main/packages/cli/README.md) | `zen` — agent projects on the command line           |
-| [`@zenera/neo`](https://github.com/andreyryabov/ZeneraNeo/blob/main/packages/neo/README.md) | the runtime — agents, models, tools, skills, memory  |
-| [`@zenera/rag`](https://github.com/andreyryabov/ZeneraNeo/blob/main/packages/rag/README.md) | `zen rag` — an API description as a searchable graph |
+| [`@zenera/cli`](https://github.com/andreyryabov/ZeneraNeo/blob/main/packages/cli/README.md) | `zen` - agent projects on the command line           |
+| [`@zenera/neo`](https://github.com/andreyryabov/ZeneraNeo/blob/main/packages/neo/README.md) | the runtime - agents, models, tools, skills, memory  |
+| [`@zenera/rag`](https://github.com/andreyryabov/ZeneraNeo/blob/main/packages/rag/README.md) | `zen rag` - an API description as a searchable graph |
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@zenera/faker",
-    "version": "1.1.14",
+    "version": "1.1.16",
     "description": "Mock HTTP server for swagger/OpenAPI documents, with response bodies generated by a model.",
     "keywords": [
         "openapi",
@@ -45,7 +45,7 @@
         "@apidevtools/swagger-parser": "^12.0.0",
         "ajv": "^8.17.1",
         "ajv-formats": "^3.0.1",
-        "@zenera/cli": "^1.1.14",
-        "@zenera/neo": "^1.1.14"
+        "@zenera/cli": "^1.1.16",
+        "@zenera/neo": "^1.1.16"
     }
 }