diff --git a/README.md b/README.md index 0bac1072..9597a1e7 100644 --- a/README.md +++ b/README.md @@ -18,10 +18,10 @@ Angular, Solid and plain-HTML apps (measured in Chromium with an unpublished 0.1 2026-10-10, not re-run on 0.2.2 or 0.3.0: [compatibility matrix](https://github.com/genclass-dev/GenClass/blob/main/compat/RESULTS.md)). -**Status: `@genclass/runtime@0.3.0-beta.5`, the newest line (npm `beta` dist-tag: `npm install @genclass/runtime@beta`; -the stable line is `0.2.x`), with model `@genclass/runtime-model@0.2.0`.** npm dist-tags on 2026-11-02: `latest` is -`0.2.3` and `beta` is `0.3.0-beta.5` (`0.3.0-beta.1` to `0.3.0-beta.5` were released between 2026-10-22 and -2026-11-02). This README describes the `0.3.0` line; `0.2.x`, npm's `latest`, is the exception for an app that cannot +**Status: `@genclass/runtime@0.3.0-beta.6`, the newest line (npm `beta` dist-tag: `npm install @genclass/runtime@beta`; +the stable line is `0.2.x`), with model `@genclass/runtime-model@0.2.0`.** npm dist-tags on 2026-11-11: `latest` is +`0.2.3` and `beta` is `0.3.0-beta.6` (`0.3.0-beta.1` to `0.3.0-beta.6` were released between 2026-10-22 and +2026-11-11). This README describes the `0.3.0` line; `0.2.x`, npm's `latest`, is the exception for an app that cannot take a prerelease. Both lines load the same model. AI coding agents working on this repository: start at [AGENTS.md](AGENTS.md). @@ -47,7 +47,7 @@ import "@genclass/runtime/auto"; Or with no build step, first in `
`: ```html - + ``` - **That covers network, user actions, errors and timing in the whole app, and its state where it can be found.** @@ -309,7 +309,7 @@ but the gate fired anyway. Source and history: 10.2 MB q8, about 180 to 600 ms per model pass at 500 to 1,170 tokens on one WASM thread (estimated from runs in Node, not in a browser), loaded from jsDelivr at idle and cached. The model and the situation text it reads (`situation-v2.3`) are the same in `0.2.2` and in every `0.3.0` release so far -(`0.3.0-beta.0` to `0.3.0-beta.5`; each CHANGELOG entry says no model-visible text changed). On held-out data (§1): +(`0.3.0-beta.0` to `0.3.0-beta.6`; each CHANGELOG entry says no model-visible text changed). On held-out data (§1): | profile | guard FIR | guard recall (clear / real) | heal FIR | heal recall (clear / real) | report threshold | |---|---|---|---|---|---| diff --git a/demo-site/DEMO-3MIN.md b/demo-site/DEMO-3MIN.md index f1880069..911eaf4b 100644 --- a/demo-site/DEMO-3MIN.md +++ b/demo-site/DEMO-3MIN.md @@ -21,7 +21,7 @@ End card (your edit): **Detect → Hotfix → Permanently fix → Monitor.** 1. **Live versions.** These three must be live (Claude Code reports each one when it is done): - genclass.dev: collector version `5602614c` (the Snowday estimate in the dashboard and in MCP). - - npm: `@genclass/runtime@0.3.0-beta.5` (the widget counts checks; the measured checks' counts reach telemetry). + - npm: `@genclass/runtime@0.3.0-beta.6` (the widget counts checks; the measured checks' counts reach telemetry). - snowday-predictor.ca: `~/snowday-demo` deployed with beta.4 (`cd ~/snowday-demo && npm run deploy`). 2. **Google's overlay ads off** for the recording (they cover the page and steal clicks; a click during the test opened an advertiser's site): AdSense → Ads → By site → snowday-predictor.ca → Edit → Ad formats → **Overlay formats**: diff --git a/docs/runtime/ANALYTICS.md b/docs/runtime/ANALYTICS.md index d6cc9ba3..fd19385f 100644 --- a/docs/runtime/ANALYTICS.md +++ b/docs/runtime/ANALYTICS.md @@ -6,7 +6,7 @@ app's token (or a custom telemetry endpoint), are turned off by every telemetry never record element text, and never reach the model or a decision. Status: merged into `main` on 2026-10-18 and shipped in `@genclass/runtime` 0.3.0-beta.1 (2026-10-22, npm's `beta` dist-tag); visits, funnels, navigation paths and the version check (sections 1.2, 3.1, 11 and 4.1) followed in 0.3.0-beta.2 (2026-10-25); the newest release is -0.3.0-beta.5 (2026-11-02). npm's `latest`, 0.2.3, has no analytics (section 4.1). +0.3.0-beta.6 (2026-11-11). npm's `latest`, 0.2.3, has no analytics (section 4.1). Design written 2026-10-17 and **approved by the owner the same day** with every recommendation in [section 9](#9-decisions-for-the-owner) (AGENTS.md rule 8: widening what telemetry sends needs that OK). **Built** @@ -234,7 +234,7 @@ GenClass.init({ token: "gc_…", analytics: true }); Interaction analytics first shipped in `@genclass/runtime` **0.3.0-beta.1**, on npm's `beta` dist-tag (install it with `npm install @genclass/runtime@beta`, `npx @genclass/runtime@beta init`, or a script tag pinned to the exact version, -`@0.3.0-beta.5` on 2026-11-03). npm's `latest` is still `0.2.3` until 0.3.0 is stable, and `0.2.x` and `0.3.0-beta.0` +`@0.3.0-beta.6` on 2026-11-11). npm's `latest` is still `0.2.3` until 0.3.0 is stable, and `0.2.x` and `0.3.0-beta.0` have no analytics: they ignore `analytics: true` without a word (reproduced on 0.2.2 in jsdom: no warning, no `runtime.analytics`, nothing sent; a TypeScript app gets a type error for the unknown option). Those releases cannot change, so every path that the newest line controls says it instead: diff --git a/docs/runtime/API.md b/docs/runtime/API.md index e1ed9b9e..49c39940 100644 --- a/docs/runtime/API.md +++ b/docs/runtime/API.md @@ -1,7 +1,7 @@ # GenClass Runtime API reference (@genclass/runtime) This page describes every export, option, event, action and type of `@genclass/runtime` on `main`. -`npm i @genclass/runtime` installs 0.2.3 (`latest`); `npm i @genclass/runtime@beta` installs 0.3.0-beta.5. Items +`npm i @genclass/runtime` installs 0.2.3 (`latest`); `npm i @genclass/runtime@beta` installs 0.3.0-beta.6. Items marked 0.3.0 are not in 0.2.x; items marked 0.3.0-beta.1 (interaction analytics, the devtools redesign) and later are on npm's `beta` dist-tag since 2026-10-22. diff --git a/docs/runtime/ARCHITECTURE.md b/docs/runtime/ARCHITECTURE.md index d5b12be3..d9663a0d 100644 --- a/docs/runtime/ARCHITECTURE.md +++ b/docs/runtime/ARCHITECTURE.md @@ -3,8 +3,8 @@ GenClass Runtime (`@genclass/runtime`) is a browser library. It watches what a web app does (requests, pushed messages, user actions, timers, state writes, errors) and, for the few situations that look risky, asks a small on-device model whether something is going wrong and what to do. This page explains how the parts fit together and -why they are built this way, for `@genclass/runtime` on `main` (version string 0.3.0-beta.5; npm `latest` is 0.2.3, `beta` is -0.3.0-beta.5) with model +why they are built this way, for `@genclass/runtime` on `main` (version string 0.3.0-beta.6; npm `latest` is 0.2.3, `beta` is +0.3.0-beta.6) with model `@genclass/runtime-model` 0.2.0. Items marked 0.3.0 are in the 0.3.0 line (0.3.0-beta.0 and later) and not in 0.2.x. How to use it: [API.md](API.md). Binding rules: [CONTRACT.md](CONTRACT.md). Every measured number: [RESULTS.md](RESULTS.md). Terms: the [glossary](README.md#glossary). diff --git a/docs/runtime/OPTIONS-SPEC.md b/docs/runtime/OPTIONS-SPEC.md index df3c0a13..88f4d7ce 100644 --- a/docs/runtime/OPTIONS-SPEC.md +++ b/docs/runtime/OPTIONS-SPEC.md @@ -3,7 +3,7 @@ This page is the design spec for the configuration options of `@genclass/runtime`: why each option exists and how the options combine. The reference for each option is [API.md](API.md) and the JSDoc in `packages/runtime/src/types.ts`; where they differ from this spec, they describe the code. `npm i @genclass/runtime@beta` -installs 0.3.0-beta.5 (npm's `beta` dist-tag, 2026-11-02); plain `npm i @genclass/runtime` installs the stable line, +installs 0.3.0-beta.6 (npm's `beta` dist-tag, 2026-11-11); plain `npm i @genclass/runtime` installs the stable line, 0.2.3 (`latest`). Items marked 0.3.0 are not in 0.2.x. Status: built. Most options here shipped in 0.1.0-beta.1 (the CHANGELOG's "Batch 12, 19 options") and are in every diff --git a/docs/runtime/README.md b/docs/runtime/README.md index 4ee5a217..7711af55 100644 --- a/docs/runtime/README.md +++ b/docs/runtime/README.md @@ -1,8 +1,8 @@ # GenClass documentation This is the index of the GenClass Runtime documentation: which document answers which question, how current each one -is, and where genclass.dev shows it. It covers `@genclass/runtime` on `main` (version string 0.3.0-beta.5; -`npm i @genclass/runtime@beta` installs 0.3.0-beta.5, `npm i @genclass/runtime` installs 0.2.3) and the model +is, and where genclass.dev shows it. It covers `@genclass/runtime` on `main` (version string 0.3.0-beta.6; +`npm i @genclass/runtime@beta` installs 0.3.0-beta.6, `npm i @genclass/runtime` installs 0.2.3) and the model `@genclass/runtime-model` 0.2.0. Items marked 0.3.0 are in the 0.3.0 line (0.3.0-beta.0 and later) and not in 0.2.x. The [glossary](#glossary) at the end defines the terms the other documents use. diff --git a/packages/genclass-runtime/README.md b/packages/genclass-runtime/README.md index 6f162726..0536acbe 100644 --- a/packages/genclass-runtime/README.md +++ b/packages/genclass-runtime/README.md @@ -15,12 +15,12 @@ failures, and `heal` is experimental. ## What should I run instead? ```bash -npx @genclass/runtime@beta init # the newest line: 0.3.0-beta.5 on 2026-11-03 +npx @genclass/runtime@beta init # the newest line: 0.3.0-beta.6 on 2026-11-11 npx @genclass/runtime@beta init --token gc_... # use a token you already have (no call to genclass.dev) npx @genclass/runtime@beta init --no-token # no token, no call to genclass.dev ``` -`@beta` is the newest line of `@genclass/runtime` (`0.3.0-beta.5` on 2026-11-03); the stable line, `0.2.3` (npm's +`@beta` is the newest line of `@genclass/runtime` (`0.3.0-beta.6` on 2026-11-11); the stable line, `0.2.3` (npm's `latest`, `npx @genclass/runtime init`), is the exception. npm's `genclass-runtime` is still at `0.1.0-beta.3`, so `npx genclass-runtime init` runs that old CLI unless the project already has `@genclass/runtime` installed (see below). @@ -59,7 +59,7 @@ sending Global Privacy Control are never collected. Details: