Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand All @@ -47,7 +47,7 @@ import "@genclass/runtime/auto";
Or with no build step, first in `<head>`:

```html
<script src="https://cdn.jsdelivr.net/npm/@genclass/runtime@0.3.0-beta.5"></script>
<script src="https://cdn.jsdelivr.net/npm/@genclass/runtime@0.3.0-beta.6"></script>
```

- **That covers network, user actions, errors and timing in the whole app, and its state where it can be found.**
Expand Down Expand Up @@ -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 |
|---|---|---|---|---|---|
Expand Down
2 changes: 1 addition & 1 deletion demo-site/DEMO-3MIN.md
Original file line number Diff line number Diff line change
Expand Up @@ -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**:
Expand Down
4 changes: 2 additions & 2 deletions docs/runtime/ANALYTICS.md
Original file line number Diff line number Diff line change
Expand Up @@ -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**
Expand Down Expand Up @@ -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:
Expand Down
2 changes: 1 addition & 1 deletion docs/runtime/API.md
Original file line number Diff line number Diff line change
@@ -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.

Expand Down
4 changes: 2 additions & 2 deletions docs/runtime/ARCHITECTURE.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down
2 changes: 1 addition & 1 deletion docs/runtime/OPTIONS-SPEC.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions docs/runtime/README.md
Original file line number Diff line number Diff line change
@@ -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.
Expand Down
6 changes: 3 additions & 3 deletions packages/genclass-runtime/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down Expand Up @@ -59,7 +59,7 @@ sending Global Privacy Control are never collected. Details:
<!-- Maintainers: npmjs.com shows the README and package.json fields of the published version. On 2026-10-27 npm has
genclass-runtime 0.1.0-beta.3 (latest, published 2026-10-09) with its older README and description ("Short alias for
the @genclass/runtime CLI ...") and no deprecation flag; release.yml packs and publishes only packages/runtime
(@genclass/runtime, 0.3.0-beta.5 on main), so this README and the description here do not reach npm. The notice
(@genclass/runtime, 0.3.0-beta.6 on main), so this README and the description here do not reach npm. The notice
reaches npm users only through
`npm deprecate genclass-runtime "Deprecated: use @genclass/runtime (npx @genclass/runtime@beta init)"`, which
npmjs.com shows and npm prints when it installs the package; that is the owner's call. genclass-runtime@0.3.0-beta.1,
Expand Down
2 changes: 1 addition & 1 deletion packages/runtime-model/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ diagnostics are separate (see [Privacy](#privacy)).

This page covers `@genclass/runtime-model@0.2.0` (model `genclass-runtime-r17` 2.0.0-rc4t, training run
`r17-v2dT`), the default model of `@genclass/runtime` 0.1.0-beta.1 and later, including `0.2.3` (npm `latest`) and
`0.3.0-beta.5` (`beta`, 2026-11-03). Training data, held-out results, thresholds and limits are in the
`0.3.0-beta.6` (`beta`, 2026-11-11). Training data, held-out results, thresholds and limits are in the
[model card](https://github.com/genclass-dev/GenClass/blob/main/packages/runtime-model/MODEL_CARD.md).

## At a glance
Expand Down
6 changes: 3 additions & 3 deletions packages/runtime/INTERCEPTION.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ browser global, compares what changed with the inventory at the end of this page
and counts the patch sites in `src/` (a new `addEventListener`, `defineProperty` or global assignment fails the test
until this page is updated).

> **Version.** Written for `@genclass/runtime` 0.3.0-beta.5 as it is on GitHub `main` (released 2026-11-02). The
> copy in an npm package describes that package's version. As of 2026-11-02, `npm i @genclass/runtime@beta` installs
> 0.3.0-beta.5 (the 0.3.0 line: 0.3.0-beta.1 to 0.3.0-beta.5, released 2026-10-22 to 2026-11-02), and
> **Version.** Written for `@genclass/runtime` 0.3.0-beta.6 as it is on GitHub `main` (released 2026-11-11). The
> copy in an npm package describes that package's version. As of 2026-11-11, `npm i @genclass/runtime@beta` installs
> 0.3.0-beta.6 (the 0.3.0 line: 0.3.0-beta.1 to 0.3.0-beta.6, released 2026-10-22 to 2026-11-11), and
> `npm i @genclass/runtime` installs 0.2.3 (`latest`, 2026-10-28), which has no measured visual checks, no `protect()`,
> no webhook sink and no interaction analytics. Items marked 0.3.0 are not in 0.2.x; the interaction analytics rows
> (`src/analytics/`) and the devtools overlay's `theme: "dark"` default are 0.3.0-beta.1, the `genclass.analytics.<token>`
Expand Down
12 changes: 6 additions & 6 deletions packages/runtime/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ import "@genclass/runtime/auto"; // first line of your entry file (Next.js 15.3+
Or with no build step, first in `<head>`:

```html
<script src="https://cdn.jsdelivr.net/npm/@genclass/runtime@0.3.0-beta.5"></script>
<script src="https://cdn.jsdelivr.net/npm/@genclass/runtime@0.3.0-beta.6"></script>
```

That is the whole setup. Network traffic, user actions, errors and timing are observed, and so is your app's state:
Expand All @@ -59,7 +59,7 @@ React component state, Redux and Redux Toolkit stores, and Zustand stores with `
are not: there, stale responses are reported only for stores you register (double submits need no state).

**Versions:** this README describes `0.3.0` with model `@genclass/runtime-model@0.2.0`. The newest line is
`0.3.0-beta.5`, npm's `beta` dist-tag (`0.3.0-beta.1` to `beta.5` were released between 2026-10-22 and 2026-11-02);
`0.3.0-beta.6`, npm's `beta` dist-tag (`0.3.0-beta.1` to `beta.6` were released between 2026-10-22 and 2026-11-11);
npm's `latest` is still the older `0.2.3` (`npm view @genclass/runtime dist-tags` shows them now). Every npm and npx
command here names `@beta`: without it npm installs `0.2.x`, which has no token, dashboard, interaction analytics,
visual checks or agent link and ignores those options without a word (a TypeScript app gets a type error for
Expand Down Expand Up @@ -476,11 +476,11 @@ dist-tag it came from, asks npm's dist-tags once (`npm view @genclass/runtime di
on npm, with the command that runs it:

```
✔ Version @genclass/runtime 0.3.0-beta.4 (npm dist-tag beta)
▲ Newer @genclass/runtime 0.3.0-beta.5 is on npm (dist-tag beta): run npx @genclass/runtime@beta init instead
✔ Version @genclass/runtime 0.3.0-beta.5 (npm dist-tag beta)
▲ Newer @genclass/runtime 0.3.0-beta.6 is on npm (dist-tag beta): run npx @genclass/runtime@beta init instead
```

It installs its own version (`@genclass/runtime@^0.3.0-beta.5` today), and a project that already has an older one
It installs its own version (`@genclass/runtime@^0.3.0-beta.6` today), and a project that already has an older one
(a `0.2.x` from `npx @genclass/runtime init` without `@beta`) is upgraded, after the same diff and question. Every
command it prints names `@beta` while it is a prerelease.

Expand Down Expand Up @@ -509,7 +509,7 @@ Options go in `window.GENCLASS_CONFIG = { ... }` (any `InitOptions`, set before
**3. One script tag** (no build step), first in `<head>`:

```html
<script src="https://cdn.jsdelivr.net/npm/@genclass/runtime@0.3.0-beta.5" data-mode="observe" data-devtools="local"></script>
<script src="https://cdn.jsdelivr.net/npm/@genclass/runtime@0.3.0-beta.6" data-mode="observe" data-devtools="local"></script>
```

It exposes `window.GenClass` and loads the model worker and the overlay on demand from the same version; `data-mode`,
Expand Down
8 changes: 4 additions & 4 deletions packages/runtime/TELEMETRY.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,10 @@ GenClass Runtime (`@genclass/runtime`), an open-source browser library that repo
sends anonymous diagnostics about its own decisions to its maintainers, by default on public websites; this page lists
every event and field it sends, where they are stored and for how long, and every way to turn it off.

> **Version.** Written for `@genclass/runtime` 0.3.0-beta.5 (2026-11-02), the version on GitHub `main`, in
> **Version.** Written for `@genclass/runtime` 0.3.0-beta.6 (2026-11-11), the version on GitHub `main`, in
> `package.json` and in the `runtime` field of every batch. The copy in an npm package describes that package's version.
> As of 2026-11-02, `npm i @genclass/runtime@beta` installs 0.3.0-beta.5 (the newest line; 0.3.0-beta.1 to beta.5 were
> released 2026-10-22 to 2026-11-02) and `npm i @genclass/runtime` installs the stable line, 0.2.3 (`latest`,
> As of 2026-11-11, `npm i @genclass/runtime@beta` installs 0.3.0-beta.6 (the newest line; 0.3.0-beta.1 to beta.6 were
> released 2026-10-22 to 2026-11-11) and `npm i @genclass/runtime` installs the stable line, 0.2.3 (`latest`,
> 2026-10-28). Items
> marked 0.3.0 are not in 0.2.x; interaction analytics are marked 0.3.0-beta.1, visits and navigation paths
> 0.3.0-beta.2.
Expand Down Expand Up @@ -106,7 +106,7 @@ segment holding an `@`, such as an e-mail address, is `:id` too).
"token": "gc_…", // only when the app configured a valid token (InitOptions.token); see "App tokens"
"sid": "3f9c…", // 24 hex chars from crypto.getRandomValues, new on every page load, never stored
"sent": 12034, // ms since this page's GenClass started (no wall-clock time is sent)
"runtime": "0.3.0-beta.5", // @genclass/runtime version
"runtime": "0.3.0-beta.6", // @genclass/runtime version
"model": "2.0.0-rc4t", // model card version, or null without a model
"events": [ /* ≤ 100 events, ≤ 60 KB per request */ ]
}
Expand Down
4 changes: 2 additions & 2 deletions telemetry-worker/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -422,7 +422,7 @@ The daily cron also deletes expired challenges and device codes and expired or r
|---|---|---|---|
| `AUTH_ORIGIN` | var | `https://genclass.dev` | expected `Origin`, WebAuthn origin, OAuth redirect URIs, cookie `Secure` |
| `AUTH_RP_ID` | var | `genclass.dev` | WebAuthn RP ID |
| `RUNTIME_ON_NPM` | var (wrangler.toml) | `0.3.0-beta.5` | the newest `@genclass/runtime` on npm, on any dist-tag; below `0.3.0-beta.0` the Connect dialog, `/start` and private dashboards say first that keys and `login` are not published yet. Set it with `src/pages.ts` `SNIPPET_RUNTIME` to every release once release.yml has published it and jsDelivr serves it, then deploy; at `0.3.0` also set `RUNTIME_PKG` (the snippets pin the script tag to `SNIPPET_RUNTIME` and name the `@beta` dist-tag in their commands while it is a prerelease) |
| `RUNTIME_ON_NPM` | var (wrangler.toml) | `0.3.0-beta.6` | the newest `@genclass/runtime` on npm, on any dist-tag; below `0.3.0-beta.0` the Connect dialog, `/start` and private dashboards say first that keys and `login` are not published yet. Set it with `src/pages.ts` `SNIPPET_RUNTIME` to every release once release.yml has published it and jsDelivr serves it, then deploy; at `0.3.0` also set `RUNTIME_PKG` (the snippets pin the script tag to `SNIPPET_RUNTIME` and name the `@beta` dist-tag in their commands while it is a prerelease) |
| `GOOGLE_CLIENT_ID`, `GOOGLE_CLIENT_SECRET` | secret | unset | Google sign-in, the first way in; both needed. An email and a password are offered either way |
| `GITHUB_CLIENT_ID`, `GITHUB_CLIENT_SECRET` | secret | unset | GitHub sign-in; both needed |

Expand Down Expand Up @@ -1093,7 +1093,7 @@ GenClass.init({ token: "gc_...", telemetry: { endpoint: "https://<your worker>/v

```html
<script>window.GENCLASS_CONFIG = { telemetry: { endpoint: "https://<your worker>/v1/events" } };</script>
<script src="https://cdn.jsdelivr.net/npm/@genclass/runtime@0.3.0-beta.5" data-token="gc_..."></script>
<script src="https://cdn.jsdelivr.net/npm/@genclass/runtime@0.3.0-beta.6" data-token="gc_..."></script>
```

Accounts work on it as on genclass.dev (an email and a password, and passkeys; Google and GitHub with your own OAuth
Expand Down
2 changes: 1 addition & 1 deletion telemetry-worker/src/pages.ts
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ export const ANALYTICS_RUNTIME = "0.3.0-beta.1";
* set SNIPPET_RUNTIME to "0.3.0" and RUNTIME_PKG to "@genclass/runtime" (and RUNTIME_ON_NPM in wrangler.toml), then
* deploy.
*/
export const SNIPPET_RUNTIME = "0.3.0-beta.5";
export const SNIPPET_RUNTIME = "0.3.0-beta.6";
export const RUNTIME_PKG = "@genclass/runtime@beta";
export const CDN_SCRIPT = `https://cdn.jsdelivr.net/npm/@genclass/runtime@${SNIPPET_RUNTIME}`;
/** What local and private hosts do, as the runtime behaves (src/telemetry/config.ts) and PRIVACY.md says. */
Expand Down
4 changes: 2 additions & 2 deletions telemetry-worker/wrangler.toml
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,10 @@ routes = [

# The newest @genclass/runtime on npm, on any dist-tag. Below 0.3.0-beta.0 the Connect panel, /start and private
# dashboards say first that project keys and `login` are not published yet. Set it (with pages.ts SNIPPET_RUNTIME, then
# deploy) to every release once release.yml has published it and jsDelivr serves it: 0.3.0-beta.5 now, "0.3.0" at 0.3.0
# deploy) to every release once release.yml has published it and jsDelivr serves it: 0.3.0-beta.6 now, "0.3.0" at 0.3.0
# (with RUNTIME_PKG).
[vars]
RUNTIME_ON_NPM = "0.3.0-beta.5"
RUNTIME_ON_NPM = "0.3.0-beta.6"
# "on" sells the plans marked managed_payments in billing/plans.json through Stripe Managed Payments (Stripe, through
# Link, is the merchant of record, for 3.5% of each payment on top of Stripe's fees). No plan is marked today
# (no plan is sold on the site today), so it stays "off"; README "Paid plans".
Expand Down
Loading