@cbxss/eoka 0.1.0-beta.1 → 0.1.0-beta.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,540 +1,171 @@
1
1
  # @cbxss/eoka
2
2
 
3
- The Node.js SDK for the eoka NDJSON browser sidecar. The source package remains private and unpublished; npm version `0.1.0-beta.1` is reserved for the qualified beta release and can be built and packed locally for integration testing. It supports **Node.js 24 LTS, starting at 24.21.0** (`^24.21.0`) and exports compiled ESM and TypeScript declarations. Node 22 and Current/non-LTS lines are outside the support policy. CommonJS `require` is not an export.
3
+ Node.js SDK for eoka, a stealth Chrome automation sidecar.
4
4
 
5
- ## Current scope and platform qualification
6
-
7
- The SDK provides correlated subprocess transport, typed browser/page operations, durable operation handles, pinned full Chrome for Testing installation, verified native server resolution, PNG/JPEG/WebP capture, native MP4 recording, and bounded disposal. It does not provide deterministic scenario replay or video transcoding. Importing the package and installing with `--ignore-scripts` do not launch processes, download Chrome, or create a browser cache. There are no install lifecycle scripts, Cargo requirements, or package command-line binaries.
8
-
9
- Managed targets are `linux-x64-gnu`, `linux-arm64-gnu`, `darwin-x64`, `darwin-arm64`, and `win32-x64`. Linux managed selection requires glibc >= 2.35 and rejects musl/Alpine; Windows arm64 and unknown combinations are rejected before downloads. GNU release artifacts are built on Ubuntu 22.04 and checked for GLIBC requirements no higher than 2.35. Arbitrary source-built or host-development binaries are not qualified by that result.
5
+ ```sh
6
+ npm install @cbxss/eoka@latest
7
+ ```
10
8
 
11
- Both explicit server and Chrome paths are an expert override for managed platform checks, not a new support guarantee. Node.js support does not imply Bun, Deno, browser-side JavaScript, or drop-in Puppeteer compatibility. Packed npm consumption is verified; pnpm/Yarn and registry-backed publication remain separate gates.
9
+ Requires Node.js 24.21+ (ESM only). Supported platforms: Linux x64/arm64 (glibc 2.35+), macOS x64/arm64, Windows x64.
12
10
 
13
- ## Managed launch and explicit preparation
11
+ ## Quick start
14
12
 
15
13
  ```js
16
- import { Browser, installBrowser } from "@cbxss/eoka";
17
-
18
- await installBrowser({
19
- browserCacheDir: "/opt/eoka/cache",
20
- timeoutMs: 300000,
21
- onProgress: ({ downloadedBytes, totalBytes, buildId }) => {
22
- process.stderr.write(`${buildId}: ${downloadedBytes}/${totalBytes} bytes\n`);
23
- },
24
- });
14
+ import { Browser } from "@cbxss/eoka";
25
15
 
26
- const browser = await Browser.launch({
27
- browserCacheDir: "/opt/eoka/cache",
28
- download: "never",
29
- sandbox: true,
30
- timeoutMs: 30000,
31
- });
16
+ const browser = await Browser.launch();
32
17
  try {
33
- const page = await browser.newPage("data:text/html,%3Ctitle%3Eoffline%3C/title%3E");
34
- console.log(await page.invoke("page.evaluate", { pageId: page.id, js: "document.title" }));
18
+ const page = await browser.newPage("https://example.com");
19
+ console.log(await page.title());
20
+ await page.screenshotToFile({ path: "./example.png" });
35
21
  } finally {
36
22
  await browser.close();
37
23
  }
38
24
  ```
39
25
 
