Initial build and package verification

Recorded September 19, 2026 — P0

These results describe the original snapshot, not the current source or release. Local artifact paths are provenance records, not public downloads.

Archive index · Current support

The snapshot exposed eight f32 operations and eight signatures.

Recorded validation

Apple M1 Pro, 10 logical CPUs, 16 GiB, macOS 27; Node 24.19.0, pnpm 12.4.2 and Rust 1.96.0. Node 22.13.0 was additionally checked.

Check	Historical result
Format, lint, types, rustfmt/clippy	Passed
TS / Rust	105 / 2 passed
Local native, dual Wasm, browser entry and missing-native fallback	Passed through the real tarball
Chromium / WebKit	Ten each passed, including relocated Vite assets
Firefox	Ten failed before page loading
Node 22.13.0	Tests and tarball passed; not all later Node 22 patches
Native targets	darwin-arm64 passed; remaining four pending

The full baseline status was failed because Firefox could not start. Its message was Could not find profile folder. Retrying the cached/downloaded browser and an independent profile did not resolve it. The symptom matched the linked Mozilla report; this was not an assertion about laneops page calculations. No system privacy settings were changed.

Evidence and reproduction

artifacts/baseline/p0-2026-09-19-local/ retained report.json, source.tar.gz, benchmark.json, core-benchmark.json, browser/report.json, rebuild.log, node22-test.log and node22-package.log. The archive excluded Git metadata and ignored build directories. A fresh extraction was checked against its file manifest before install and release checks. A new Git checkpoint is required to produce a new Git-source report in that extracted directory.

JS schema v1 records microseconds per call, seven samples, iterations, median, MAD/min/max, warmup policy, environment and asset hashes; Rust emitted JSON Lines. Only the executing native target was marked verified. No speed gate or universal speedup claim was made. The source snapshot was uncommitted.