v0.1.2

v0.1.2

The browser variant could not render on a real node. This is the fix.

WHAT WAS WRONG WITH v0.1.1

HOME pointed at /home/nonroot, which useradd -M never created. Chromium died
before opening a page, with an error about a crash-handler database that names
nothing about a home directory. Every fetch through the chromium backend failed
on a k3s node; a local kind cluster had not shown it, because kind answers the
admission question and this was not that.

HOME is /tmp now, the one path guaranteed writable in every deployment of this
image: a tmpfs in compose, an emptyDir in Kubernetes under a read-only root
filesystem, and the container's own writable layer under a plain docker run.

Measured on a t3.xlarge running k3s, 2026-08-10. NOT reproduced under docker
run locally in any shape tried, so the precise trigger is not isolated and the
fix stands on its own merit rather than on a diagnosis.

ALSO IN THIS TAG

Gates for the last three invariants that were prose: no decision delegated to a
backend, nothing outliving a fetch, nothing claiming compliance. Writing the
first moved a verdict out of the chromium backend, which now takes one decision
function supplied from above and constructs none of its own.

TWO SIZE NUMBERS, BECAUSE ONE MISLEADS

scopyx:v0.1.2 3.5 MB to pull, 15.4 MB on disk
scopyx:v0.1.2-chromium 267 MB to pull, 1.03 GB on disk

Commits

• 867cf47 fix(image): HOME named a directory that does not exist, and v0.1.1 could not render (#17)
• b5553e6 gate: the last three invariants that were prose, and one moved the code (#16)

Support

A 0.x release: only main is supported and fixes are not backported. This Release object was created on 2026-09-12 for a tag cut earlier; the signed checksums, provenance attestation and SBOM that later releases carry start with the next tag.