40
- `Browser.launch()` resolves its server **before** installing Chrome. Server precedence is `serverPath` > `EOKA_SERVER_BIN` > exact optional platform package. It never searches PATH, builds Rust, or downloads a server. Browser precedence is `executablePath` > `EOKA_CHROME_PATH` > the managed pin. There is no fallback to a system browser or a different build. `Browser.connect()` resolves/starts the server but does not install or access the managed Chrome cache.
41
-
42
- `installBrowser` prepares only Chrome; it does not install system libraries or native server packages. Its options are `browserCacheDir`, `download` (`"auto"` by default or `"never"`), `signal`, `timeoutMs` (300000 ms by default), and `onProgress`. It returns `{ executablePath, cacheDir, buildId, platform, source }`, with `source: "cache"` or `"download"`. Cancellation/deadlines terminate the owned installer worker before cleaning its own staging resources. One launch deadline covers server resolution, Chrome installation, handshake, and native launch.
43
-
44
- `onProgress` receives download byte counts without writing to stdout. Without a callback, the first actual download chunk emits one diagnostic to stderr; verified cache hits and imports remain silent.
45
-
46
- ## Cache, runtime, and offline operation
47
-
48
- Cache root precedence is `browserCacheDir` > `EOKA_BROWSER_CACHE_DIR` > the per-user OS default:
49
-
50
- | OS | Default cache root |
51
- | --- | --- |
52
- | Linux | `${XDG_CACHE_HOME}/eoka`, or `~/.cache/eoka` |
53
- | macOS | `~/Library/Caches/eoka` |
54
- | Windows | `${LOCALAPPDATA}/eoka/Cache`, or `~/AppData/Local/eoka/Cache` |
55
-
56
- The installer keeps the complete distribution, including resources, libraries, and macOS bundle contents. It hashes the archive against the release pin, inventories the full installed tree, stages publication atomically, and coordinates concurrent installs per build. Cache validation detects missing/corrupt companion files as well as executable changes. Local writable inventory metadata is a same-user trust boundary, not protection against a malicious account that can replace both data and metadata.
57
-
58
- Preinstall using the same platform/build and cache root as the eventual runtime. Preserve the **whole** cache entry and its metadata; copying just Chrome's executable is insufficient. A verified cache hit requires no network or writes, including on a read-only image. `download: "never"` fails with `BrowserNotInstalled` on an absent entry and does not repair corruption by downloading. Cache integrity failures are explicit. Default cache retention is persistent; `Browser.close()` never removes installed Chrome. Remove unused cache roots only as an explicit administrator action when no session is using them.
59
-
60
- Runtime root precedence is `runtimeDir` > `EOKA_RUNTIME_DIR` > the OS temporary directory. Every launch gets a private child beneath that root. Child-only `TMPDIR`/`TMP`/`TEMP` direct native scratch work there without changing the Node process's environment. Keep runtime writable even when the browser cache is read-only. Owned child directories are cleaned only after owned-process termination is confirmed; uncertain termination retains the directory and reports its path through `RuntimeCleanupUncertain`. Caller roots, persistent `userDataDir` profiles, and the cache are not deleted. On POSIX keep the root short enough for Chrome's singleton Unix socket. Do not share persistent profiles concurrently; they contain cookies and other private session data.
61
-
62
- From an installed SDK application, run the shipped examples directly:
63
-
64
- ```sh
65
- node node_modules/@cbxss/eoka/examples/install-browser.mjs /opt/eoka/cache
66
- EOKA_RUNTIME_DIR=/tmp/eoka node node_modules/@cbxss/eoka/examples/offline.mjs /opt/eoka/cache
67
- ```
68
-
69
- The offline example uses a data URL, so its page also requires no network. `download: "never"` governs installation, not web page requests; use an OS/container network policy to prevent application traffic.
70
-
71
- ## Download pins, size, and proxy configuration
72
-
73
- This source pins full Chrome for Testing **155.0.8059.39**, not ChromeDriver or a runtime-selected latest version. `releaseManifest` and `@cbxss/eoka/release-manifest.json` expose the release metadata. The archive SHA-256 values were computed from full HTTPS archives during controlled release preparation; they are reviewed integrity pins, **not vendor signatures**. Runtime installation uses those embedded pins and never looks up a hash or substitutes a mirror/build. Browser updates require a deliberate new release and fresh native gates.
74
-
75
- Measured compressed archive sizes for this pin:
76
-
77
- | Chrome platform | Bytes |
78
- | --- | ---: |
79
- | linux64 | 198195769 |
80
- | linux-arm64 | 198202003 |
81
- | mac-x64 | 203101743 |
82
- | mac-arm64 | 192634606 |
83
- | win64 | 207197429 |
84
-
85
- Budget additional space for the expanded distribution, temporary archive/staging, and concurrent runtime profiles. The SDK does not download browser drivers.
86
-
87
- The installer honors `HTTPS_PROXY`, `HTTP_PROXY`, `ALL_PROXY`, and `NO_PROXY` through its pinned proxy dependency. Configure them in the setup process environment, or in `serverEnv` for a launch-scoped child environment. Do not put proxy credentials in progress logs. Standard Node trust configuration such as `NODE_EXTRA_CA_CERTS` must be set before starting Node when an enterprise CA is required. TLS failures and hash mismatches fail closed; do not disable certificate verification.
88
-
89
- ```sh
90
- HTTPS_PROXY=http://proxy.example:8080 NO_PROXY=localhost,127.0.0.1 \
91
- node node_modules/@cbxss/eoka/examples/install-browser.mjs /opt/eoka/cache
92
- ```
93
-
94
- ## Linux libraries, sandbox, and containers
95
-
96
- The SDK does not install privileged OS packages. Chrome requires its host libraries and fonts even in headless mode: NSS/NSPR, ATK/AT-SPI, CUPS, DRM/GBM, X11/XCB/Xcomposite/Xdamage/Xfixes/Xrandr, xkbcommon, ALSA, GLib, Cairo/Pango, and fonts. The native server's dependencies are artifact-specific; current Linux staging also needs OpenSSL 3 (`libssl.so.3` and `libcrypto.so.3`). Inspect actual release binaries and qualify the chosen distribution rather than treating this list as an ABI certification.
97
-
98
- Sandboxing is enabled by default. Run as an unprivileged user with Chrome's sandbox requirements satisfied (including the host/container user-namespace and seccomp policy). A sandbox failure is an error; the SDK never retries with sandbox disabled. `sandbox: false` is an explicit security-reducing expert choice for a separately isolated environment, not the default container recipe.
99
-
100
- Ubuntu 23.10+ can deny unprivileged user namespaces through AppArmor even when
101
- Chrome itself is sandbox-enabled. An administrator must provide a narrowly
102
- scoped executable-path policy for the owned Chrome runtime, as described in
103
- [Chromium's AppArmor guidance](https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md).
104
- Any process able to replace an executable at an allowed path gains that
105
- permission; use a private runtime directory, not a broad `/tmp/**/chrome` rule.
106
- The SDK neither installs privileged policies nor disables the host restriction.
107
- ARM release CI uses a private per-job path exception, removes it afterward,
108
- and checks Chrome's actual PID/network namespace and seccomp status.
109
-
110
- For example, prepare a Linux x64 image with Node 24.21.0 and a distribution new enough for the **actual staged binary**. The following Debian trixie setup is a recipe to qualify, not a statement of completed container support. Supply the two locally staged tarballs described below as build inputs:
111
-
112
- ```dockerfile
113
- FROM node:24.21.0-trixie
114
- RUN apt-get update && apt-get install -y --no-install-recommends \
115
- ca-certificates fonts-liberation libasound2t64 libatk-bridge2.0-0t64 libatk1.0-0t64 \
116
- libcairo2 libcups2t64 libdbus-1-3 libdrm2 libgbm1 libglib2.0-0t64 libnspr4 \
117
- libnss3 libpango-1.0-0 libssl3t64 libx11-6 libxcb1 libxcomposite1 libxdamage1 \
118
- libxext6 libxfixes3 libxkbcommon0 libxrandr2 \
119
- && rm -rf /var/lib/apt/lists/*
120
- WORKDIR /app
121
- RUN chown node:node /app
122
- COPY --chown=node:node cbxss-eoka-0.1.0-beta.1.tgz cbxss-eoka-server-linux-x64-gnu-0.1.0-beta.1.tgz ./
123
- USER node
124
- RUN npm init -y && npm install --ignore-scripts --omit=optional --no-audit --no-fund \
125
- ./cbxss-eoka-server-linux-x64-gnu-0.1.0-beta.1.tgz ./cbxss-eoka-0.1.0-beta.1.tgz
126
- ENV EOKA_BROWSER_CACHE_DIR=/app/browser-cache
127
- ENV EOKA_RUNTIME_DIR=/tmp/eoka
128
- RUN node node_modules/@cbxss/eoka/examples/install-browser.mjs
129
- CMD ["node", "node_modules/@cbxss/eoka/examples/offline.mjs"]
130
- ```
131
-
132
- Network is needed during image preparation for npm dependencies and the pinned Chrome ZIP. Runtime can then be isolated with `docker run --init --network=none --read-only --tmpfs /tmp:rw,nosuid,size=1g IMAGE`, provided the host's sandbox policy permits Chrome. Use an init process to reap orphaned browser children. Preserve cache ownership/metadata in the image and keep `/tmp` writable. Adapt library names, resource limits, and sandbox policy to the deployment; never use an Alpine/musl base for managed mode.
133
-
134
- ## Build, source staging, and local consumption
135
-
136
- This SDK and its five native packages share reserved npm version `0.1.0-beta.1`. The native server is pinned separately to `0.5.0`, published registry core to `0.7.0`, and the protocol to `1.3`; npm version equality is not wire compatibility. Release manifests accept exact semantic versions, including prereleases, but reject floating ranges, tags, and malformed versions. Packaged servers are checked against their name/version/platform, staged release metadata, actual binary digest, and expected handshake version. Explicit servers still must pass the protocol handshake.
137
-
138
- The source manifest intentionally has no fabricated hashes for unprepared native artifacts. The source package omits native optional dependencies so a clean `npm ci` does not need unpublished packages. Staging derives all five exact native dependencies from the validated release manifest and adds them to the staged SDK's package metadata. Packing the source SDK alone is useful for import/type gates, but is **not** a ready managed server distribution. Missing native packages (including after `--omit=optional`) raise `ServerPackageMissing`; a present package with an unstaged SDK pin raises `ReleaseNotPrepared`. There is no compile/download fallback.
139
-
140
- Run `mise install` at the repository root to install the pinned Node 24.21.0 toolchain. With mise activated, prepare local artifacts from this package directory without publishing:
141
-
142
- ```sh
143
- npm ci --ignore-scripts --omit=optional
144
- npm run build
145
- npm run stage:release -- --artifacts /absolute/path/to/release-server-artifacts \
146
- --output /absolute/path/to/new-stage --host-only
147
- npm pack --ignore-scripts --pack-destination /absolute/path/to/tarballs \
148
- /absolute/path/to/new-stage/platforms/linux-x64-gnu
149
- npm pack --ignore-scripts --pack-destination /absolute/path/to/tarballs \
150
- /absolute/path/to/new-stage/sdk
151
- ```
152
-
153
- Use the detected host ID in the platform path. `--host-only` is a local gate, not qualification of unbuilt targets: it marks the stage as development and embeds the Linux artifact's measured minimum glibc, which may exceed 2.35. Without that flag, staging requires all five target artifacts and rejects Linux binaries whose `readelf` GLIBC requirements exceed 2.35; repeated `--platform ID` selects specific preparation targets. Staging consumes existing server release binaries, computes their real digest/size, and writes matching SDK/platform metadata; it does not invoke Cargo or build alternate binaries. Use the same controlled artifacts as the server release and retain their provenance. Unstaged targets remain explicitly unavailable.
154
-
155
- The artifact directory uses the existing server release asset names:
156
-
157
- | Platform ID | Required server artifact |
158
- | --- | --- |
159
- | linux-x64-gnu | `eoka-server-linux-amd64` |
160
- | linux-arm64-gnu | `eoka-server-linux-arm64` |
161
- | darwin-x64 | `eoka-server-darwin-amd64` |
162
- | darwin-arm64 | `eoka-server-darwin-arm64` |
163
- | win32-x64 | `eoka-server-windows-amd64.exe` |
164
-
165
- In a separate ESM application, install the matching native tarball as a direct dependency together with the staged SDK:
166
-
167
- ```sh
168
- npm install --ignore-scripts --omit=optional \
169
- /absolute/path/to/cbxss-eoka-server-linux-x64-gnu-0.1.0-beta.1.tgz \
170
- /absolute/path/to/cbxss-eoka-0.1.0-beta.1.tgz
171
- npm install --save-dev typescript@5.9.3 @types/node@24.19.2
172
- ```
173
-
174
- The local direct dependency deliberately avoids relying on unpublished optional packages being available in a registry. A future qualified published release will install the exact matching optional package normally; do not omit it unless supplying an explicit server path. No publishing is performed or authorized by source staging.
26
+ The first launch downloads a pinned Chrome for Testing build (about 200 MB) into a per-user cache. Later launches reuse it.
175
27
 
176
- Use `"type": "module"`, TypeScript `target: "ES2024"`, and `module`/`moduleResolution: "NodeNext"`. The root export supplies runtime SDK classes, installation APIs/errors, release/platform metadata, options, and common protocol types. `@cbxss/eoka/protocol` exposes the complete wire map. CommonJS consumers use dynamic `import()`. Runtime dependencies pin AJV `8.17.1`, `@puppeteer/browsers` `3.2.4`, `yauzl` `3.4.0`, and `proxy-agent` `8.0.1`; their engine requirements are compatible with the SDK's Node 24 LTS baseline.
177
-
178
- ## Explicit-path launch and verified receipts
28
+ ## Pages
179
29
 
180
30
  ```js
181
- import { randomUUID } from "node:crypto";
182
- import { Browser } from "@cbxss/eoka";
183
-
184
- const browser = await Browser.launch({
185
- serverPath: "/absolute/path/to/eoka-server",
186
- executablePath: "/absolute/path/to/chrome",
187
- headless: true,
188
- sandbox: true,
189
- viewport: { width: 1024, height: 768, deviceScaleFactor: 1 },
190
- timeoutMs: 15000,
31
+ await page.goto("https://example.com/login");
32
+ await page.fill("#email", "ada@example.com");
33
+ await page.click("button[type=submit]", {
34
+ actionOptions: { expect: { kind: "url", value: "/home", contains: true } },
191
35
  });
192
36
 
193
- try {
194
- const html = '<!doctype html><label>Name <input id="name"></label>';
195
- const page = await browser.newPage(`data:text/html,${encodeURIComponent(html)}`);
196
- const target = { query: { kind: "css", selector: "#name" } };
197
- const operationId = randomUUID();
198
- const receipt = await page.fill(target, "Ada", {
199
- operationId,
200
- timeoutMs: 10000,
201
- actionOptions: {
202
- expect: { kind: "value", target, value: "Ada" },
203
- timeout_ms: 5000,
204
- },
205
- });
206
- console.log({ operationId, receipt });
207
- console.log(await page.invoke("page.evaluate", {
208
- pageId: page.id,
209
- js: '({name: document.querySelector("#name").value})',
210
- }));
211
- } finally {
212
- await browser.close();
213
- }
37
+ await page.waitForText("Welcome");
38
+ const heading = await page.getText("h1");
39
+ const count = await page.evaluate("()=>document.querySelectorAll('li').length");
214
40
  ```
215
41
 
216
- `fill`, `goto`, `select`, `hover`, and the other action conveniences resolve with an actual canonical `ActionReceipt` only after terminal verified completion. Admission is not completion. `click`, `type`, `pressKey`, `submit`, `drag`, and consequential actions passed to `perform` require an explicit `actionOptions.expect` before dispatch. Locator strings mean CSS selectors; generated `LocatorSpec` objects retain the canonical query/frame/index semantics.
42
+ String targets are CSS selectors. An action resolves only after its result is verified. `click`, `type`, `pressKey`, `submit` and `drag` need an `expect` that describes the result.
217
43
 
218
- `newPage(url)` and `goto(url)` verify a navigation commit, not DOM parsing or application readiness. Before parser-dependent reads, use `evaluate` to await `DOMContentLoaded` only while `document.readyState === "loading"`; resolve the promise to a JSON-compatible value such as `true`. `goto` accepts an explicit `actionOptions.expect` when navigation must also establish application readiness.
44
+ - **Reads:** `text`, `content`, `title`, `url`, `getText`, `getAttribute`, `exists`, `evaluate`
45
+ - **Waits:** `waitFor`, `waitForVisible`, `waitForText`
46
+ - **Actions:** `goto`, `fill`, `select`, `hover`, `click`, `type`, `pressKey`, `submit`, `drag`
219
47
 
220
- Run the included example after building:
48
+ ## Shadow DOM and Turnstile
221
49
 
222
- ```sh
223
- npm run example -- /absolute/path/to/eoka-server /absolute/path/to/chrome
224
- ```
225
-
226
- Alternatively set `EOKA_SERVER_BIN` and `EOKA_CHROME_PATH`. Explicit options take precedence. Providing both paths bypasses managed installation/platform selection; no arbitrary system discovery is performed. `userDataDir` remains caller-owned. A temporary profile belongs to its owned session.
227
-
228
- ## Durable operations and uncertainty
50
+ `page.frames()` lists every frame, including cross-origin OOPIFs. `page.clickShadow(selector, { frameId?, resolveTimeoutMs? })` searches the frame's light DOM and every shadow root (closed roots included), maps the matched node's center to viewport coordinates, and clicks with human-like movement. `resolveTimeoutMs` bounds the server-side resolution; `CallOptions.timeoutMs` remains the RPC deadline and defaults to the resolution deadline plus 10 seconds when omitted:
229
51
 
230
52
  ```js
231
- const operationId = randomUUID();
232
- const operation = await page.perform(
233
- { kind: "fill", target, value: "Ada" },
234
- { operationId, actionOptions: { expect: { kind: "value", target, value: "Ada" } } },
235
- );
236
- const record = await operation.wait({ waitTimeoutMs: 1000, timeoutMs: 2000 });
237
- console.log({ operationId, state: record.state, outcome: record.outcome, receipt: record.receipt });
53
+ const challenge = (await page.frames()).find(frame =>
54
+ frame.url.includes("challenges.cloudflare.com"));
55
+ if (challenge) {
56
+ await page.clickShadow('input[type="checkbox"]', { frameId: challenge.id });
57
+ }
238
58
  ```
239
59
 
240
- `perform` returns an `Operation` after admission. `Operation.get`, `wait`, and `cancel` return canonical operation records. A bounded `wait` may return a still-running record; it does not assert success. `waitTimeoutMs` bounds the server wait, while `timeoutMs` and `signal` govern the local call. Cancellation is not rollback.
60
+ `page.solveTurnstile({ timeoutMs })` is a best-effort helper for interactive Cloudflare challenge pages. The server finds the challenge frame, clicks the checkbox, and waits for the page to leave the challenge state, then resolves with `{ clicks, elapsedMs }` (zero clicks on a normal page). It is not a general CAPTCHA solver.
241
61
 
242
- Get/cancel for an already-admitted operation remain responsive while an unrelated page request waits. Unknown IDs retain ordering behind earlier queued admissions. Operation lists are independent snapshots of currently admitted records, not barriers for queued mutations. These controls still obey the negotiated in-flight limit.
62
+ ### Automatic challenge handling
243
63
 
244
- Persist a caller-known UUID before dispatch when recovery matters. After a lost response or local timeout, recover the same operation using `browser.operation(operationId).get()` or `page.operation(operationId).get()`. The operation must still exist in the same sidecar runtime; its ledger is not a restart-persistent store. Do not automatically replay an action with an unknown outcome.
64
+ `Browser.launch({ autoSolveCloudflare: true })` (and `Browser.connect`) has the server watch every tab and solve full-page Cloudflare challenges as they appear. It does not click Turnstile widgets embedded in normal forms. The Go SDK, CLI (`--auto-solve-cloudflare`) and MCP server (`EOKA_AUTO_SOLVE_CLOUDFLARE=1`) use the same server watcher.
245
65
 
246
66
  ```js
247
- import { EokaError } from "@cbxss/eoka";
248
-
67
+ const browser = await Browser.launch({ autoSolveCloudflare: true });
249
68
  try {
250
- await page.fill(target, "Ada", { operationId, timeoutMs: 1000 });
251
- } catch (error) {
252
- if (!(error instanceof EokaError)) throw error;
253
- console.error({
254
- code: error.code,
255
- requestId: error.requestId,
256
- operationId: error.operationId,
257
- requestState: error.requestState,
258
- receipt: error.receipt,
259
- });
260
- if (error.operationId) {
261
- console.log(await browser.operation(error.operationId).get({ timeoutMs: 5000 }));
262
- }
69
+ const page = await browser.newPage("https://1337x.to/");
70
+ console.log(await page.title()); // Torrent Search Engine | 1337x.to
71
+ } finally {
72
+ await browser.close();
263
73
  }
264
74
  ```
265
75
 
266
- `EokaError` is the base for `ConfigurationError`, `InstallationError`, `TransportError`, `ProtocolError`, `ServerOperationError`, and `OperationError`. Installation errors expose stable codes including `UnsupportedPlatform`, `BrowserNotInstalled`, `IntegrityMismatch`, `InstallationFailed`, `InstallationAborted`, `InstallationTimeout`, `ServerPackageMissing`, `ServerPackageMismatch`, and `ReleaseNotPrepared`. Errors preserve available request/operation IDs, dispatch uncertainty, receipt, structured server data, stderr, and cause. `OperationError` also exposes the latest record. These fields are evidence, not a promise that dispatch was prevented. `ServerError` is a generated wire type, not the runtime exception class.
76
+ Tune it with `{ intervalMs, timeoutMs }` (defaults 500 and 30000). The server logs each challenge and result to its stderr. The watcher stops with `browser.close()`.
267
77
 
268
- Stderr diagnostics retain bounded complete lines while redacting credentials, configured proxy secrets, and DevTools endpoint capability details. Truncated partial lines are discarded rather than exposed as potentially unredacted fragments.
78
+ ## Screenshots and recording
269
79
 
270
- When both an operation/lifecycle failure and its cleanup fail, the SDK reports an `AggregateError`. Its `cause` preserves the primary error (also `errors[0]`), including any `operationId`, request state, and receipt; inspect that cause when recovering an operation. The remaining `errors` preserve cleanup failures rather than replacing the original evidence.
271
-
272
- ## Typed reads and invocation
273
-
274
- `Browser` and `Page` implement the generated `InvokeClient` contract:
275
-
276
- ```ts
277
- import type { MethodResults } from "@cbxss/eoka";
278
- import { protocolVersion } from "@cbxss/eoka/protocol";
80
+ ```js
81
+ const png = await page.screenshot(); // Buffer
82
+ await page.screenshot({ format: "webp", quality: 80 });
83
+ await page.screenshotToFile({ path: "./full.png", fullPage: true });
279
84
 
280
- const result: MethodResults["page.evaluate"] = await page.invoke(
281
- "page.evaluate",
282
- { pageId: page.id, js: "({answer: 42, items: [1, null]})" },
283
- { timeoutMs: 5000 },
284
- );
285
- console.log(protocolVersion, result.result);
85
+ const recording = await page.record({ path: "./session.mp4" });
86
+ // ...
87
+ await recording.stop();
286
88
  ```
287
89
 
288
- The method map is generated from the canonical sidecar schemas, including dynamic JSON evaluation results. Use `browser.supports(method)` and `browser.hasCapability(name)` to inspect the actual handshake rather than assuming every generated method is available on an older sidecar. `hello`, `sessionInfo`, `ownership`, and `browserVersion` expose negotiated/session metadata.
289
-
290
- Page conveniences cover text/content/title/URL, element reads/waits, evaluation/execution, screenshots, viewport, browser state, and agent observation/steps. `page.fetch` is the legacy unbounded response API. Prefer `page.fetchBounded` for response-body reads: its default body budget is 8192 bytes and maximum is 1048576 bytes; inspect `truncated`, `bytesRead`, and `bodyOmitted` along with the body/status/headers. The `boundedFetch` capability indicates sidecar support. A bounded read is not the same as a complete response.
90
+ File output never overwrites an existing file, and the directory must already exist. Recordings are silent MP4s. For screenshots larger than 16 MiB, use `screenshotToFile`.
291
91
 
292
- ## Screenshots and native recording
92
+ ## Options
293
93
 
294
94
  ```js
295
- const image = await page.screenshot({
296
- format: "webp",
297
- quality: 80,
298
- clip: { x: 0, y: 0, width: 640, height: 360 },
299
- timeoutMs: 10000,
300
- });
301
- const screenshot = await page.screenshotToFile({
302
- path: "./captures/page.png",
303
- fullPage: true,
304
- });
305
- const recording = await page.record({
306
- path: "./captures/session.mp4",
307
- maxWidth: 1280,
308
- maxHeight: 720,
309
- fps: 30,
95
+ await Browser.launch({
96
+ headless: true, // default
97
+ sandbox: true, // default; leave it on
98
+ download: "auto", // "never" fails when Chrome isn't cached
99
+ browserCacheDir: "/opt/eoka/cache",
100
+ viewport: { width: 1280, height: 720, deviceScaleFactor: 1 },
101
+ timeoutMs: 30000,
310
102
  });
311
- console.log(recording.id, await recording.status());
312
- const video = await recording.stop({ timeoutMs: 60000 });
313
- console.log(screenshot.path, screenshot.bytes, video.path, video.container);
314
103
  ```
315
104
 
316
- Create destination directories first. Relative paths resolve once in the Node caller, not in the sidecar's working directory. File output stages privately beside the destination, flushes/closes, and publishes without overwriting an existing file; there is no overwrite option. An `Artifact` contains `path`, `bytes`, and `mimeType`; completed videos also report `container: "mp4"`. No video Buffer/base64 API is offered.
317
-
318
- Returned artifact paths are canonical and may use Windows' `\\?\` namespace
319
- prefix. Compare filesystem identity, not the spelling of the requested path.
320
-
321
- `screenshot()` returns a PNG Buffer by default and still accepts the original `{signal, timeoutMs}` call options. `format` supports `png`, `jpeg`, and `webp` where Chrome supports them. `quality` is an integer from 0 through 100 for JPEG/WebP and is invalid for PNG. `clip` uses nonnegative CSS-pixel positions and positive sizes. `fullPage` and `clip` are mutually exclusive. Viewport `deviceScaleFactor` is the only render-scale control. Full-page dimensions depend on current layout and Chrome's image limits; prefer a fixed viewport/crop for deterministic output. In-memory screenshots are bounded to 16 MiB raw bytes; `ScreenshotTooLarge` directs callers to `screenshotToFile`, with no automatic retry or fallback.
322
-
323
- Direct file output bypasses the 16 MiB sidecar response limit, not Chrome's image limits or the core's 64 MiB CDP message/frame budget (which includes base64 encoding and JSON). It is not an unbounded streaming screenshot API.
324
-
325
- Capture dispatch requires negotiated methods and capabilities: `screenshotOptions`, `screenshotFile`, and `nativeRecording`. Native recording additionally requires a ready active page and an encoder supported by the actual Chrome build. Unsupported recording raises `RecordingUnsupported`; the SDK never switches engines/browser versions. Video is silent native MP4 with Chrome-selected codec, not a promise of H.264. FFmpeg is not an SDK runtime dependency. `fps` is an integral ceiling from 1 through 120, not deterministic fixed-rate playback; optional `maxWidth`/`maxHeight` are positive integers no greater than 2147483647. Screenshot crops/quality are not recording options.
326
-
327
- Chrome 155.0.8059.39 can emit duplicate MP4 decoding timestamps, including
328
- zero-duration prefixes and terminal tails. The sidecar validates the fragmented
329
- MP4 before publication and applies bounded, lossless timing corrections.
330
- Within a fragment, a run of `k` explicit zero durations becomes `k` one-tick
331
- durations; the following duration decreases by `k` and must remain positive.
332
- The run endpoint and later timestamps remain unchanged. A duplicate final sample
333
- starting a new fragment advances by one tick, with its duration reduced by one
334
- tick and matching fragment decode/index times corrected.
335
- Encoded packets, sample count, file length and the final presentation endpoint
336
- are preserved; clean recordings stay byte-identical.
337
-
338
- This changes container timing metadata, not the codec or encoded frames. It
339
- requires neither a Chrome fork nor FFmpeg. Unsupported or malformed containers,
340
- insufficient donor duration and unresolved cross-fragment timing collisions
341
- fail finalization without publishing a success-named file. Validation/repair uses the original
342
- staging descriptor under a five-second deadline; failure retains partial-file
343
- evidence. The core Rust raw-stream primitive remains unmodified Chrome output.
344
- Release checks require strictly increasing finalized packet DTS and semantically
345
- verified diagnostics, not merely a successful decoder exit. The
346
- [qualification policy](#prerelease-qualification-and-publication) distinguishes
347
- proven frame-rate-estimation advisories from failures without retiming the video.
348
-
349
- `page.record` generates a UUID before dispatch, or accepts a caller-provided `recordingId`. There is one active recorder per target. A repeated start with the same ID and equivalent parameters recovers the existing record; changed parameters conflict instead of restarting. After a lost response use the ID rather than starting another recorder:
105
+ To install Chrome ahead of time, for example while building a Docker image:
350
106
 
351
107
  ```js
352
- import { RecordingError } from "@cbxss/eoka";
353
-
354
- try {
355
- const recording = await page.record({ path: "./captures/session.mp4" });
356
- await recording.stop();
357
- } catch (error) {
358
- if (!(error instanceof RecordingError)) throw error;
359
- const recording = browser.recording(error.recordingId);
360
- const record = await recording.status();
361
- console.log(record.state, record.failure?.stage, record.failure?.partialPath);
362
- }
108
+ import { installBrowser } from "@cbxss/eoka";
109
+ await installBrowser({ browserCacheDir: "/opt/eoka/cache" });
363
110
  ```
364
111
 
365
- Recovery is scoped to the live sidecar session, not crash resume. `Recording.status()` returns the current `RecordingRecord`; `.record` retains the latest observed evidence. States are `running`, `finalizing`, `completed`, `cancelled`, and `failed`. Unknown IDs fail explicitly. `stop()` shares server-side finalization and fulfills only with a completed, published native artifact. Repeated/concurrent stop calls do not stop Chrome twice. Each local waiter has its own signal/deadline; aborting or timing out a waiter does **not** cancel the recorder or finalizer. Recover status or wait again. `cancel()` explicitly releases capture/stream resources and returns a terminal record, including `completed` if publication won the race or `failed` if cleanup failed.
366
-
367
- A sidecar retains at most 1,024 distinct recording IDs and 16 MiB of cumulative
368
- UTF-8 `recordingId`, `pageId`, and resolved `path` bytes. The byte limit bounds
369
- retained start parameters, not exact process memory. Completed, cancelled, and
370
- failed records keep their capacity; IDs are never evicted or reused. At capacity,
371
- new IDs fail with `ServerBusy` before recording or file staging starts. Existing
372
- IDs still recover, and changed parameters still conflict. Start a new
373
- `Browser`/sidecar session for fresh capacity; stopping or cancelling does not
374
- reset history.
375
-
376
- `RecordingError` preserves `recordingId`, `record`, `failure`, `path`, `partialPath`, and `cleanupUncertain`, plus the normal request state/ID, cause, server data, and stderr evidence. Failed/cancelled stop outcomes are errors, never completed artifacts. A retained partial file is not the destination success name. Closing a tab/browser cancels unfinished recordings by default; explicitly await stop to save first. Disconnect/target-loss outcomes preserve honest failure/cleanup uncertainty; closing a borrowed session never kills the borrowed browser.
112
+ To drive a Chrome you already run, use `Browser.connect({ browserWSEndpoint })`. Closing the SDK leaves that browser running.
377
113
 
378
- Error-carried recording records receive the same identity, output-path and completed-artifact checks as successful responses. Inconsistent records raise `Protocol`, retain the rejected wire evidence, and do not replace a handle's known record. Valid later evidence for the same failed terminal recording may still add partial-file or publication details.
114
+ | Environment variable | Purpose |
115
+ | --- | --- |
116
+ | `EOKA_BROWSER_CACHE_DIR` | Where Chrome is cached |
117
+ | `EOKA_RUNTIME_DIR` | Scratch directory for sessions |
118
+ | `EOKA_CHROME_PATH` | Use your own Chrome binary |
119
+ | `EOKA_SERVER_BIN` | Use your own `eoka-server` binary |
120
+ | `HTTPS_PROXY`, `NO_PROXY` | Proxy for the Chrome download |
379
121
 
380
- `examples/capture.mjs OUTPUT_DIRECTORY [BROWSER_CACHE_DIRECTORY]` captures a local animated scene using an installed managed Chrome. It writes fresh screenshots and a silent native MP4 without requiring network or an alternate recorder. Existing output names intentionally fail instead of being replaced.
122
+ ## Errors
381
123
 
382
- ## Connect and cleanup
124
+ Every SDK error extends `EokaError` and has a stable `code`:
383
125
 
384
126
  ```js
385
- const browser = await Browser.connect({
386
- serverPath: "/absolute/path/to/eoka-server",
387
- browserWSEndpoint: "ws://127.0.0.1:9222/devtools/browser/your-browser-id",
388
- });
127
+ import { EokaError } from "@cbxss/eoka";
128
+
389
129
  try {
390
- console.log(browser.ownership, await browser.tabs());
391
- } finally {
392
- await browser.close();
130
+ await page.fill("#name", "Ada");
131
+ } catch (error) {
132
+ if (error instanceof EokaError) console.error(error.code, error.message);
133
+ throw error;
393
134
  }
394
135
  ```
395
136
 
396
- `connect` borrows Chrome; closing the SDK stops its owned sidecar and detaches without closing the borrowed browser. `launch` owns its Chrome session. `close()` is idempotent and must be awaited; async disposal is also supported. Pending local calls are rejected when closing starts. Teardown requests graceful shutdown, then waits within `shutdownTimeoutMs` (45000 ms by default) before terminating the SDK-owned process tree: a private process group on POSIX, or the owned PID tree on Windows. This escalation does not target a separately running borrowed Chrome process.
397
-
398
- Cleanup failures remain errors. The normal owned-Chrome cleanup path is graceful shutdown/sidecar EOF. Forced termination reports cleanup uncertainty: it cannot guarantee removal of runtime files or termination of descendants that left the owned process group/tree. Caller-owned profiles are never an SDK installation cache.
137
+ ## Linux and Docker
399
138
 
400
- If `newPage` was dispatched before a local abort/deadline, the SDK retains its native completion so it can close the exact late-created tab. If that response does not arrive within the bounded cleanup deadline, it closes the owned sidecar and reports `CleanupUncertain`; a borrowed Chrome may retain an unknown tab. That uncertainty is also retained in `Browser.close()` failures and is not evidence that the tab was removed.
139
+ Chrome needs its usual system libraries even in headless mode. On Debian:
401
140
 
402
- ## Development checks
403
-
404
- ```sh
405
- npm run generate:check
406
- npm run typecheck
407
- npm test
408
- npm run test:consumer
141
+ ```dockerfile
142
+ FROM node:24-trixie
143
+ RUN apt-get update && apt-get install -y --no-install-recommends \
144
+ ca-certificates fonts-liberation libasound2t64 libatk-bridge2.0-0t64 libatk1.0-0t64 \
145
+ libcairo2 libcups2t64 libdbus-1-3 libdrm2 libgbm1 libglib2.0-0t64 libnspr4 \
146
+ libnss3 libpango-1.0-0 libssl3t64 libx11-6 libxcb1 libxcomposite1 libxdamage1 \
147
+ libxext6 libxfixes3 libxkbcommon0 libxrandr2 \
148
+ && rm -rf /var/lib/apt/lists/*
149
+ USER node
409
150
  ```
410
151
 
411
- `build` emits JavaScript/declarations (including the installer worker), the pinned release manifest, canonical runtime schema bundle, and license; it does not regenerate protocol outputs. SDK source builds reject unused locals, unused parameters, and switch fallthrough. `typecheck` checks accepted/rejected fixtures and the public SDK consumer against compiled exports. The packed-consumer regression installs with `--ignore-scripts --omit=optional`, checks silent/no-side-effect imports and actionable missing-server errors, compiles the public API consumer, and runs it. The native capture fixture checks the published MP4's file size and container signature rather than accepting a nonempty artifact count.
152
+ Run as a non-root user. On Ubuntu 23.10 and later, AppArmor may block Chrome's sandbox; see [Chromium's AppArmor notes](https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md). Alpine (musl) isn't supported.
412
153
 
413
- For the real outside-repository managed/offline consumer gate, supply a prepared stage and an already verified host Chrome cache:
154
+ ## Examples
414
155
 
415
156
  ```sh
416
- EOKA_RELEASE_STAGE_DIR=/absolute/path/to/new-stage \
417
- EOKA_BROWSER_CACHE_DIR=/absolute/path/to/cache npm run test:consumer
157
+ node node_modules/@cbxss/eoka/examples/install-browser.mjs
158
+ node node_modules/@cbxss/eoka/examples/offline.mjs
159
+ node node_modules/@cbxss/eoka/examples/capture.mjs ./captures
418
160
  ```
419
161
 
420
- Without both variables the staged native/browser test is skipped; import/type tests are not evidence of a native browser launch. The native test packs/installs only local staged SDK/platform tarballs and launches with `download: "never"`. It exercises PNG/JPEG/WebP, DPR/crop/full-page dimensions, equivalent Buffer/file images, existing-file protection, native MP4 stop/recovery/repeated stop, and explicit cancel with no success-named partial. A deterministic 2500×2500 RGB-noise scene verifies that screenshots larger than 16 MiB raise `ScreenshotTooLarge` with direct-file guidance, remain usable through `screenshotToFile`, and do not disconnect the page. Container decoding/observed codec and duration require the separate ffprobe/ffmpeg release smoke; those tools are not SDK runtime dependencies. Actual no-network enforcement, sandbox, container, and all-platform qualification remain separate release gates.
421
-
422
- From the repository root use `mise run node-build`, `node-check`, or `node-consumer`; `node-stage-release -- --artifacts DIR --output NEWDIR --host-only`, `node-install-browser -- CACHE`, and `node-offline -- CACHE` expose the preparation/offline workflows. `npm run example:schema` retains the generated-schema example.
423
-
424
- `mise.toml` pins the development and CI runtime to Node 24.21.0; CI reads that configuration rather than maintaining another Node version. Node types are pinned to `@types/node` 24.19.2. SDK and consumer fixtures target ES2024. Native-package staging inherits the SDK's `engines` field. The Node CI job checks the committed schema projection, accepted/rejected consumers, runtime regressions, and packed imports without requiring Rust or Chrome; the full local `node-check` additionally checks the schema against the Rust exporter. Native gates still require the explicit environment above.
425
-
426
- ## Prerelease qualification and publication
427
-
428
- Core `0.7.0` is published on crates.io. Reserved prerelease versions are
429
- server/protocol crates `0.5.0`, wire protocol `1.3`, and SDK/native npm packages
430
- `0.1.0-beta.1`. Source and ordinary staged packages remain private;
431
- `--publication` is a separate, fail-closed staging mode.
432
-
433
- `.github/workflows/qualify-node-release.yml` builds all five native targets and
434
- qualifies installed tarballs outside the repository. GNU builds use Ubuntu 22.04
435
- and enforce glibc ≤2.35; runtime checks use non-root hosted runners with Chrome's
436
- sandbox enabled. Evidence includes fresh/cache/offline installation, artifact
437
- rejection, verified input, image dimensions, finalized MP4 packet timestamps and
438
- decode diagnostics, headed launch, owned cleanup, and borrowed-browser survival.
439
- Failures retain recordings and diagnostics as workflow artifacts. FFmpeg/ffprobe
440
- are qualification tools, not consumer dependencies.
441
-
442
- The [lossless-repair preview](https://github.com/shrimp-software/eoka-tools/actions/runs/38612635401)
443
- at tools `70b47e0ff27b271407c3073f5c1a389d87a5fd0a` and core
444
- `9bae96b9cefa02794a4058ae54b67273ad453490` completed every runtime check on
445
- Ubuntu 22.04 x64, Ubuntu 24.04 ARM64, macOS 15 x64/ARM64, and Windows 2025 x64.
446
- All 50 one-attempt finalized recordings passed strict packet DTS and empty
447
- decoder diagnostics; all 28 deterministic repair regressions passed on each
448
- architecture. Image, sandbox, headed-launch and ownership checks also passed.
449
- Those jobs ended **blocked** solely by the then-closed source readiness record.
450
- The recording blocker is now cleared using that native evidence plus retained
451
- defective-file repair/preservation proof, not passing live samples alone.
452
- Registry-backed qualification and npm publication prerequisites remain separate.
453
- Live recording still does not promise fixed-cadence export.
454
-
455
- For local host-development evidence, not release qualification:
162
+ ## Development
456
163
 
457
164
  ```sh
458
- mise run node-qualify-release -- --stage /absolute/stage \
459
- --cache /absolute/cache --output /absolute/evidence --preview
165
+ mise install
166
+ npm ci --ignore-scripts --omit=optional
167
+ npm run build
168
+ npm test
460
169
  ```
461
170
 
462
- The workflow resolves `source_ref` to an immutable tools revision and builds
463
- against published registry core `0.7.0`, without a sibling checkout or Cargo
464
- patch. It checks every native build's core identity and exact source lockfile,
465
- including registry checksum
466
- `447a498ec28c34b2020be583617c70f89dc718228bb02db5750f72e4da333a1e`.
467
- Local host-development staging and `--preview` remain separate from release
468
- qualification and cannot authorize publication.
469
-
470
- `scripts/publication-readiness.json` records unresolved release defects. Clearing
471
- a recording blocker requires deterministic repair/preservation regressions and
472
- fresh five-platform qualification, not passing samples alone. Every Chrome pin
473
- update must pass the complete recording suite on each architecture and ten
474
- single-attempt native captures: four short/default-rate clips, two short
475
- 120-fps clips, one 1-fps clip, two two-second clips, and one multi-fragment clip.
476
- Both artifact collection and publication independently require the actual running
477
- Chrome version to match the pin, the complete schedule, published MP4 records,
478
- strictly increasing packet DTS, and successful full decoding. A `passed` summary
479
- alone is insufficient. One known FFmpeg MOV input-rate-estimation diagnostic may
480
- be retained as a VFR advisory only when its adjacent packet indices and exact
481
- timestamps match the probe and the declared positive packet duration exactly
482
- reaches the next timestamp. Missing or inexact timing evidence, unknown
483
- diagnostics, and nonzero decoder exits remain fatal. Raw probe/decoder logs are
484
- preserved, and collection/publication independently recompute advisory
485
- classifications; labels alone cannot authorize release. Probe logging includes
486
- warnings. There is no retry-to-pass, hidden warning filtering, or retiming to
487
- satisfy a frame-rate heuristic. The private MP4 correction remains limited to
488
- the documented native timing defects; changing Chrome's container layout requires
489
- renewed qualification, not an implicit generic muxer or transcoder.
490
-
491
- `publish-node.yml` is manual, restricted to an exact current protected `main`
492
- commit, and publishes only `0.1.0-beta.1` under `next` with npm provenance.
493
- It requires an existing `npm-prerelease` environment with required reviewers
494
- and a single allowed deployment branch, `main`. By default it uses only npm
495
- trusted publishing through OIDC, requires self-review to be disabled, and
496
- requires all six scoped package names to exist with trusted publishers configured
497
- for this repository, workflow, and environment. There is no automatic token fallback.
498
-
499
- For the first release, explicitly dispatch with `bootstrap: true` and an
500
- environment-scoped `NPM_BOOTSTRAP_TOKEN` secret. Use a short-lived npm granular
501
- token authorized to create and publish these scoped packages, with the permissions
502
- required for unattended publication under the account's 2FA policy. Never commit
503
- the token or pass it as a workflow input. Bootstrap still requires environment
504
- reviewer approval, but permits the owner to approve their own deployment; this
505
- exception does not apply to normal OIDC publication.
506
-
507
- Only the bootstrap publish step receives the token. Its temporary private npm
508
- configuration contains an environment-variable reference, not the token value.
509
- Package verification and the final registry installation remain credential-free.
510
- Bootstrap accepts an absent name only when both public and authenticated registry
511
- reads return 404; an existing private package or an authorization failure aborts.
512
- Both modes retain GitHub OIDC provenance and the same qualification checks.
513
-
514
- After the first successful release, configure npm trusted publishers for all six
515
- packages, remove the bootstrap environment secret, revoke its npm token, and
516
- restore `prevent_self_review: true` with an independent environment reviewer before
517
- using normal publication. A bootstrap rerun after a partial upload still needs
518
- the token and must follow the same-run recovery procedure below.
519
-
520
- The publish job accepts only same-run, same-source qualified artifacts and
521
- preflights all six registry versions before writing anything. Existing versions
522
- are skipped only when their SHA-512 integrity matches the qualified tarball,
523
- `next` already points at that version, npm registry signatures verify, and
524
- keyless Sigstore provenance binds the exact artifact, source commit, protected
525
- main workflow, manual event, and original workflow run. The pinned public Sigstore
526
- verifier is release-tooling-only, not an SDK runtime dependency. Registry signature
527
- checks use isolated installs with lifecycle scripts disabled; foreign-platform
528
- packages are installed only for verification, never executed.
529
-
530
- After a partial publication or lost publish response, rerun the failed jobs of
531
- the **same workflow run**, retaining its qualified artifacts and unchanged current
532
- `main` source. Verified existing uploads are preserved; only missing native
533
- packages are published, followed by the SDK. Mismatched integrity, provenance,
534
- tags, source, or unavailable registry evidence abort before any new upload.
535
- There is no automatic publish retry or retagging. If source or artifacts changed,
536
- do not bypass these checks: use a separately reviewed roll-forward release.
537
- The final smoke checks a credential-free registry installation and provenance.
538
-
539
- No tag, merge, or publication is part of PR preparation. Existing Rust publishing
540
- workflows trigger on `main`; merging the version changes is a release action.
171
+ Releases are automatic: merge a version bump to `main` and approve the `npm-prerelease` deployment.