@reticlehq/vite-plugin 3.1.0 → 3.2.0

package/dist/index.cjs

@@ -4213,7 +4213,42 @@ var ReticleEnv = {
   /** Base URL for the harness's model API, for a proxy or a gateway. */
   HARNESS_BASE_URL: "RETICLE_HARNESS_BASE_URL",
   /** Hard ceiling on harness model turns in one drive. Bounds cost, not value. */
-  HARNESS_MAX_STEPS: "RETICLE_HARNESS_MAX_STEPS"
+  HARNESS_MAX_STEPS: "RETICLE_HARNESS_MAX_STEPS",
+  /**
+   * Which model backs the harness driver: `anthropic` (the default) or `jev`.
+   *
+   * Two drivers exist because the driver's job turns out not to need a text generator. It picks the
+   * next action and says what it expects; the verdict is decided afterwards by the engine, with no
+   * model anywhere near it. A System One model answers typed questions against a state, which is
+   * exactly that job and none of the rest, so it can drive without being able to generate a
+   * sentence. Unset keeps the existing behaviour for everybody who has not asked for this.
+   */
+  HARNESS_DRIVER: "RETICLE_HARNESS_DRIVER",
+  /**
+   * A direct Jev key, for this repo's own benchmarks and for anyone holding a TypeSafe account.
+   *
+   * Users are not expected to have one. The ordinary path is the key they already minted on the
+   * platform (`RETICLE_API_KEY`), which reaches Jev through the proxy at `RETICLE_CLOUD_URL` —
+   * this variable is the escape hatch that skips it, and it takes precedence when both are set so
+   * that a developer debugging the upstream is never silently talking to the proxy instead.
+   */
+  HARNESS_JEV_KEY: "JEV_API_KEY",
+  /** Base URL for the Jev API, for a proxy or a gateway. Defaults to TypeSafe's own endpoint. */
+  HARNESS_JEV_URL: "RETICLE_HARNESS_JEV_URL",
+  /** A direct OpenAI key. As with Jev, the ordinary path is the platform key and its proxy. */
+  HARNESS_OPENAI_KEY: "OPENAI_API_KEY",
+  /** Model the OpenAI driver uses. Defaults to a small one — see `DEFAULT_OPENAI_MODEL`. */
+  HARNESS_OPENAI_MODEL: "RETICLE_HARNESS_OPENAI_MODEL",
+  /**
+   * The API key minted on the platform, and the host it belongs to.
+   *
+   * Read through `apiKeyFrom()`, never directly — see the note on that function for why there are
+   * two names for one key and why neither may be dropped.
+   */
+  API_KEY: "RETICLE_API_KEY",
+  /** The name this key had until 2026-09. Still honoured; see `apiKeyFrom()`. */
+  CLOUD_KEY: "RETICLE_CLOUD_KEY",
+  CLOUD_URL: "RETICLE_CLOUD_URL"
 };
 var TRANSPORT_LIMITS = {
   MAX_MESSAGE_BYTES: 1024 * 1024,
@@ -4290,6 +4325,24 @@ var ReticleDir = {
   IMPACT_FILE: "impact.json",
   /** what changes were SUPPOSED to make true —.reticle/intent.json (git-checked, reviewed) */
   INTENT_FILE: "intent.json",
+  /**
+   * The sharded form of the same ledger —.reticle/intent/ (git-checked, for the same reason).
+   *
+   * Named here rather than inline at the store that writes it, because the partition guard over
+   * this object is what decides whether a name Reticle creates is committed or ignored. A directory
+   * spelled as a free string somewhere else is one the guard cannot see, so nobody ever makes that
+   * decision: `intent/` was written into users' repositories for that reason alone, neither
+   * classified nor ignored.
+   */
+  INTENT_SUBDIR: "intent",
+  /**
+   * what a drive types into a field, keyed by the field's label —.reticle/fill-values.json.
+   *
+   * Git-checked on purpose. A generated value is paid for once and then belongs to the project: the
+   * next drive reuses it for free, a replay sends exactly what the recording sent, and a human who
+   * dislikes one can edit the file rather than argue with a model.
+   */
+  FILL_VALUES_FILE: "fill-values.json",
   /** opt-in pixel baselines —.reticle/visual/<name>.png + <name>.diff.png. */
   VISUAL_SUBDIR: "visual",
   /** verification-run artifacts —.reticle/runs/<runId>.json (the OEM/CI-consumable verdict). */
@@ -4302,6 +4355,15 @@ var ReticleDir = {
   JOURNAL_EVENTS_FILE: "events.jsonl",
   /** append-only action ledger inside a session dir (one JournalAction per line). */
   JOURNAL_ACTIONS_FILE: "actions.jsonl",
+  /**
+   * the event ledger's closure report — .reticle/sessions/<id>/events.closed.json.
+   *
+   * Written once, when the byte ceiling refuses a batch, and never removed. Its PRESENCE is what
+   * makes the ceiling durable: a session id survives a reload, so the next connection reopens the
+   * same ledger with an empty memory, and a bound that lives only in one object's field is a bound
+   * per connection. Its CONTENTS are the loss report a time-windowed query cannot filter away.
+   */
+  JOURNAL_EVENTS_CLOSED_FILE: "events.closed.json",
   /** learned expected-envelopes per route, accumulated across runs (the deviation-report baseline). */
   ENVELOPES_FILE: "envelopes.json",
   /** learned ambient (action-less churn) region map — excluded from settle/summaries/envelopes. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reticlehq/vite-plugin",
-  "version": "3.1.0",
+  "version": "3.2.0",
   "description": "Vite plugin for Reticle: dev-only source-map stamping plus auto-injected reticle.connect(). apply:'serve' guarantees it never ships to production.",
   "type": "module",
   "license": "Apache-2.0",
@@ -41,15 +41,15 @@
   ],
   "dependencies": {
     "@babel/core": "^7.26.0",
-    "@reticlehq/babel-plugin": "3.1.0",
-    "@reticlehq/core": "3.1.0"
+    "@reticlehq/babel-plugin": "3.2.0",
+    "@reticlehq/core": "3.2.0"
   },
   "devDependencies": {
     "@types/babel__core": "^7.20.5",
     "esbuild": "^0.28.2",
     "svelte": "^5.56.10",
     "vite": "^8",
-    "@reticlehq/react": "3.1.0"
+    "@reticlehq/react": "3.2.0"
   },
   "peerDependencies": {
     "vite": ">=4"