harden: drop 'unsafe-inline' from style-src (closes #328 )

The popup's markup no longer carries style attributes. The 42 in index.html and in the HTML the view helpers build are now Tailwind classes, each computing to the value it replaced, so style-src is 'self' in both manifests, pinned in tests/manifest.test.js. The address dot's 16 colours are written out as whole classes, because Tailwind builds only the classes it finds in the source. The Settings debug well is shown and hidden with the hidden class, since clearing an inline display no longer uncovers it. Two tests that found the colour dot by its inline style now find it by its class. Script that sets element.style is unaffected. Model: opus-5-5
2026-10-05 12:14:42 +00:00
40 changed files with 566 additions and 1664 deletions
@@ -1,77 +1,7 @@
-# .dockerignore does NOT use .gitignore semantics. Docker matches with
+# .git is deliberately NOT excluded: build.js shells out to `git rev-parse` for
-# moby/patternmatcher: filepath.Match plus `**`, so `*` does not cross
+# build-info stamping and the Dockerfile runs `make build`, so excluding it
-# `/` and an unprefixed pattern is anchored at the context root. Every
+# would make every built extension report commitHash "unknown".
-# depth-independent pattern therefore needs `**/`, or `config/.env` and
+node_modules
-# `certs/server.key` still ship while this file reads as solved. Only
+.DS_Store
-# genuinely root-anchored entries go unprefixed. Never transplant these
+dist
-# into .gitignore, where `**/` is wrong.
+release
 #
 # Matching is case-sensitive, so secrets use character ranges rather
 # than an ALL-CAPS twin, which would still miss `Server.Key`.
 #
 # Extend with this repo's own host-built artifacts, written anchored:
 # `/myapp`, never `**/myapp`, which also matches `cmd/myapp/` and
 # deletes the package directory from the context.
 # .git is sent without its config. Without a VERSION build argument the
 # stage that compiles runs `git describe --tags --always` on .git, which
 # does not need .git/config; that file can hold a credential, such as a
 # password in a remote URL or the token the CI checkout step stores there.
 # Each submodule keeps a config with the same exposure in its git directory
 # under .git/modules/, nested again for a submodule's own submodules, or in
 # its own .git directory when it keeps one.
 # KNOWN GAP: a submodule whose name has a `config` segment (`config`,
 # `deploy/config`, `config/lib`) loses its whole git directory, because
 # `**/.git/modules/**/config` also matches that segment's directory
 # under .git/modules/. Go's version stamping then fails the build;
 # nothing leaks. Name such a submodule without that segment:
 # `git submodule add --name`.
 **/.git/config
 **/.git/modules/**/config
 # Agent scratch: one full checkout of the repo per in-flight agent.
 # Anchored because it occurs once where agents run at the repo root.
 # KNOWN GAP: a repo running agents in subdirectories still ships
 # `services/api/.claude/` and must add its own anchored entry.
 .claude
 # Environment files. `*.env` covers bare `.env` and the `prod.env`
 # convention. Re-include a committed template with a negation if the
 # build needs one: `!docs/example.env`.
 **/*.[eE][nN][vV]
 **/.[eE][nN][vV].*
 **/.[eE][nN][vV][rR][cC]
 # Private keys and the bundles carrying them. Public certificates
 # (*.crt, *.cer) are deliberately absent: they are legitimate inputs.
 **/*.[pP][eE][mM]
 **/*.[kK][eE][yY]
 **/*.[pP]12
 **/*.[pP][fF][xX]
 **/[iI][dD]_[rR][sS][aA]
 **/[iI][dD]_[dD][sS][aA]
 **/[iI][dD]_[eE][cC][dD][sS][aA]
 **/[iI][dD]_[eE][cC][dD][sS][aA]_[sS][kK]
 **/[iI][dD]_[eE][dD]25519
 **/[iI][dD]_[eE][dD]25519_[sS][kK]
 # Dependencies: restored inside the image, never copied in.
 **/node_modules
 # OS metadata.
 **/.DS_Store
 **/Thumbs.db
 # Editor state: never a build input, and it churns COPY.
 **/*.swp
 **/*.swo
 **/*~
 **/*.bak
 **/.idea
 **/.vscode
 **/*.sublime-*
 # This repo's host-built artifacts: make build writes dist/ and make package
 # writes release/. The image builds its own.
 /dist
 /release
@@ -2,11 +2,11 @@ name: e2e
 on: [push]
 # The browser end-to-end suites, one job per browser, deliberately kept out
-# of the check workflow: REPO_POLICIES.md caps make test at 60 seconds and
+# of the check workflow: REPO_POLICIES.md caps make test at 20 seconds and
-# script/cibuild runs script/check, so folding a browser suite into either
+# script/cibuild is a plain `docker build .` whose Dockerfile runs
-# would blow that cap and slow the local fast path. Before this workflow
+# make check, so folding a browser suite into either would blow that cap
-# every browser-level guarantee in this repo held only when a human
+# and slow the local fast path. Before this workflow every browser-level
-# remembered to run it.
+# guarantee in this repo held only when a human remembered to run it.
 #
 # One job per browser rather than two steps in one job, so a Chrome failure
 # does not hide the Firefox result.
@@ -35,10 +35,6 @@ on: [push]
 jobs:
    e2e-chrome:
        runs-on: ubuntu-latest
        # Bounds the image build, a cold cache included, and both Chrome
        # programs, so a hung browser frees the shared runner. README.md
        # "In CI" has the measured times.
        timeout-minutes: 20
        steps:
            # actions/checkout v4.2.2, 2026-02-22
            - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
@@ -46,10 +42,6 @@ jobs:
    e2e-firefox:
        runs-on: ubuntu-latest
        # Bounds the image build, a cold cache included, and both Firefox
        # programs, so a hung browser frees the shared runner. README.md
        # "In CI" has the measured times.
        timeout-minutes: 15
        steps:
            # actions/checkout v4.2.2, 2026-02-22
            - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
@@ -11,40 +11,14 @@ Thumbs.db
 .vscode/
 *.sublime-*
 # Agent scratch (worktrees of this repo, created and destroyed by
 # in-flight tooling). Unanchored: .gitignore patterns already match at
 # every depth, so no prefix is wanted here. This is not a .dockerignore
 # entry and must not be given a `**/` prefix on the way into one.
 .claude/
 # Node
 node_modules/
-# Secrets. Unanchored like every entry above, so each matches at every
+# Environment / secrets
-# depth. Matching is case-sensitive on Linux, so names use character
+.env
-# ranges rather than a lowercase form that misses `Server.Key`.
+.env.*
-
+*.pem
-# Environment files. `*.env` covers bare `.env` and the `prod.env`
+*.key
 # convention. Only the templates `example.env` and `sample.env` are
 # re-included below. A repository that commits any other template adds
 # its own negation after these lines, for example `!.env.example`.
 *.[eE][nN][vV]
 .[eE][nN][vV].*
 .[eE][nN][vV][rR][cC]
 !example.env
 !sample.env
 # Private keys and the bundles carrying them.
 *.[pP][eE][mM]
 *.[kK][eE][yY]
 *.[pP]12
 *.[pP][fF][xX]
 [iI][dD]_[rR][sS][aA]
 [iI][dD]_[dD][sS][aA]
 [iI][dD]_[eE][cC][dD][sS][aA]
 [iI][dD]_[eE][cC][dD][sS][aA]_[sS][kK]
 [iI][dD]_[eE][dD]25519
 [iI][dD]_[eE][dD]25519_[sS][kK]
 # Build output
 dist/
@@ -1,2 +1,5 @@
 node_modules/
 yarn.lock
 dist/
 release/
 .claude/
@@ -1,80 +1,41 @@
 # Lint phase: ESLint, prettier --check, and script/check-censored. The tools
 # are invoked directly rather than through `make lint` or `script/lint`, which
 # are themselves a docker build and would recurse into a daemon that does not
 # exist in a build step.
 #
 # node:22-slim (22.x LTS), 2026-02-24
-FROM node@sha256:5373f1906319b3a1f291da5d102f4ce5c77ccbe29eb637f072b6c7b70443fc36 AS lint
+FROM node@sha256:5373f1906319b3a1f291da5d102f4ce5c77ccbe29eb637f072b6c7b70443fc36 AS base
 WORKDIR /app
 # Marks "already inside the lint container" for script/lint, which otherwise
 # shells out to docker to build the lint stage below. Nothing outside this
 # image sets it.
 ENV AUTISTMASK_LINT_NATIVE=1
 # script/test's default 30s bound is the host figure. In here the same suite
 # starts on a cold jest cache and shares the runner with the rest of the build,
 # so 30s is too tight — it killed a healthy suite at 30.6s on a cold CI cache.
 # 180s still catches a hang in three minutes and cannot be tripped by a suite
 # that is merely running on contended hardware.
 ENV AUTISTMASK_TEST_TIMEOUT=180
 # script/bootstrap installs all prerequisites (make via apt here; node
 # is already in the base image, yarn comes via corepack) and runs
 # yarn install --frozen-lockfile. Dependency manifests are copied first
 # so the bootstrap layer is cached until they change.
 COPY script/ script/
 COPY package.json yarn.lock ./
 RUN script/bootstrap
 COPY . .
-RUN yarn run lint
+# Lint stage — fail fast on static analysis and formatting, before the tests
-RUN script/check-censored
+# and the build. This is also the stage script/lint builds from a host, which
-
+# is how linting stays on the pinned ESLint rather than the host's.
-# Test phase, same shape and for the same reason: the jest suite (its worker
+FROM base AS lint
-# cap is in package.json), rerun verbose on failure, then
+RUN make lint
 # script/test-verify-build.
 #
 # node:22-slim (22.x LTS), 2026-02-24
 FROM node@sha256:5373f1906319b3a1f291da5d102f4ce5c77ccbe29eb637f072b6c7b70443fc36 AS test
 WORKDIR /app
 COPY script/ script/
 COPY package.json yarn.lock ./
 RUN script/bootstrap
 COPY . .
 RUN timeout 90 yarn run test || \
    { echo "--- Rerunning with --verbose for details ---"; \
      timeout 90 yarn run test:verbose; exit 1; }
 RUN script/test-verify-build
 # Development environment with the extension built, and the last stage: a
 # plain `docker build .` names no target and so builds this one. Nothing is
 # wanted from the two phases above; the copies are what make BuildKit build
 # them first, so this image cannot be produced unless lint and test passed. A
 # stage appended after this one would drop all three out of a plain build.
 #
 # node:22-slim (22.x LTS), 2026-02-24
 FROM node@sha256:5373f1906319b3a1f291da5d102f4ce5c77ccbe29eb637f072b6c7b70443fc36
 WORKDIR /app
 # Full check and build. The COPY --from is a no-op file copy whose only job is
 # to make BuildKit finish the lint stage before this one starts; without it the
 # stages run in parallel and a lint failure would not fail the build early.
 FROM base AS check
 COPY --from=lint /app/package.json /dev/null
 COPY --from=test /app/package.json /dev/null
-# script/bootstrap installs all prerequisites, git included. Manifests are
+RUN make check
-# copied first so that layer stays cached until dependencies change.
+RUN make build
 COPY script/ script/
 COPY package.json yarn.lock ./
 RUN script/bootstrap
 # A tar-stream context keeps the sender's file owners, which git refuses.
 RUN git config --system --add safe.directory /app
 COPY . .
 # The VERSION build arg when one is given, otherwise
 # `git describe --tags --always` on the .git in the build context. With .git
 # present, a version that is still empty, dev or unknown fails the build: git
 # is missing or could not read the checkout, and build.js, which stamps the
 # extension with the commit it was built from, would stamp "unknown".
 ARG VERSION
 RUN VERSION="${VERSION:-$(git describe --tags --always)}"; \
    if [ -e .git ]; then \
        case "$VERSION" in ""|dev|unknown) \
            echo "version is '$VERSION' although .git is present" >&2; \
            exit 1 ;; \
        esac; \
    fi; \
    make build
 # A LABEL cannot run git, so it carries the build argument alone; a plain
 # `docker build .` leaves it empty.
 LABEL org.opencontainers.image.version="${VERSION}"
@@ -107,14 +107,6 @@ vendor-blocklist:
 clean:
 	@rm -rf dist/ release/
 # Run the build make build runs, without the checks that follow it, then run it
 # again after every change to a file under src/, manifest/ or icons/, until
 # interrupted. A failed build is reported, may leave dist/ partly written, and
 # watching carries on. It writes no build receipt, so nothing can verify what it
 # leaves in dist/: anything handed on comes from make build. A release build
 # unless AUTISTMASK_DEBUG=1 is exported. A change anywhere else, package.json
 # and build.js included, starts no build, and a directory created while it runs
 # is not watched; restart it after either.
 dev:
 	@echo "Building in watch mode..."
 	@yarn run build --watch 2>&1
@@ -222,32 +222,31 @@ provide:
 - `script/setup` — make a fresh clone ready for development: bootstrap plus the
  git pre-commit hook
 - `script/projectname` — print the project name (used for the Docker image tag)
- `script/test` — build the Dockerfile's `test` phase, uncached: the jest suite,
+- `script/test` — run the test suite (jest)
  stopped after 90 seconds and rerun verbose if it fails, then
  `script/test-verify-build`
 - `script/test-e2e` — run the Chrome browser end-to-end suite (docker is the
  only prerequisite: it builds a pinned image that carries the repo and a fresh
  extension build, see [End-to-End Tests](#end-to-end-tests))
 - `script/test-e2e-firefox` — run the Firefox browser end-to-end suite (same,
  against an image with a pinned Firefox and geckodriver, see
  [End-to-End Tests](#end-to-end-tests))
- `script/lint` — build the Dockerfile's `lint` phase, uncached: ESLint
+- `script/lint` — run ESLint (`eslint.config.js`) and then `prettier --check`,
-  (`eslint.config.js`), `prettier --check`, then `script/check-censored`,
+  failing on either. It never writes: `--fix` is not in this path, so
-  failing on any of them. It never writes: `--fix` is not in this path, so
+  `make check` stays non-mutating. Linting runs in the container — the script
-  `make check` stays non-mutating. Linting runs only in the container, because
+  builds the Dockerfile's `lint` stage — because an ESLint result that depends
-  an ESLint result that depends on whichever ESLint the host happens to have is
+  on whichever ESLint the host happens to have is not a result. Docker is
-  not a result, so docker is required to lint.
+  therefore required to lint; inside that image `AUTISTMASK_LINT_NATIVE=1` makes
- `script/fmt` — format all files (writes), on the host
+  the same script lint in place instead of recursing.
- `script/fmt-check` — check formatting (read-only), on the host
+- `script/fmt` — format all files (writes)
- `script/check` — run `script/test`, `script/lint` and `script/fmt-check`
+- `script/fmt-check` — check formatting (read-only)
 - `script/check` — run test, test-verify-build, check-censored, lint, and
  fmt-check
 - `script/check-censored` — assert the competitor name RULES.md bars appears
  nowhere in the working tree or under `dist/` outside its documented
  exceptions: the pinned source reference in `script/vendor-blocklist`, the two
  provider-shim identifiers in `src/content/inpage.js`, and one ERC-20's
  on-chain name in `src/shared/tokenList.js`. Each is scoped to that path and
-  fails anywhere else. Run by the `lint` phase, so part of `make check`; it
+  fails anywhere else. Part of `make check`, which inspects `dist/` when there
-  inspects `dist/` when there is one and says loudly when there is not, and the
+  is one and says loudly when there is not; `make build` re-runs it with
  build context of that phase never has one. `make build` re-runs it with
  `--require-dist`, so a build artifact is always covered
 - `script/package` — produce the release artifacts: `make build` first, so the
  archives can only ever be made from a `dist/` that has been verified against
@@ -282,23 +281,14 @@ provide:
  failing and a succeeding release build step, and read the `make build` and
  `make build-debug` recipes back out of `make -n` to check that they pass the
  mode as an argument on a scrubbed environment and wrap only the release path.
-  Run by the `test` phase, so part of `make check`; it reads no build artifacts
+  Part of `make check`; it reads no build artifacts and writes nothing under
-  and writes nothing under `dist/`. The cases that depend on file permissions
+  `dist/`. The cases that depend on file permissions cannot mean anything for a
-  cannot mean anything for a process that is not subject to them, so the harness
+  process that is not subject to them, so the harness proves its runner against
-  proves its runner against a mode-000 file before counting them, dropping to an
+  a mode-000 file before counting them, dropping to an unprivileged user when
-  unprivileged user when run as root; if it cannot, it skips those cases and
+  run as root; if it cannot, it skips those cases and says so in a banner rather
-  says so in a banner rather than passing them.
+  than passing them.
- `script/docker` — build the Docker image, uncached and tagged via
+- `script/docker` — build the Docker image tagged via `script/projectname`
-  `script/projectname`: the `lint` and `test` phases, then `make build` in the
+- `script/cibuild` — CI entrypoint: plain `docker build .`
  last stage. It passes what `git describe --tags --always --dirty` prints on
  the host as the `VERSION` build argument, or `unknown` when that prints
  nothing, and the last stage fails on `unknown` whenever the build context
  carries `.git`. Only a build given no `VERSION` at all, such as a plain
  `docker build .`, runs `git describe` on the `.git` in the build context,
  which `.dockerignore` sends without its `config`, and fails if git cannot read
  it
 - `script/cibuild` — CI entrypoint: `script/bootstrap`, `script/check`, then the
  same image build as `script/docker`
 - `script/precommit` — run by the git pre-commit hook; runs `script/check`
 - `script/install-precommit` — install the git pre-commit hook
@@ -316,15 +306,7 @@ The Makefile shims to those. It also carries a few targets that have no
  debug build, and keeping its `dist/` on failure (see
  [Debug Builds](#debug-builds))
 - `make clean` — remove `dist/` and `release/`
- `make dev` — run the build `make build` runs, without the checks that follow
+- `make dev` — build in watch mode
  it, then run it again after every change to a file under `src/`, `manifest/`
  or `icons/`, until interrupted. A failed build is reported, may leave `dist/`
  partly written, and watching carries on. It writes no build receipt, so
  nothing can verify what it leaves in `dist/` (see
  [Build Receipts](#build-receipts)): anything handed on comes from
  `make build`. A release build unless `AUTISTMASK_DEBUG=1` is exported. A
  change anywhere else, `package.json` and `build.js` included, starts no build,
  and a directory created while it runs is not watched; restart it after either
 ## End-to-End Tests
@@ -394,12 +376,6 @@ reserve while sitting on the same side of the estimate, so swapping the two in
 what [#154](https://git.eeqj.de/sneak/AutistMask/issues/154) was, and it was
 previously correct by reading only.
 It also covers both ways the wait for a sent transaction's receipt ends on the
 error screen: lookups that still find no receipt 60 seconds after the broadcast,
 and six lookups in a row that fail. Each must show its own message, and Done
 must lead back to the address screen. Both wait in real time, about a minute
 each.
 It also covers the **dApp approval round trips** — the one place where the
 content script, the inpage provider, the background worker and the approval
 popup all have to work together. A local test page is served by the route
@@ -627,7 +603,7 @@ Two limits are worth knowing, both real differences from the Chrome suite:
  out, but it cannot report which requests were attempted.
 Neither `make test-e2e` nor `make test-e2e-firefox` is part of `make check` or
-`make test`. `REPO_POLICIES.md` caps `make test` at 60 seconds and a browser
+`make test`. `REPO_POLICIES.md` caps `make test` at 20 seconds and a browser
 suite does not fit; nothing in `tests/e2e/` is named `*.test.js`, so jest cannot
 pick it up either. Run them locally before changing anything under
 `src/popup/views/`.
@@ -636,7 +612,7 @@ pick it up either. Run them locally before changing anything under
 `.gitea/workflows/e2e.yml` runs both suites on every push, as two jobs —
 `e2e-chrome` and `e2e-firefox` — separate from the `check` workflow, so the
-60-second `make test` cap and the local fast path are untouched. Each job is a
+20-second `make test` cap and the local fast path are untouched. Each job is a
 checkout and the matching `script/` entrypoint, nothing else.
 Docker is the only thing either job needs from the runner, and that is not an
@@ -661,22 +637,10 @@ Nothing in either job can pass vacuously. There is no `continue-on-error` and no
 build fails, and when the browser fails to start; the Chrome harness aborts the
 suite outright if its network interception is not in effect.
-Measured on this repo's runner in the green runs of early October 2026, from a
+Measured on this repo's runner: `e2e-chrome` about 1m55s cold, almost all of it
-warm docker cache to a cold one: `e2e-chrome` 1m44s to 4m48s, and `e2e-firefox`
+the one-time pull of the pinned ~800MB Playwright layer, and well under a minute
-31s to 4m07s. A cold cache adds three to four minutes to each job, spent
+once that layer is cached. `e2e-firefox` about 1m05s cold, and it caches its
-rebuilding its image: reinstalling dependencies and, for `e2e-firefox`,
+Firefox and geckodriver downloads the same way.
 installing Firefox, geckodriver and their system libraries. Both scripts now
 build their image with `--no-cache`, so every run pays the cold figure. Those
 `e2e-chrome` runs predate the cases that wait in real time for a receipt to end
 in error. `make test-e2e` took 3m51s locally with its image cached, so with the
 image rebuilt every run, an `e2e-chrome` run comes to about seven minutes.
 Each e2e job has a `timeout-minutes` cap, so a hung build or browser ends the
 job instead of holding the shared runner: `e2e-firefox` 15 minutes and
 `e2e-chrome` 20, each over two and a half times the job's slowest cold run. A
 job that reaches its cap has hung; read it as a hang, not as a slow run to
 retry. The `check` job has no cap: `.gitea/workflows/check.yml` is the canonical
 copy from `sneak/prompts`, kept byte-identical.
 ### Element id guard (part of `make check`)
@@ -2218,8 +2182,8 @@ Dev dependencies (not shipped in extension):
 | Package            | Version | License | Purpose                   |
 | ------------------ | ------- | ------- | ------------------------- |
 | `esbuild`          | 0.27.3  | MIT     | JS bundler (inlines deps) |
-| `tailwindcss`      | 4.3.1   | MIT     | CSS compilation           |
+| `tailwindcss`      | 4.2.1   | MIT     | CSS compilation           |
-| `@tailwindcss/cli` | 4.3.1   | MIT     | Tailwind CLI              |
+| `@tailwindcss/cli` | 4.2.1   | MIT     | Tailwind CLI              |
 | `jest`             | 30.2.0  | MIT     | Test runner               |
 | `prettier`         | 3.8.1   | MIT     | Code formatter            |
@@ -1,6 +1,6 @@
 ---
 title: Repository Policies
-last_modified: 2026-10-04
+last_modified: 2026-07-06
 ---
 This document covers repository structure, tooling, and workflow standards. Code
@@ -60,28 +60,17 @@ style conventions are in separate documents:
  prerequisite since nvm requires bash. yarn is then pinned via
  `corepack prepare yarn@<version> --activate`. Never install "latest" or "lts";
  always exact versions. `script/cibuild` runs the CI build: it changes to the
-  repo root, runs `script/bootstrap`, runs `script/check`, and builds the image
+  repo root and runs `docker build .`; the Gitea workflow calls it. Four further
-  with the version; the Gitea workflow calls it. **`script/cibuild` runs
+  scripts are our own extensions to the standard: `script/check` runs
-  `script/bootstrap` first**, because the workflow checks out the repo and runs
+  `script/test`, `script/lint`, and `script/fmt-check`; `script/precommit` is
-  nothing else, while `script/fmt-check` runs the formatter on the host: on a
+  what the git pre-commit hook runs, and it calls `script/check`;
-  pristine checkout with nothing installed the run dies there, after the
+  `script/install-precommit` installs the git pre-commit hook (the `make hooks`
-  containerised gates have passed. **The bootstrap alone is not enough**:
+  target shims to it); and `script/projectname` (literally that filename) simply
-  `script/bootstrap` installs node and yarn under nvm and leaves neither on the
+  outputs the project's name. Scripts that need the name call
-  `PATH` of the shell that called it, so a bare `yarn` still exits 127. The host
+  `script/projectname` — e.g. `script/docker` assembles its image tag from it —
-  entrypoints that need yarn — `script/fmt` and `script/fmt-check` — therefore
+  so those scripts stay byte-identical across all repos. Repo-type-specific
-  source nvm for the pinned node version before invoking it, exactly as
+  pre-commit extras (e.g. `go mod tidy` verification in Go repos) belong in
-  `script/bootstrap`'s own install step does. A runner carrying nothing but
+  `script/precommit`, not in the hook itself. Model scripts are at
  docker and git then gets through `script/check`. Four further scripts are our
  own extensions to the standard: `script/check` runs `script/test`,
  `script/lint` and `script/fmt-check`; `script/precommit` is what the git
  pre-commit hook runs, and it calls `script/check`; `script/install-precommit`
  installs the git pre-commit hook (the `make hooks` target shims to it); and
  `script/projectname` (literally that filename) simply outputs the project's
  name. Scripts that need the name call `script/projectname` — e.g.
  `script/docker` assembles its image tag from it — so those scripts stay
  byte-identical across all repos. Repo-type-specific pre-commit extras (e.g.
  `go mod tidy` verification in Go repos) belong in `script/precommit`, not in
  the hook itself. Model scripts are at
  `https://git.eeqj.de/sneak/prompts/raw/branch/main/script/<name>`. The README
  must document the provided scripts in an **Entrypoints** section (see the
  README requirements below).
@@ -100,198 +89,87 @@ style conventions are in separate documents:
  contributor should be able to understand the entire development workflow by
  reading the Makefile.
- Every repo should have a `Dockerfile`, and it carries the repo's gates: a
+- Every repo should have a `Dockerfile`. All Dockerfiles must run `make check`
-  `lint` phase and a `test` phase, with the final stage depending on both so the
+  as a build step so the build fails if the branch is not green. For non-server
-  image cannot be built unless they pass. For non-server repos the final stage
+  repos, the Dockerfile should bring up a development environment and run
-  brings up a development environment; for server repos it is the runtime image.
+  `make check`. For server repos, `make check` should run as an early build
-  The gate phases and the build stage start from their pinned base images and
+  stage before the final image is assembled. Dockerfiles install development
-  install what those images lack either inline, as the canonical Go `Dockerfile`
+  prerequisites by running `script/bootstrap` rather than duplicating installs
-  below does for `git`, or by running `script/bootstrap`, as the `prompts`
+  inline; COPY `script/` and the dependency manifests (`package.json` +
-  repo's own `Dockerfile` does for its yarn packages. The development
+  `yarn.lock`, `go.mod` + `go.sum`, etc.) before running it so the bootstrap
-  environment stage installs development prerequisites by running
+  layer stays cached until dependencies change.
  `script/bootstrap` rather than duplicating its installs inline. A stage that
  runs `script/bootstrap` COPYs `script/` and the dependency manifests
  (`package.json` + `yarn.lock`, `go.mod` + `go.sum`, etc.) before running it.
- **Linting and testing run in Docker, as phases of the `Dockerfile`.** There is
+- **Dockerfiles must use a separate lint stage for fail-fast feedback.** Go
-  no separate lint file. `script/lint` and `script/test` each build one phase
+  repos use a multistage build where linting runs in an independent stage based
-  and nothing else:
+  on the `golangci/golangci-lint` image (pinned by hash). This stage runs
  `make fmt-check` and `make lint` before the full build begins. The build stage
  then declares an explicit dependency on the lint stage via
  `COPY --from=lint /src/go.sum /dev/null`, which forces BuildKit to complete
  linting before proceeding to compilation and tests. This ensures lint failures
  surface in seconds rather than minutes, without blocking on dependency
  download or compilation in the build stage.
-    ```sh
+    The standard pattern for a Go repo Dockerfile is:
    docker build --no-cache --target lint -t "$(script/projectname)-lint" .
    docker build --no-cache --target test -t "$(script/projectname)-test" .
    ```
    **A stage that is not the last one in the file is built only when the final
    stage's chain depends on it, or when `--target` names it.** That is why the
    two gates are always invoked by name here, and why the final stage carries a
    `COPY --from=` of a harmless file from each of them: without that edge a
    plain `docker build .` builds the last stage alone and exits 0 having linted
    and tested nothing.
    **Every `docker build` in `script/` is tagged**, here and in
    `script/cibuild` and `script/docker`. An untagged build leaves a dangling
    image behind on every invocation, on every developer host and every CI
    runner; a tagged one replaces the previous image.
    Inside a phase the tool is invoked directly — `golangci-lint`, `go test`,
    `eslint`, `prettier` — never through `make lint` or `script/test`, which are
    themselves a `docker build` and would recurse into a daemon that does not
    exist in a build step. Formatting is the exception and stays on the host:
    `script/fmt` writes the working tree, and `script/fmt-check` is its
    read-only twin.
    **No lint verdict may come from a host invocation of the linter.** On a
    shared host golangci-lint reads a result cache keyed on file content rather
    than location, so a second checkout of the same content is served the first
    one's findings, and a host-global lock in `$TMPDIR` makes concurrent runs
    exit non-zero with `parallel golangci-lint is running` — a status a caller
    cannot tell from real findings. Both have produced wrong verdicts in this
    org, in both directions. A container has its own cache, its own `TMPDIR` and
    a digest-pinned binary, so neither is reachable.
 - **Any build that runs checks is built with `--no-cache`.** Docker invalidates
  a `COPY` layer only when the copied content changes, so on an unchanged tree
  the check `RUN` is served from cache, nothing executes, and the build still
  exits 0. Every `docker build` in `script/` therefore passes `--no-cache`:
  `script/lint`, `script/test`, `script/cibuild` and `script/docker` are the
  four, and there is no fifth — `script/check` runs the two gate phases and
  `script/fmt-check`, and builds no image of its own. A bare `docker build .` is
  not evidence that anything ran: a sub-second build reporting success is a
  cache hit, not a result. Never invalidate by pruning — `docker builder prune`
  and friends destroy a build cache shared with every other build on the host.
  When a check is added or changed, prove it works by planting a defect it must
  catch and watching the run fail on it, then revert the defect. A green run
  alone shows neither that the check ran nor that it covers what it should.
 - **The gate phases are separate stages, and the build stage depends on both.**
  The lint phase is based on the `golangci/golangci-lint` image (pinned by
  hash), so lint failures surface in seconds rather than after a full compile,
  and the test phase is based on the Debian Go image. The canonical Go repo
  `Dockerfile`:
    ```dockerfile
-    # Lint phase
+    # Lint stage — fast feedback on formatting and lint issues
    # golangci/golangci-lint:v2.x.x, YYYY-MM-DD
    FROM golangci/golangci-lint@sha256:... AS lint
    WORKDIR /src
    COPY go.mod go.sum ./
    RUN go mod download
    COPY . .
-    RUN golangci-lint run --config .golangci.yml ./...
+    RUN make fmt-check
    RUN make lint
-    # Test phase. -race needs cgo and so a C compiler, which the Debian Go
+    # Build stage
    # image ships and the alpine one does not.
    # golang:1.x, YYYY-MM-DD
    FROM golang@sha256:... AS test
    WORKDIR /src
    COPY go.mod go.sum ./
    RUN go mod download
    COPY . .
    RUN go test -timeout 90s -race -cover ./... || \
        { echo "--- Rerunning with -v for details ---"; \
          go test -timeout 90s -race -v ./...; exit 1; }
    # Build stage. Nothing is wanted from either phase above; the copies
    # are what make BuildKit build them first, so this stage cannot run
    # unless lint and test passed.
    # golang:1.x-alpine, YYYY-MM-DD
    FROM golang@sha256:... AS builder
    COPY --from=lint /src/go.sum /dev/null
    COPY --from=test /src/go.sum /dev/null
    RUN apk add --no-cache git
    # A tar-stream context keeps the sender's file owners, which git refuses.
    RUN git config --system --add safe.directory /src
    WORKDIR /src
    # Force BuildKit to run the lint stage before proceeding
    COPY --from=lint /src/go.sum /dev/null
    COPY go.mod go.sum ./
    RUN go mod download
    COPY . .
    RUN make test
-    # The VERSION build arg when one is given, otherwise
+    ARG VERSION=dev
-    # `git describe --tags --always` on the .git in the build context. With
+    RUN CGO_ENABLED=0 go build -trimpath \
    # .git present, a version that is still empty, dev or unknown fails the
    # build: git is missing or could not read the checkout.
    ARG VERSION
    RUN VERSION="${VERSION:-$(git describe --tags --always)}"; \
        if [ -e .git ]; then \
            case "$VERSION" in ""|dev|unknown) \
                echo "version is '$VERSION' although .git is present" >&2; \
                exit 1 ;; \
            esac; \
        fi; \
        CGO_ENABLED=0 go build -trimpath \
        -ldflags="-s -w -X main.Version=${VERSION}" \
        -o /app ./cmd/app/
-    # Runtime stage, and the last one
+    # Runtime stage
    FROM alpine@sha256:...
    COPY --from=builder /app /usr/local/bin/app
    ENTRYPOINT ["app"]
    ```
    Key points:
-    - The lint phase uses the `golangci/golangci-lint` image directly (it has
+    - The lint stage uses the `golangci/golangci-lint` image directly (it
-      both Go and the linter), so nothing needs installing.
+      includes both Go and the linter), so there is no need to install the
-    - `COPY --from=<phase> /src/go.sum /dev/null` is a no-op copy whose only
+      linter separately.
-      purpose is the ordering edge. BuildKit runs stages in parallel by default,
+    - `COPY --from=lint /src/go.sum /dev/null` is a no-op file copy that creates
-      and a stage nothing depends on is not built at all, so without these two
+      a stage dependency. BuildKit runs stages in parallel by default; without
-      lines a red gate would not fail the build.
+      this line, the build stage would not wait for lint to finish and a lint
-    - Keep the runtime stage last, and if you add a stage after it, give it the
+      failure might not fail the overall build.
      same two copies. A plain `docker build .` builds the last stage's chain
      and nothing else.
    - If the project uses `//go:embed` directives that reference build artifacts
-      (e.g. a web frontend compiled in a separate stage), the lint phase must
+      (e.g. a web frontend compiled in a separate stage), the lint stage must
      create placeholder files so the embed directives resolve. Example:
      `RUN mkdir -p web/dist && touch web/dist/index.html web/dist/style.css`.
-    - If the project requires CGO or system libraries for linting, install them
+      The lint stage should not depend on the actual build output — it exists to
-      in the lint phase. The `golangci/golangci-lint` image is Debian-based and
+      fail fast.
-      has no `apk`, so install with `apt-get` under the Debian package name
+    - If the project requires CGO or system libraries for linting (e.g.
-      (`libvips-dev`, where alpine says `vips-dev`), and delete the package
+      `vips-dev`), install them in the lint stage with `apk add`.
-      lists in the same `RUN`, so the layer does not keep them:
+    - The build stage runs `make test` after compilation setup. Tests run in the
-
+      build stage, not the lint stage, because they may require compiled
-        ```dockerfile
+      artifacts or heavier dependencies.
        RUN apt-get update \
            && apt-get install -y --no-install-recommends libvips-dev \
            && rm -rf /var/lib/apt/lists/*
        ```
    - `.dockerignore` lets `.git` into the build context. It keeps out every git
      `config` at any depth (`**/.git/config`, `**/.git/modules/**/config`): the
      repository's own, each submodule's under `.git/modules/`, and that of a
      submodule keeping its own `.git` directory. `git describe` does not need
      them, and each can hold a credential: a password in a remote URL, or the
      token the CI checkout step stores there. A submodule whose name has a
      `config` segment (`config`, `deploy/config`, `config/lib`) loses its whole
      git directory to `**/.git/modules/**/config`, and Go's version stamping
      then fails the build: give it a name without that segment
      (`git submodule add --name`). The stage that compiles has `git` (the
      Debian Go image has it; an alpine one needs `apk add --no-cache git`) and
      takes the version from the `VERSION` build argument when one is given,
      otherwise from `git describe --tags --always`. That gives the tag on a
      tagged commit; on a later commit, the tag, the number of commits since it
      and the short commit (`v1.2.3-4-gabc1234`); and the short commit when no
      tag is reachable. The stage that compiles also marks its working directory
      safe for git (`git config --system --add safe.directory /src`): a context
      sent as a tar stream keeps the sender's file owners, and git refuses a
      checkout owned by another user, so the version would come out empty.
      `ARG VERSION` has no default, and the build fails if the context carries
      `.git` and the version still comes out empty, `dev` or `unknown`. A plain
      `docker build .` with no build arguments must succeed; a Dockerfile that
      refuses an empty build argument drops that refusal and keeps the argument.
 - Every repo should have a Gitea Actions workflow (`.gitea/workflows/`) that
-  runs `script/cibuild` on push, and checks out the repo as its only other step.
+  runs `script/cibuild` (which runs `docker build .`) on push. Since the
-  That script bootstraps, runs the gate phases, and then builds the image, so a
+  Dockerfile already runs `make check`, a successful build implies all checks
-  successful run means every check passed; a bare `docker build .` does not
+  pass.
  carry the same guarantee, because its gate phases may come from the cache. The
  image build is uncached and so runs the gate phases a second time. That is the
  price of the rule above, and it is worth paying: the image that ships is built
  from a run of its own gates rather than from a cache entry. A separate
  workflow limited to `main` by a `branches` list under `on: push` cannot be
  checked by review: to try a change to it, add the feature branch to that list
  and push, then remove the branch from the list again before merging. Keep any
  job in it that publishes behind `if: github.ref_name == 'main'`, so the run
  from the feature branch publishes nothing.
 - Use platform-standard formatters: `black` for Python, `prettier` for
  JS/CSS/Markdown/HTML, `go fmt` for Go. Always use default configuration with
@@ -311,21 +189,14 @@ style conventions are in separate documents:
  module under test to verify it compiles/parses. There is no excuse for
  `make test` to be a no-op.
- `make test` must complete in under 60 seconds. That is the hard cap, and a
+- `make test` must complete in under 20 seconds. Add a 30-second timeout in the
-  suite that exceeds it fails. Under 20 seconds is the target. A suite between
+  Makefile.
  20 and 60 seconds is still green, but the overage must be filed as an
  improvement bug against that repo. Add a 90-second timeout to the test
  invocation (`go test -timeout 90s`). The backstop deliberately sits above the
  hard cap so that it catches a genuinely hung test rather than a merely slow
  one.
- **The test command should use the conditional verbose rerun pattern.** Run
+- **`make test` should use the conditional verbose rerun pattern.** Run tests
-  tests without `-v` (verbose) first. If tests fail, automatically rerun with
+  without `-v` (verbose) first. If tests fail, automatically rerun with `-v` to
-  `-v` to show full output. This keeps CI logs and `docker build` output clean
+  show full output. This keeps CI logs and `docker build` output clean on
-  on success (just package/suite summaries) while providing full diagnostic
+  success (just package/suite summaries) while providing full diagnostic detail
-  detail on failure (every test case, every assertion). The command lives in the
+  on failure (every test case, every assertion). The general shell pattern:
  `test` phase of the `Dockerfile`, since `script/test` builds that phase; the
  Makefile form below is the same pattern for any repo-local invocation:
    ```makefile
    test:
@@ -338,26 +209,11 @@ style conventions are in separate documents:
    ```makefile
    test:
-    	@go test -count=1 -timeout 90s -race -cover ./... || \
+    	@go test -timeout 30s -race -cover ./... || \
    		{ echo "--- Rerunning with -v for details ---"; \
-    		  go test -count=1 -timeout 90s -race -v ./...; exit 1; }
+    		  go test -timeout 30s -race -v ./...; exit 1; }
    ```
    `-count=1` is required on both invocations: it defeats Go's test _result_
    cache, so neither run can report a stored pass in place of running the
    tests. It leaves the build cache alone, so it costs the runtime of the suite
    and no recompilation.
    That cache is Go's own, separate from Docker's layer cache. Go stores a
    passing result in its cache directory (`GOCACHE`), and when the same tests
    run again on unchanged code it prints that result, marked `(cached)`,
    without running them. That matters on a developer's machine, where this
    target runs and the directory lasts from one run to the next. The `test`
    phase of the `Dockerfile` needs no `-count=1`: its base image holds no
    result for this repo's tests and nothing before its `go test` step runs a
    test, so there is nothing to replay. `--no-cache` (above) is what makes that
    step run on an unchanged tree.
    Python example:
    ```makefile
@@ -383,84 +239,10 @@ style conventions are in separate documents:
  must be in `.gitignore`. No exceptions.
 - `.gitignore` should be comprehensive from the start: OS files (`.DS_Store`),
-  editor files (`.swp`, `*~`), in-repo agent scratch directories (`.claude/`),
+  editor files (`.swp`, `*~`), language build artifacts, and `node_modules/`.
-  language build artifacts, and `node_modules/`. Fetch the standard `.gitignore`
+  Fetch the standard `.gitignore` from
-  from `https://git.eeqj.de/sneak/prompts/raw/branch/main/.gitignore` when
+  `https://git.eeqj.de/sneak/prompts/raw/branch/main/.gitignore` when setting up
-  setting up a new repo. These patterns are written to `.gitignore`'s own
+  a new repo.
  semantics, in which an unanchored pattern already matches at every depth; they
  are not a `.dockerignore` and must not be transplanted into one unmodified.
 - **`.dockerignore` does not use `.gitignore` semantics, and copying patterns
  across unmodified leaves secrets in the build context.** Docker matches with
  `moby/patternmatcher`: `filepath.Match` semantics plus a `**` extension, so
  `*` does not cross `/` and a pattern without a leading `**/` is anchored at
  the build-context root. A `.dockerignore` listing `.env`, `*.pem` and `*.key`
  therefore excludes only the copies at the repository root, while `config/.env`
  and `certs/server.key` still reach the context and can land in an image layer
  — which is more dangerous than a short file with no secret patterns at all,
  because it reads as solved and stops anyone looking. Give every
  depth-independent pattern the `**/` prefix and leave only genuinely
  root-anchored entries unprefixed: `.claude`, and the repo's own host-built
  binary, written `/myapp` and never `**/myapp`, which would also match
  `cmd/myapp/` and delete the package directory from the context. Matching is
  case-sensitive, and an ALL-CAPS twin per pattern still misses `Server.Key`, so
  secret names use character ranges — `**/*.[kK][eE][yY]`, `**/*.[pP][eE][mM]`,
  and likewise for `.envrc` and the extensionless SSH keys. Where such a pattern
  also catches something the build needs, re-include it with a negation
  (`!docs/example.env`); deleting the pattern reopens the exposure for every
  other file it covers. Fetch the standard `.dockerignore` from
  `https://git.eeqj.de/sneak/prompts/raw/branch/main/.dockerignore` and extend
  it with the repo's own artifacts.
 - **In-repo agent scratch belongs in both files, written to each file's own
  semantics.** `.claude/` holds one worktree per in-flight agent — an entire
  additional checkout of the repo — so under `COPY . .` the build context
  inflates by a multiple of the repo and another session's unreviewed work can
  be copied into an image layer. In `.gitignore` the entry is `.claude/`,
  unanchored. In `.dockerignore` it is `.claude`, anchored and with **no** `**/`
  prefix, because the prefixed form would also delete any nested directory of
  that name from the build. Anchoring carries a known gap that the canonical
  `.dockerignore` states in its own comment, since consuming repos receive the
  file and not the tracker: the directory is created in the agent's working
  directory, so a repo running agents in subdirectories still ships
  `services/api/.claude/` and must add its own anchored entry there.
 - **A plain `docker build .` of a clone stamps the version that
  `git describe --tags --always` gives**, derived from the `.git` in the build
  context as the canonical `Dockerfile` above shows. Without its failure check,
  a missing `git` or an unreadable checkout would leave `-X main.Version=` empty
  and the build would still exit 0. `script/docker` and `script/cibuild` pass
  the version they compute on the host; it takes precedence. They do this
  byte-identically across repos:
    ```sh
    # Own line: a failing command substitution inside an argument does not
    # trip `set -e`, so the inline form degrades to an empty constant.
    version="$(git describe --tags --always --dirty 2>/dev/null || true)"
    [ -n "$version" ] || version="unknown"
    docker build --no-cache \
        --build-arg VERSION="$version" \
        -t "$(script/projectname)" .
    ```
    `--always` makes an untagged repo yield an abbreviated commit hash rather
    than failing, and the `[ -n "$version" ]` line is the single place the
    fallback is applied — a live check that fires on a build from an export with
    no `.git` and on a repository with no commits yet. Do not fold it into the
    substitution as `|| echo unknown`, which makes the guard unreachable. The
    Dockerfile's side is `ARG VERSION` in the stage that compiles, declared
    there because `ARG` is stage-scoped; passing `VERSION` to a repo whose
    Dockerfile declares no such `ARG` is ignored and costs nothing, which is why
    the scripts stay byte-identical. One consequence for CI: the standard
    checkout action clones shallow and fetches no tags, so a repo that embeds a
    tag-derived version must set `fetch-depth: 0` on its checkout step.
 - **Verify `.dockerignore` by enumerating the image, not by reading the
  patterns.** Plant files at the root _and_ at least two directories deep, build
  a probe image that does `COPY . .`, and list what actually landed
  (`docker run --rm --entrypoint find IMAGE /app`). The `transferring context`
  size is not a substitute: a nested secret is a few bytes, and BuildKit
  transfers only the delta from the previous build.
 - **No build artifacts in version control.** Code-derived data (compiled
  bundles, minified output, generated assets) must never be committed to the
@@ -476,56 +258,9 @@ style conventions are in separate documents:
 - Make all changes on a feature branch. You can do whatever you want on a
  feature branch.
- `.golangci.yml` is standardized. The vendored copy in a consuming repo must
+- `.golangci.yml` is standardized and must _NEVER_ be modified by an agent, only
-  _NEVER_ be modified by an agent: fetch it from
+  manually by the user. Fetch from
-  `https://git.eeqj.de/sneak/prompts/raw/branch/main/.golangci.yml` and keep it
+  `https://git.eeqj.de/sneak/prompts/raw/branch/main/.golangci.yml`.
  byte-identical, so that no repo can quietly loosen its own linting. Linter
  configuration changes are made to the canonical copy in the `prompts` repo and
  reach consuming repos by re-vendoring; an agent may open a PR against
  canonical, which only the user merges. One list is exempt from byte-identity,
  because it cannot be written once for every repo: the `deny` list of the
  `test-support` depguard rule, where a repo names its own test-support packages
  by full import path. A repo adds entries there and changes nothing else, and a
  re-vendor carries its entries forward. The canonical golangci-lint version is
  v2.14.0 (released 2026-09-24), pinned as the digest of the lint phase's base
  image
  (`golangci/golangci-lint@sha256:ad862ba6b3798cbe0fd9fd7408d498fd74fbd2623a92406b2fd3898faf0bf98f`,
  which reports `2.14.0 built with go1.27.0 from 114493f9`). A module's `go`
  directive must not name a newer Go minor version than the one golangci-lint
  was built with, or golangci-lint refuses to lint it: this release lints
  `go 1.27.1` but not `go 1.28`. That digest is the only pin, since no repo
  installs golangci-lint on the host. A repo sets the lint phase digest to the
  one named here and re-vendors `.golangci.yml` in the same commit, whichever of
  the two prompted the change: the canonical copy can name linters that an older
  golangci-lint rejects, and a newer golangci-lint can add linters that
  `default: all` switches on until the canonical copy disables them.
 - **`script/bootstrap` installs a pinned tool by comparing versions, never by
  testing presence.** An `if ! command -v <tool>; then install; fi` guard tests
  `PATH` only, so on an already-provisioned machine the pin is inert and a
  version bump is a silent no-op — while the Dockerfile, installing into a clean
  image, gets the pinned version, so a local `make check` and `make docker` can
  disagree about what the tool even is. The canonical form:
    - compares the installed version against the pin over the **whole** version
      token; a parser that stops at the first `-` reports `2.12.2` for a host
      running `2.12.2-rc1` and skips the install;
    - treats absent, non-zero, empty or unrecognised `--version` output as a
      mismatch, so the failure direction is a redundant install and never a
      skipped one;
    - after installing, re-resolves the binary the way callers do — `hash -r`,
      then through `PATH`, not through the directory the installer wrote to —
      and fails naming the resolved path, since an install that a shadowing
      binary hides succeeds while changing nothing any caller sees;
    - is actually called, and prints the version on both success paths: a
      function defined and never invoked has the same exit status and the same
      empty output as one that worked.
    Keep it POSIX sh: no arrays, no `[[`, no `grep -P`.
    A Go tool a repo needs on the host is installed with `go install` pinned to
    a commit hash (`go install <package>@<commit hash>`). It is never tracked as
    a `go.mod` tool dependency or through a `tools.go` file, either of which
    pulls the tool's own dependencies into the repo's `go.mod` and `go.sum`.
 - When pinning images or packages by hash, add a comment above the reference
  with the version and date (YYYY-MM-DD).
@@ -639,14 +374,12 @@ style conventions are in separate documents:
  settings.
 - Avoid putting files in the repo root unless necessary. Root should contain
-  only project-level config files (`README.md`, `AGENTS.md`, `Makefile`,
+  only project-level config files (`README.md`, `Makefile`, `Dockerfile`,
-  `Dockerfile`, `LICENSE`, `.gitignore`, `.editorconfig`, `REPO_POLICIES.md`,
+  `LICENSE`, `.gitignore`, `.editorconfig`, `REPO_POLICIES.md`, and
-  and language-specific config). Everything else goes in a subdirectory.
+  language-specific config). Everything else goes in a subdirectory. Canonical
-  Canonical subdirectory names:
+  subdirectory names:
    - `bin/` — executable scripts and tools
-    - `cmd/` — Go command entrypoints; thin only: one `main.go` per binary whose
+    - `cmd/` — Go command entrypoints
      body is a single call into `internal/` or `pkg/`, no project logic in
      `cmd/`
    - `configs/` — configuration templates and examples
    - `deploy/` — deployment manifests (k8s, compose, terraform)
    - `docs/` — documentation and markdown (README.md stays in root)
@@ -673,7 +406,3 @@ style conventions are in separate documents:
    - Go: `go.mod`, `go.sum`, `.golangci.yml`
    - JS: `package.json`, `yarn.lock`, `.prettierrc`, `.prettierignore`
    - Python: `pyproject.toml`
 - Guidance for coding agents lives in one `AGENTS.md` at the repository root. It
  is never committed under a file or directory named after one agent tool, such
  as `CLAUDE.md` or `.claude/`, and never split into separate memory files.
@@ -45,69 +45,6 @@ but the review is broader than any of them.
 # Completed Steps
 - 2026-10-06: The canonical files are re-vendored from `sneak/prompts` at
  `dd4027b` ([#472](https://git.eeqj.de/sneak/AutistMask/issues/472)). The
  `Dockerfile` has separate `lint` and `test` phases, and its last stage depends
  on both before it runs `make build`. `script/lint` and `script/test` each
  build one phase, uncached. `script/check-censored` runs in the `lint` phase
  and `script/test-verify-build` in the `test` phase. `script/check` runs the
  two phases and `script/fmt-check`. `script/cibuild` bootstraps, runs
  `script/check`, then builds the image uncached. Given no `VERSION` build
  argument, as in a plain `docker build .`, the image build takes one from
  `git describe` on the `.git` in the build context, which `.dockerignore` now
  sends without its `config`. The vendored `check.yml` has no `timeout-minutes`,
  so the `check` job's cap is gone.
 - 2026-10-06: Reloading or closing the popup mid-refresh no longer logs the
  requests that cancels as failures
  ([#218](https://git.eeqj.de/sneak/AutistMask/issues/218)). Chrome cancels a
  closing page's open requests just after `pagehide`, and in the page a
  cancelled `fetch()` fails with the same "Failed to fetch" as a server that
  cannot be reached, so the home screen's transaction list and the balance
  refresh logged an error for each, and the e2e suite failed on them. The popup
  now aborts an `AbortController` on `pagehide`, and those two check its signal
  before reporting a failure. New e2e tests reload the popup with Blockscout
  held and require nothing logged, and fail the transaction list for real and
  require the failure reported; `tests/balanceRefreshCancelled.test.js` covers
  the balance refresh. The address and token screens and the address scan after
  a new wallet still log a cancelled request
  ([#475](https://git.eeqj.de/sneak/AutistMask/issues/475)).
 - 2026-10-05: `make build` no longer prints the Node `DEP0205`
  `module.register()` deprecation warning
  ([#355](https://git.eeqj.de/sneak/AutistMask/issues/355)). The call came from
  `@tailwindcss/node`, which the Tailwind CLI loads; `tailwindcss` and
  `@tailwindcss/cli` are now pinned at 4.3.1, the first release that uses
  `module.registerHooks()` where Node has it. The compiled CSS computes to the
  same values; it drops the unused `.start` and `.end` rules and writes
  `calc(var(--spacing) * 1)` as `var(--spacing)` and `calc(var(--spacing) * 0)`
  as `0`.
 - 2026-10-05: `make dev` watches
  ([#332](https://git.eeqj.de/sneak/AutistMask/issues/332)). It used to pass
  `--watch` to a `build.js` that read no arguments, so it built once and exited.
  `build.js --watch` now builds, then builds again after every change to a file
  under `src/`, `manifest/` or `icons/`; any other argument fails. It watches
  each directory rather than using Node's recursive watch, which on Linux stops
  seeing a file an editor saves by renaming a new copy over it. It writes no
  build receipt, so nothing can verify what it builds; `make build` remains the
  way to produce a `dist/` to hand on. `tests/buildWatch.test.js` covers the
  watch loop against a temp directory.
 - 2026-10-05: Every CI job has a `timeout-minutes` cap
  ([#294](https://git.eeqj.de/sneak/AutistMask/issues/294)): `check` 10 minutes,
  `e2e-firefox` 15 and `e2e-chrome` 20, each over two and a half times the job's
  slowest cold-cache run. A hung build or browser now ends its job instead of
  holding the shared runner for hours.
 - 2026-10-05: `PROXY_METHODS` in `src/background/index.js` no longer lists
  `eth_chainId` and `net_version`
  ([#326](https://git.eeqj.de/sneak/AutistMask/issues/326)). `handleRpc` answers
  both itself before its proxy branch, so the list named two methods that are
  never sent to the RPC endpoint. No other entry is answered earlier.
  `tests/proxyMethods.test.js` sends every listed method from a page and fails
  on any that does not reach the RPC endpoint.
 - 2026-10-05: The popup's Content Security Policy no longer allows inline style
  ([#328](https://git.eeqj.de/sneak/AutistMask/issues/328)): `style-src` is
  `'self'` in both manifests, pinned in `tests/manifest.test.js`. The 42
@@ -119,20 +56,6 @@ but the review is broader than any of them.
  `display` no longer uncovers it. Script that sets `element.style` is
  unaffected.
 - 2026-10-05: `.prettierignore` no longer lists an AI vendor's tool directory
  ([#363](https://git.eeqj.de/sneak/AutistMask/issues/363)). The directory is
  not tracked, so the line ignored nothing.
 - 2026-10-05: The Chrome end-to-end suite drives both ways the wait for a
  transaction's receipt ends on the error screen
  ([#315](https://git.eeqj.de/sneak/AutistMask/issues/315)): lookups that still
  find no receipt 60 seconds after the broadcast end it with the timeout
  message, and six lookups that fail in a row end it with the message naming the
  unreachable network. Done then returns to the address screen. Both cases wait
  in real time, about a minute each. Playwright's clock would apply to every
  later test in the run and cannot be removed, and moving the stored broadcast
  time back can be undone by the save the popup makes every ten seconds.
 - 2026-10-05: The Chrome end-to-end suite covers the last of the
  [#150](https://git.eeqj.de/sneak/AutistMask/issues/150) and
  [#151](https://git.eeqj.de/sneak/AutistMask/issues/151) items
@@ -15,15 +15,6 @@ const DIST_CHROME = path.join(DIST, "chrome");
 const DIST_FIREFOX = path.join(DIST, "firefox");
 const SRC = path.join(__dirname, "src");
 // What `make dev` watches: the directories whose files build() bundles,
 // compiles or copies. A change anywhere else, package.json and build.js
 // included, starts no build; restart make dev after one.
 const WATCHED_DIRS = [
    SRC,
    path.join(__dirname, "manifest"),
    path.join(__dirname, "icons"),
 ];
 // The module whose compiled DEBUG state script/verify-build asserts. Which
 // bundles contain it is derived from esbuild's own dependency graph rather
 // than from a hardcoded list, so it tracks the bundle layout instead of
@@ -40,7 +31,7 @@ const AUDITED_MODULE = "src/shared/constants.js";
 // the build, whether or not a text matcher would have recognized it. A
 // background entry point the table does not name fails as well, so a second
 // worker is protected by default rather than by someone remembering this file.
-// The Dockerfile's last stage runs `make build`, so it is enforced in CI.
+// Dockerfile:42 runs `make build`, so it is enforced in CI.
 // The build receipt: every file this build emits, with its sha256 and whether
 // it is one of the audited bundles. script/verify-build is handed this and
@@ -450,10 +441,6 @@ function getBuildInfo() {
 async function build() {
    console.log("Building AutistMask extension...");
    // Under make dev this runs once per rebuild in the same process, and each
    // build accounts only for what it emits itself.
    emittedFiles.length = 0;
    const receiptPath = receiptTarget();
    if (!receiptPath) {
        console.warn(
@@ -610,74 +597,10 @@ async function build() {
    console.log("Build complete: dist/chrome/ and dist/firefox/");
 }
 // make dev: build, then build again after every change under `dirs`, until
 // interrupted. A failed build is reported and watching carries on, so a
 // half-finished edit does not end it. A change that arrives while a build is
 // running is not lost: it causes one more build as soon as that one finishes.
 // A directory created after this starts is not watched until a restart.
 //
 // make dev sets no AUTISTMASK_BUILD_RECEIPT, so these builds write no receipt
 // and nothing can verify what they leave in dist/.
 //
 // `rebuild` is build() everywhere but tests/buildWatch.test.js, which also
 // closes the returned watchers.
 function watch(dirs, rebuild) {
    let building = false;
    let changedAgain = false;
    async function run() {
        if (building) {
            changedAgain = true;
            return;
        }
        building = true;
        do {
            // Let the rest of one save's events arrive first, so that one
            // save is one build.
            await new Promise((resolve) => setTimeout(resolve, 100));
            changedAgain = false;
            try {
                await rebuild();
            } catch (err) {
                console.error(
                    `Build failed: ${err && err.message ? err.message : err}`,
                );
            }
        } while (changedAgain);
        building = false;
        console.log("Watching for changes (Ctrl-C to stop)...");
    }
    // One watcher per directory rather than fs.watch's recursive option: on
    // Linux, Node's recursive watch watches each file, and stops seeing one
    // that an editor saves by renaming a new copy over it. A directory's
    // watcher reports every change to the files in it, however they are saved.
    const subdirectories = dirs.flatMap((dir) =>
        fs
            .readdirSync(dir, { recursive: true, withFileTypes: true })
            .filter((entry) => entry.isDirectory())
            .map((entry) => path.join(entry.parentPath, entry.name)),
    );
    const watchers = [...dirs, ...subdirectories].map((dir) =>
        fs.watch(dir, run),
    );
    run();
    return watchers;
 }
 // Run only as a program. Required as a module — which is how
-// tests/buildForbiddenInputs.test.js and tests/buildWatch.test.js reach the
+// tests/buildForbiddenInputs.test.js reaches the checks below — this file
-// functions below — this file builds nothing and writes nothing.
+// builds nothing and writes nothing.
 if (require.main === module) {
    const args = process.argv.slice(2);
    // An argument this file does not know fails rather than being ignored.
    if (args.length > 1 || (args.length === 1 && args[0] !== "--watch")) {
        console.error("usage: node build.js [--watch]");
        process.exit(2);
    }
    if (args[0] === "--watch") {
        watch(WATCHED_DIRS, build);
    } else {
    build().catch((err) => {
        console.error(
            `Build failed: ${err && err.message ? err.message : err}`,
@@ -685,19 +608,16 @@ if (require.main === module) {
        process.exit(1);
    });
 }
 }
-// Exported for tests only: watch() for tests/buildWatch.test.js, the rest for
+// Exported for tests/buildForbiddenInputs.test.js only. The prohibition these
-// tests/buildForbiddenInputs.test.js. The prohibition those enforce is the
+// three functions enforce is the guarantee behind
-// guarantee behind https://git.eeqj.de/sneak/AutistMask/issues/324, and
+// https://git.eeqj.de/sneak/AutistMask/issues/324, and `make check` does not
-// `make check` does not run `make build` — so they are unit tested against
+// run `make build` — so they are unit tested against synthetic metafiles
-// synthetic metafiles rather than being exercised only by CI, where "it ran"
+// rather than being exercised only by CI, where "it ran" is not "it works".
 // is not "it works".
 module.exports = {
    importChain,
    newForbiddenRecord,
    recordBundledInputs,
    assertNoForbiddenInputs,
    assertForbiddenTableCovered,
    watch,
 };
@@ -16,9 +16,9 @@ so the "release commit" throughout is the `main` commit the milestone PR merged.
 ## Procedure
 1. **Confirm `main` is green in CI.** The `check` workflow
-   (`.gitea/workflows/check.yml`) runs `script/cibuild`, which runs
+   (`.gitea/workflows/check.yml`) runs `script/cibuild`, i.e. `docker build .`,
-   `script/check` and then builds the image uncached, so a green `check` run is
+   and the `Dockerfile` runs `make check` as a build step, so a green `check`
-   a green `make check`. Find the run for the exact release commit on the
+   run is a green `make check`. Find the run for the exact release commit on the
   tracker's Actions view. _Check:_ that commit's `check` run succeeded; running
   `make check` on a clean checkout of the commit reproduces it and exits 0.
@@ -15,14 +15,14 @@
    },
    "devDependencies": {
        "@eslint/js": "10.0.1",
-        "@tailwindcss/cli": "4.3.1",
+        "@tailwindcss/cli": "^4.2.1",
        "esbuild": "^0.27.3",
        "eslint": "10.8.1",
        "globals": "17.11.0",
        "jest": "^30.2.0",
        "playwright-core": "1.56.0",
        "prettier": "^3.8.1",
-        "tailwindcss": "4.3.1"
+        "tailwindcss": "^4.2.1"
    },
    "dependencies": {
        "ethereum-blockies-base64": "^1.0.2",
@@ -1,14 +1,14 @@
 #!/bin/sh
-# script/check: run all checks (test, lint, fmt-check). Our own
+# script/check: run all checks (test, test-verify-build, lint, fmt-check).
-# extension to scripts-to-rule-them-all. test and lint are Docker
+# Our own extension to scripts-to-rule-them-all. Must not modify any files.
 # phases; fmt-check is native, because a formatter writes the working
 # tree. Must not modify any files.
 set -eu
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd -P)"
 main() {
    "$SCRIPT_DIR/test"
    "$SCRIPT_DIR/test-verify-build"
    "$SCRIPT_DIR/check-censored"
    "$SCRIPT_DIR/lint"
    "$SCRIPT_DIR/fmt-check"
 }
@@ -1,8 +1,8 @@
 #!/bin/sh
 # script/check-censored: assert that the competitor name RULES.md bars appears
 # nowhere in this repo, and nowhere in the built extension, except where it is
-# deliberate. Our own extension to scripts-to-rule-them-all, run by the
+# deliberate. Our own extension to scripts-to-rule-them-all, run from
-# Dockerfile's lint phase and by make build.
+# script/check and from make build.
 #
 # Where the name is allowed, and why each one is not negotiable away:
 #
@@ -1,28 +1,13 @@
 #!/bin/sh
-# script/cibuild: run the CI build. It bootstraps first: a CI runner
+# script/cibuild: run the CI build. The Dockerfile runs make check, so
-# checks out and runs this and nothing else, and script/fmt-check runs
+# a successful build implies all checks pass.
 # the formatter on the host, which a pristine checkout cannot do.
 # --no-cache for the same reason as script/docker: the gate phases the
 # final stage depends on are RUN steps, and a cached one is a check that
 # did not run.
 set -eu
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd -P)"
+ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
 ROOT="$(cd "$SCRIPT_DIR/.." && pwd -P)"
 main() {
    cd "$ROOT"
-    "$SCRIPT_DIR/bootstrap"
+    docker build .
    "$SCRIPT_DIR/check"
    # Own line: a failing command substitution inside an argument does
    # not trip `set -e`, so the inline form degrades silently to an
    # empty constant. The VERSION build argument takes precedence over
    # the version a build stage derives from the .git in the context.
    version="$(git describe --tags --always --dirty 2>/dev/null || true)"
    [ -n "$version" ] || version="unknown"
    docker build --no-cache \
        --build-arg VERSION="$version" \
        -t "$("$SCRIPT_DIR/projectname")" .
 }
 main "$@"
@@ -1,8 +1,6 @@
 #!/bin/sh
 # script/docker: build the Docker image tagged with the project name.
 # Identical in all repos; the tag comes from script/projectname.
 # --no-cache because the gate phases the final stage depends on are RUN
 # steps, and a cached one is a check that did not run.
 set -eu
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd -P)"
@@ -10,15 +8,7 @@ ROOT="$(cd "$SCRIPT_DIR/.." && pwd -P)"
 main() {
    cd "$ROOT"
-    # Own line: a failing command substitution inside an argument does
+    docker build -t "$("$SCRIPT_DIR/projectname")" .
    # not trip `set -e`, so the inline form degrades silently to an
    # empty constant. The VERSION build argument takes precedence over
    # the version a build stage derives from the .git in the context.
    version="$(git describe --tags --always --dirty 2>/dev/null || true)"
    [ -n "$version" ] || version="unknown"
    docker build --no-cache \
        --build-arg VERSION="$version" \
        -t "$("$SCRIPT_DIR/projectname")" .
 }
 main "$@"
@@ -4,29 +4,10 @@ set -eu
 ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
 # Must match the pin in script/bootstrap.
 NODE_VERSION="22.17.0"
 # script/bootstrap installs node and yarn under nvm and leaves neither
 # on the PATH of the shell that called it, so resolve the pinned
 # toolchain here the way bootstrap's own install step does. nvm is a
 # bash script, hence the subshell.
 run_yarn() {
    if command -v yarn >/dev/null 2>&1; then
        exec yarn "$@"
    fi
    if [ ! -s "$HOME/.nvm/nvm.sh" ]; then
        echo "fmt: no yarn; run script/bootstrap first" >&2
        exit 1
    fi
    exec bash -c '. "$HOME/.nvm/nvm.sh" && nvm use "$1" >/dev/null &&
        shift && exec yarn "$@"' bash "$NODE_VERSION" "$@"
 }
 main() {
    cd "$ROOT"
    echo "Formatting..."
-    run_yarn run fmt
+    yarn run fmt 2>&1
 }
 main "$@"
@@ -5,29 +5,10 @@ set -eu
 ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
 # Must match the pin in script/bootstrap.
 NODE_VERSION="22.17.0"
 # script/bootstrap installs node and yarn under nvm and leaves neither
 # on the PATH of the shell that called it, so resolve the pinned
 # toolchain here the way bootstrap's own install step does. nvm is a
 # bash script, hence the subshell.
 run_yarn() {
    if command -v yarn >/dev/null 2>&1; then
        exec yarn "$@"
    fi
    if [ ! -s "$HOME/.nvm/nvm.sh" ]; then
        echo "fmt-check: no yarn; run script/bootstrap first" >&2
        exit 1
    fi
    exec bash -c '. "$HOME/.nvm/nvm.sh" && nvm use "$1" >/dev/null &&
        shift && exec yarn "$@"' bash "$NODE_VERSION" "$@"
 }
 main() {
    cd "$ROOT"
    echo "Checking formatting..."
-    run_yarn run fmt-check
+    yarn run fmt-check 2>&1
 }
 main "$@"
@@ -14,7 +14,7 @@
 // the build when esbuild's own metafile reports src/shared/state.js as an input
 // of a background bundle. That consults the resolution esbuild actually
 // performed, so no specifier syntax and no resolution rule can slip past it,
-// and the Dockerfile's last stage runs `make build` in CI.
+// and Dockerfile:42 runs `make build` in CI.
 //
 // What this rule is: fast local feedback, in the editor and in `make lint`,
 // before a full bundle. It reads sources from disk and matches import
@@ -1,23 +1,51 @@
 #!/bin/sh
-# script/lint: run the linter. Linting is a phase of the Dockerfile and
+# script/lint: run the linter (eslint, then prettier --check).
 # this builds that phase alone; the linter is never installed or run on
 # a developer host, where a shared result cache and a host-global lock
 # make its answer untrustworthy.
 #
-# The phase is not the last stage in the file, so it is built only when
+# Linting is containerized. ESLint results depend on the ESLint version, and
-# --target names it. --no-cache because a cached lint layer is a lint
+# the pinned one is the one in the image; a host's own install must not be
-# that did not run. The tag makes each build replace the previous image
+# able to decide whether this repo is green. From a host this therefore builds
-# instead of leaving a dangling one behind.
+# the Dockerfile's `lint` stage, which runs this same script inside the image.
 #
 # AUTISTMASK_LINT_NATIVE is set only in that image (see the Dockerfile) and is
 # what stops the recursion, so `make check` inside the CI build lints in place
 # instead of trying to reach a docker daemon it does not have.
 set -eu
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd -P)"
+ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
 ROOT="$(cd "$SCRIPT_DIR/.." && pwd -P)"
 main() {
    cd "$ROOT"
-    docker build --no-cache \
+
-        --target lint \
+    case "${AUTISTMASK_LINT_NATIVE:-}" in
-        -t "$("$SCRIPT_DIR/projectname")-lint" .
+    1)
        echo "Linting..."
        yarn run lint 2>&1
        return 0
        ;;
    "") ;;
    *)
        # Set but not recognized: say so rather than silently taking the
        # docker path, which would look like the variable had no effect.
        echo "lint: AUTISTMASK_LINT_NATIVE is set to" \
            "'${AUTISTMASK_LINT_NATIVE}'; the only recognized value is 1" >&2
        exit 1
        ;;
    esac
    if ! command -v docker >/dev/null 2>&1; then
        echo "lint: docker is required; linting does not run on the host" >&2
        exit 1
    fi
    echo "Linting in the pinned container..."
    # --progress=plain: the default progress renderer collapses the lint
    # output on success, and a lint run whose output cannot be seen is not
    # evidence that it ran.
    #
    # --output=type=cacheonly: the exit status is the whole result; exporting
    # an image afterwards costs about ten times the lint itself.
    docker build --progress=plain --target lint \
        --output=type=cacheonly . 2>&1
 }
 main "$@"
@@ -1,19 +1,52 @@
 #!/bin/sh
-# script/test: run the test suite. Testing is a phase of the Dockerfile
+# script/test: run the test suite.
-# and this builds that phase alone, on the same terms as script/lint:
+#
-# --target because a phase that is not the last stage is built only when
+# jest runs three worker processes (package.json), not one per CPU core: on a
-# named, --no-cache because a cached test layer is a test that did not
+# many-core shared host one per core took gigabytes of RAM per run.
-# run, and a tag so each build replaces the previous image.
+#
 # The timeout bounds a hung suite; it is not a performance budget. On the busy
 # shared build host the suite takes 8-13s with three workers, inside
 # REPO_POLICIES' 20s budget. Inside the image the same suite also pays a cold
 # jest cache and shares the runner with the rest of the build, which is not what
 # that budget describes, so the Dockerfile raises the bound through
 # AUTISTMASK_TEST_TIMEOUT. A cap a healthy suite can trip on a cold cache
 # produces a red that means nothing, and teaches "just run it again".
 set -eu
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd -P)"
+ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
-ROOT="$(cd "$SCRIPT_DIR/.." && pwd -P)"
+TIMEOUT="${AUTISTMASK_TEST_TIMEOUT:-30}"
 main() {
    cd "$ROOT"
-    docker build --no-cache \
+    echo "Running tests (timeout ${TIMEOUT}s)..."
-        --target test \
+
-        -t "$("$SCRIPT_DIR/projectname")-test" .
+    status=0
    timeout "$TIMEOUT" yarn run test 2>&1 || status=$?
    [ "$status" -eq 0 ] && return 0
    # 124 is timeout(1) killing the suite. Say so: a kill is not a failed
    # assertion, and the verbose rerun would only spend the same wall clock
    # to be killed again.
    if [ "$status" -eq 124 ]; then
        echo "tests: TIMED OUT after ${TIMEOUT}s (no assertion failed)" >&2
        echo "tests: raise AUTISTMASK_TEST_TIMEOUT if the suite is healthy" >&2
        exit 1
    fi
    # 125 is timeout(1) itself failing, which here means AUTISTMASK_TEST_TIMEOUT
    # is not a duration it accepts. The suite never ran, so it neither timed out
    # nor failed, and the verbose rerun would only reprint the same complaint.
    if [ "$status" -eq 125 ]; then
        echo "tests: DID NOT RUN: timeout(1) rejected AUTISTMASK_TEST_TIMEOUT=\"${TIMEOUT}\"" >&2
        echo "tests: set it to a duration such as 30 or 180 (see timeout(1))" >&2
        exit 1
    fi
    echo "--- Rerunning with --verbose for details ---"
    timeout "$TIMEOUT" yarn run test:verbose 2>&1 || true
    # Always fail: the first run already proved the tests are broken, so a
    # flaky pass on the rerun must not turn the build green.
    exit 1
 }
 main "$@"
@@ -4,7 +4,7 @@
 # scripts-to-rule-them-all.
 #
 # Deliberately NOT called by script/check or script/test: REPO_POLICIES.md
-# caps make test at 60 seconds and a browser suite does not fit. Run it
+# caps make test at 20 seconds and a browser suite does not fit. Run it
 # yourself before touching popup views. ESLint's no-undef now catches a
 # used-but-not-imported identifier in make check, but only this suite sees
 # what a view actually does when it runs.
@@ -45,10 +45,7 @@ main() {
    trap 'cleanup; exit 130' INT TERM
    echo "Building the Chrome e2e image (extension included)..."
-    # --no-cache: the image build runs make build and its checks, and a
+    docker build --iidfile "$IIDFILE" -t "$IMAGE" -f tests/e2e/Dockerfile .
    # cached layer is a check that did not run.
    docker build --no-cache --iidfile "$IIDFILE" -t "$IMAGE" \
        -f tests/e2e/Dockerfile .
    echo "Running e2e suite in the pinned Playwright container..."
    # The image is run by ID, not by tag: where two clones of this repo run
@@ -4,7 +4,7 @@
 # script/test-e2e. Our own extension to scripts-to-rule-them-all.
 #
 # Deliberately NOT called by script/check or script/test, for the same
-# reason as the Chrome suite: REPO_POLICIES.md caps make test at 60 seconds
+# reason as the Chrome suite: REPO_POLICIES.md caps make test at 20 seconds
 # and a browser suite does not fit. .gitea/workflows/e2e.yml also runs it
 # on every push, in a job separate from check.
 #
@@ -44,9 +44,7 @@ main() {
    trap 'cleanup; exit 130' INT TERM
    echo "Building the pinned Firefox e2e image (extension included)..."
-    # --no-cache: the image build runs make build and its checks, and a
+    docker build --iidfile "$IIDFILE" -t "$IMAGE" \
    # cached layer is a check that did not run.
    docker build --no-cache --iidfile "$IIDFILE" -t "$IMAGE" \
        -f tests/e2e/firefox/Dockerfile .
    echo "Running the Firefox e2e suite..."
@@ -2,8 +2,7 @@
 # script/test-verify-build: exercise every failure mode of
 # script/verify-build, and what make build does with dist/ after one of them
 # (script/discard-dist-on-failure). Our own extension to
-# scripts-to-rule-them-all, run by the Dockerfile's test phase so make check
+# scripts-to-rule-them-all, run from script/check so make check covers it.
 # covers it.
 #
 # Why this exists: verify-build is the build-integrity guard, and four separate
 # reviews of it each found a fresh vacuous pass — the grep exit-2 conflation,
@@ -741,12 +741,11 @@ async function handleConnectionRequest(origin) {
    }
 }
-// Methods that are safe to proxy directly to the RPC node. A method handleRpc
+// Methods that are safe to proxy directly to the RPC node
 // answers before its proxy branch does not belong here: it would never reach
 // the node. tests/proxyMethods.test.js sends every one of these.
 const PROXY_METHODS = [
    "eth_blockNumber",
    "eth_call",
    "eth_chainId",
    "eth_estimateGas",
    "eth_gasPrice",
    "eth_getBalance",
@@ -760,6 +759,7 @@ const PROXY_METHODS = [
    "eth_getTransactionReceipt",
    "eth_maxPriorityFeePerGas",
    "eth_sendRawTransaction",
    "net_version",
    "web3_clientVersion",
    "eth_feeHistory",
    "eth_getBlockTransactionCountByHash",
@@ -1802,5 +1802,3 @@ runtime.onMessage.addListener((msg, sender, sendResponse) => {
        return false;
    }
 });
 module.exports = { PROXY_METHODS };
@@ -48,14 +48,6 @@ function renderWalletList() {
    home.render(ctx);
 }
 // Aborted when the popup page goes away, closed or reloaded. Chrome then
 // cancels the requests the page still has open, and a cancelled fetch() fails
 // with the same "Failed to fetch" as a server that cannot be reached. pagehide
 // fires first, so code that reports a failed request checks this and stays
 // silent about one the page's own closing cancelled.
 const pageClosed = new AbortController();
 window.addEventListener("pagehide", () => pageClosed.abort());
 let refreshInFlight = false;
 // The ten-second refresh init() starts, stopped when the popup moves to the
@@ -74,7 +66,6 @@ async function doRefreshAndRender() {
                state.blockscoutUrl,
                state.trackedTokens,
                state.networkId,
                pageClosed.signal,
            ),
        ]);
        state.lastBalanceRefresh = Date.now();
@@ -96,7 +87,6 @@ async function doRefreshAndRender() {
 const ctx = {
    renderWalletList,
    doRefreshAndRender,
    pageClosed: pageClosed.signal,
    showAddWalletView: () => {
        pushCurrentView();
        addWallet.show();
@@ -225,9 +225,6 @@ async function loadHomeTxs(ctx) {
        homeTxs = merged.slice(0, 25);
        renderHomeTxList(ctx);
    } catch (e) {
        // Cancelled by the popup closing, not failed: see pageClosed in
        // src/popup/index.js.
        if (ctx.pageClosed.aborted) return;
        log.errorf("loadHomeTxs failed:", e.message);
        const list = $("home-tx-list");
        if (list) {
@@ -87,15 +87,7 @@ function rawUnits(value) {
 // way `holders` already is. Absence is never filled in here: this is the
 // upstream of every screen that displays a token amount, so a value invented
 // at this point is indistinguishable from a real one everywhere below it.
-//
+async function fetchTokenBalances(address, blockscoutUrl, trackedTokens) {
 // `signal`, passed by the popup, is aborted when the popup closes; a request
 // that fails after that was cancelled by the closing and is not logged.
 async function fetchTokenBalances(
    address,
    blockscoutUrl,
    trackedTokens,
    signal,
 ) {
    try {
        const resp = await debugFetch(
            blockscoutUrl + "/addresses/" + address + "/token-balances",
@@ -198,22 +190,18 @@ async function fetchTokenBalances(
        }
        return balances;
    } catch (e) {
        if (!signal?.aborted) {
        log.errorf("fetchTokenBalances failed:", e.message);
        }
        return null;
    }
 }
 // Fetch ETH balances, ENS names, and ERC-20 token balances for all addresses.
 // `signal` is as for fetchTokenBalances().
 async function refreshBalances(
    wallets,
    rpcUrl,
    blockscoutUrl,
    trackedTokens,
    networkId,
    signal,
 ) {
    log.debugf("refreshBalances start, rpc:", urlOrigin(rpcUrl));
    const provider = getProvider(rpcUrl, networkId);
@@ -232,7 +220,6 @@ async function refreshBalances(
                        log.debugf("ETH balance", addr.address, addr.balance);
                    })
                    .catch((e) => {
                        if (signal?.aborted) return;
                        log.errorf(
                            "ETH balance failed",
                            addr.address,
@@ -256,7 +243,6 @@ async function refreshBalances(
                        );
                    })
                    .catch((e) => {
                        if (signal?.aborted) return;
                        log.errorf(
                            "ENS reverse failed",
                            addr.address,
@@ -272,7 +258,6 @@ async function refreshBalances(
                    addr.address,
                    blockscoutUrl,
                    trackedTokens,
                    signal,
                ).then((balances) => {
                    if (balances !== null) {
                        addr.tokenBalances = balances;
@@ -5,7 +5,7 @@
 //
 // The browser half of the same claim — that a real Chrome renders that
 // string as text and puts no iframe in the popup DOM — is in
-// tests/e2e/run.js. This half runs inside the 60-second make test cap.
+// tests/e2e/run.js. This half runs inside the 20-second make test cap.
 "use strict";
@@ -1,67 +0,0 @@
 // The balance refresh does not report a request the popup's own closing
 // cancelled, and still reports one that failed while the popup was open
 // (https://git.eeqj.de/sneak/AutistMask/issues/218).
 //
 // In the popup a cancelled fetch() fails with the same "Failed to fetch" as a
 // server that cannot be reached, so every request here fails that way, and
 // only the signal the popup aborts on pagehide tells the two cases apart.
 const { FetchRequest } = require("ethers");
 const { refreshBalances } = require("../src/shared/balances");
 const RPC_URL = "https://rpc.example.invalid";
 const EXPLORER_URL = "https://explorer.example.invalid/api/v2";
 const ADDRESS = "0x1111111111111111111111111111111111111111";
 const realFetch = globalThis.fetch;
 let logged;
 beforeEach(() => {
    logged = [];
    jest.spyOn(console, "error").mockImplementation((...args) => {
        logged.push(args.map(String).join(" "));
    });
    const failedToFetch = async () => {
        throw new TypeError("Failed to fetch");
    };
    // The RPC calls (ETH balance, ENS name) and the explorer request (token
    // balances) all fail the same way.
    FetchRequest.registerGetUrl(failedToFetch);
    globalThis.fetch = jest.fn(failedToFetch);
 });
 afterEach(() => {
    FetchRequest.registerGetUrl(FetchRequest.createGetUrlFunc());
    globalThis.fetch = realFetch;
    jest.restoreAllMocks();
 });
 function refresh(signal) {
    const wallets = [{ addresses: [{ address: ADDRESS }] }];
    return refreshBalances(
        wallets,
        RPC_URL,
        EXPLORER_URL,
        [],
        "mainnet",
        signal,
    );
 }
 test("a failure while the popup is open is reported", async () => {
    await refresh(new AbortController().signal);
    for (const label of [
        "ETH balance failed",
        "ENS reverse failed",
        "fetchTokenBalances failed: Failed to fetch",
    ]) {
        expect(logged.some((line) => line.includes(label))).toBe(true);
    }
 });
 test("a failure once the popup has closed is not", async () => {
    const pageClosed = new AbortController();
    pageClosed.abort();
    await refresh(pageClosed.signal);
    expect(logged).toEqual([]);
 });
@@ -1,104 +0,0 @@
 // `make dev` runs `node build.js --watch`
 // (https://git.eeqj.de/sneak/AutistMask/issues/332). These drive build.js's
 // watch() over a temp directory with a stand-in for build(), so nothing here
 // builds or writes dist/.
 const fs = require("fs");
 const os = require("os");
 const path = require("path");
 const { watch } = require("../build");
 let dir;
 let watchers = [];
 beforeEach(() => {
    dir = fs.mkdtempSync(path.join(os.tmpdir(), "autistmask-watch-"));
    fs.mkdirSync(path.join(dir, "nested"));
    jest.spyOn(console, "log").mockImplementation(() => {});
    jest.spyOn(console, "error").mockImplementation(() => {});
 });
 afterEach(() => {
    for (const watcher of watchers) watcher.close();
    watchers = [];
    fs.rmSync(dir, { recursive: true, force: true });
    jest.restoreAllMocks();
 });
 const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms));
 // Wait until `condition()` holds; fail the test if it has not within 3s.
 async function until(condition) {
    const deadline = Date.now() + 3000;
    while (!condition()) {
        if (Date.now() > deadline) throw new Error("timed out waiting");
        await sleep(10);
    }
 }
 // Save the way many editors do: write a new copy, then rename it over the
 // original, so the file at that path is a different one afterwards.
 function saveByRename(file, contents) {
    fs.writeFileSync(`${file}.tmp`, contents);
    fs.renameSync(`${file}.tmp`, file);
 }
 test("builds at start, then once per change to a file in a subdirectory", async () => {
    const file = path.join(dir, "nested", "a.js");
    fs.writeFileSync(file, "1");
    let builds = 0;
    watchers = watch([dir], async () => {
        builds++;
    });
    await until(() => builds === 1);
    fs.writeFileSync(file, "2");
    await until(() => builds === 2);
    await sleep(300);
    expect(builds).toBe(2);
 });
 test("keeps seeing a file that is saved by renaming a new copy over it", async () => {
    const file = path.join(dir, "nested", "a.js");
    fs.writeFileSync(file, "1");
    let builds = 0;
    watchers = watch([dir], async () => {
        builds++;
    });
    await until(() => builds === 1);
    saveByRename(file, "2");
    await until(() => builds === 2);
    saveByRename(file, "3");
    await until(() => builds === 3);
 });
 test("a failed build is reported and watching carries on", async () => {
    let builds = 0;
    watchers = watch([dir], async () => {
        builds++;
        if (builds === 1) throw new Error("unexpected token");
    });
    await until(() => console.error.mock.calls.length === 1);
    expect(console.error).toHaveBeenCalledWith(
        "Build failed: unexpected token",
    );
    fs.writeFileSync(path.join(dir, "a.js"), "1");
    await until(() => builds === 2);
 });
 test("a change made while a build runs causes one more build after it", async () => {
    let builds = 0;
    watchers = watch([dir], async () => {
        builds++;
        if (builds === 1) {
            fs.writeFileSync(path.join(dir, "a.js"), "1");
            await sleep(200);
        }
    });
    await until(() => builds === 2);
    await sleep(300);
    expect(builds).toBe(2);
 });
@@ -105,7 +105,7 @@ describe("the flash line the message is shown in", () => {
    // "a rejected dust threshold shifts no layout (#233)" and "an over-long
    // flash message keeps to one line (#252)" in tests/e2e/run.js, run by
    // make test-e2e. They are not in make check because REPO_POLICIES.md
-    // caps make test at 60 seconds and a browser suite does not fit.
+    // caps make test at 20 seconds and a browser suite does not fit.
    test("reserves its height in the markup", () => {
        const flashLine = POPUP_HTML.match(
            /<div\s+id="flash-msg"\s+class="([^"]*)"/,
@@ -8,7 +8,7 @@
 //   node tests/e2e/firefox/run.js [dist/firefox]
 //
 // Deliberately not part of script/check, and deliberately not named
-// *.test.js: REPO_POLICIES.md caps make test at 60 seconds and a browser
+// *.test.js: REPO_POLICIES.md caps make test at 20 seconds and a browser
 // suite does not fit.
 //
 // This shares no driver layer with the Chrome suite in tests/e2e/, and the
@@ -4,7 +4,7 @@
 //
 // This runs inside the pinned Playwright container; see script/test-e2e.
 // It is deliberately NOT part of make check — REPO_POLICIES.md caps
-// make test at 60 seconds and a browser suite does not fit.
+// make test at 20 seconds and a browser suite does not fit.
 "use strict";
@@ -418,23 +418,27 @@ function sleep(ms) {
 const HOLD_POLL_MS = 25;
 const HOLD_MAX_MS = 30000;
-// Hold a reply open for as long as the test asks: until opts[name] is false.
+// Hold a gas estimate open for as long as the test asks.
 //
-// The switch (holdGasEstimate or holdBlockscout) is read here rather than
+// opts.holdGasEstimate is read here rather than captured, so a test flips it
-// captured, so a test flips it on the same options object the route was
+// on the same options object the route was registered with — the same
-// registered with — the same pattern as seedTokenTransfer. This is the only way
+// pattern as seedTokenTransfer. This is the only way to observe the
-// to observe a screen while its request is genuinely in flight; sampling the
+// confirmation screen while its estimate is genuinely in flight; sampling
-// screen and hoping to win a race against the network would assert nothing on
+// the screen and hoping to win a race against the network would assert
-// a slow machine.
+// nothing on a slow machine.
 //
 // It never gives up quietly. A hold that outlives the bound is reported like
 // any other harness fault, because a "pending" state that stopped being
 // pending on its own is a green assertion about the wrong screen.
-async function awaitRelease(opts, name, report) {
+async function awaitRelease(opts, report) {
    const started = Date.now();
-    while (opts[name]) {
+    while (opts.holdGasEstimate) {
        if (Date.now() - started > HOLD_MAX_MS) {
-            report(name + " was never released after " + HOLD_MAX_MS + "ms");
+            report(
                "held gas estimate was never released after " +
                    HOLD_MAX_MS +
                    "ms",
            );
            return;
        }
        await sleep(HOLD_POLL_MS);
@@ -456,16 +460,6 @@ function rpcReply(req, opts, report) {
        return Object.assign(envelope, { result: ethCallResult(req, opts) });
    }
    if (req.method === "eth_getTransactionReceipt") {
        // A lookup that fails, which the wait screen counts differently from
        // one that answers "not mined yet" (README.md, WaitTx).
        if (opts.failReceiptLookup) {
            return Object.assign(envelope, {
                error: {
                    code: -32000,
                    message: "e2e fixture: receipt lookup failed",
                },
            });
        }
        const hash = Array.isArray(req.params) ? req.params[0] : null;
        return Object.assign(envelope, {
            result: opts.seedReceipt && hash ? transactionReceipt(hash) : null,
@@ -558,7 +552,7 @@ async function handleRpc(route, postData, opts, report) {
        return route.abort();
    }
    if (batch.some((req) => req.method === "eth_estimateGas")) {
-        await awaitRelease(opts, "holdGasEstimate", report);
+        await awaitRelease(opts, report);
    }
    const replies = batch.map((req) => rpcReply(req, opts, report));
@@ -614,10 +608,6 @@ function traceEnabled(raw) {
 *   node-side refusal.
 * @param {boolean} [opts.holdGasEstimate]  hold every batch containing an
 *   eth_estimateGas until this is cleared again.
 * @param {boolean} [opts.holdBlockscout]  hold every Blockscout request until
 *   this is cleared again.
 * @param {boolean} [opts.failTransactionList]  fail every request for an
 *   address's transaction list as a network error; read at request time.
 * @param {string[]} [opts.broadcastTransactions]  every raw signed
 *   transaction handed to eth_sendRawTransaction, appended in order.
 * @param {number|string|null} [opts.tokenDecimalsOverride]  the scale
@@ -629,8 +619,6 @@ function traceEnabled(raw) {
 *   symbol is markup; read at request time.
 * @param {boolean} [opts.seedReceipt]  answer eth_getTransactionReceipt with a
 *   confirmed receipt instead of null, so a wait screen resolves.
 * @param {boolean} [opts.failReceiptLookup]  answer eth_getTransactionReceipt
 *   with an error, so every receipt lookup fails; read at request time.
 * @returns {Promise<{waitForServiceWorkerTraffic: (ms: number) =>
 *   Promise<string|null>}>}
 */
@@ -693,12 +681,7 @@ async function installNetworkStubs(ctx, opts) {
        // Blockscout v2
        if (p.includes("/api/v2/")) {
            await awaitRelease(opts, "holdBlockscout", report);
            if (/\/addresses\/0x[0-9a-fA-F]{40}\/transactions$/.test(p)) {
                // Aborted rather than answered with an error status: to the
                // page this is a server that cannot be reached, and fetch()
                // rejects with "Failed to fetch".
                if (opts.failTransactionList) return route.abort();
                const addr = blockscoutAddress(p);
                return jsonResponse(route, {
                    items:
@@ -4,7 +4,7 @@
 //
 // A plain runner rather than jest on purpose: jest's default testMatch
 // would pull these files into script/test, and browser tests do not fit
-// inside the 60-second cap REPO_POLICIES.md puts on make test. Nothing
+// inside the 20-second cap REPO_POLICIES.md puts on make test. Nothing
 // here is named *.test.js for the same reason.
 "use strict";
@@ -696,62 +696,6 @@ test("the token contract row links to the explorer's token page (#151)", async (
    );
 });
 // ------------------------------------------- reload mid-refresh (#218)
 //
 // Reloading or closing the popup makes Chrome cancel the requests it still has
 // open, and in the page a cancelled fetch() fails with the same "Failed to
 // fetch" as a server that cannot be reached. Here rather than straight after
 // wallet creation because a reload also cancels the address scan that follows
 // it, which still logs (#475).
 // Blockscout is held, so the home screen's transaction list and token balances
 // cannot have been answered when the popup reloads. The assertion is the
 // harness's own: a console.error from the page being reloaded fails this test.
 test("reloading the popup mid-refresh reports no failure (#218)", async (env) => {
    await goHome(env.page);
    env.routeOpts.holdBlockscout = true;
    try {
        const inFlight = Promise.all([
            env.page.waitForRequest((r) => r.url().endsWith("/transactions")),
            env.page.waitForRequest((r) => r.url().endsWith("/token-balances")),
        ]);
        await env.page.reload();
        await inFlight;
        await env.page.reload();
    } finally {
        env.routeOpts.holdBlockscout = false;
    }
    await visible(env.page, "#view-main");
 });
 // The same "Failed to fetch" from a server that really cannot be reached is
 // still reported, so it still fails the run unless a test declares it. Chrome
 // reports the failed request itself as well, which a cancelled one does not.
 test("a transaction list that cannot be fetched is still reported (#218)", async (env) => {
    env.errors.expect(
        "loadHomeTxs failed",
        /loadHomeTxs failed: Failed to fetch/,
    );
    env.errors.expect(
        "Chrome's report of the failed request",
        /Failed to load resource: net::ERR_FAILED/,
    );
    env.routeOpts.failTransactionList = true;
    try {
        // Drawn again by the next ten-second refresh.
        await env.page.waitForFunction(
            () =>
                document
                    .getElementById("home-tx-list")
                    .textContent.includes("Failed to load transactions."),
            null,
            { timeout: 15000 },
        );
    } finally {
        env.routeOpts.failTransactionList = false;
    }
 });
 // -------------------------------------------- recovery phrase (#161)
 // The gear toggles, so pressing it while Settings is already up leaves it.
@@ -2163,9 +2107,10 @@ function quantity(wei) {
 // Wait on the main view until a changed balance fixture has been picked up.
 //
-// Not a reload: the popup re-refreshes on a 10-second timer by itself, and a
+// Deliberately not a reload: the popup re-refreshes on a 10-second timer by
-// reload on the address screen still logs the transaction list it cancels
+// itself, and reloading aborts whatever fetch the home screen has open at
-// (#475).
+// that instant, which the extension reports through log.errorf and the
 // harness — correctly — fails the run on.
 //
 // It also deliberately settles on MAIN rather than on the address screen.
 // The address screen builds the send screen's token dropdown once, from the
@@ -2854,84 +2799,6 @@ test("a token that lies about decimals() at signing time broadcasts nothing (#30
    }
 });
 // ------------------------------ the wait for a receipt ending in error (#315)
 //
 // README.md (WaitTx) documents two ways the wait ends on the error screen: a
 // lookup that answers "no receipt" 60 seconds or more after the broadcast, and
 // six lookups in a row that fail. They are different facts with different
 // messages, so each is driven to its own.
 //
 // Both wait in real time, about a minute each. The wait reads the popup's own
 // clock and its own ten-second timer. Playwright's clock would move both, but
 // it is installed on the whole browser context and cannot be removed, so every
 // later test would run on it. Moving the stored broadcast time back instead can
 // be undone by the save the popup makes every ten seconds.
 // Send ETH from the address screen and stop on the wait for its receipt.
 async function sendEthToWait(env) {
    await goToConfirm(env.page, {
        token: "ETH",
        balance: FUNDED_ETH_TEXT + " ETH",
        amount: COMFORTABLE_AMOUNT,
    });
    await waitForEstimate(env.page);
    await fillPasswordAndSend(env.page);
    await visible(env.page, "#view-wait-tx", 60000);
 }
 test("a wait still without a receipt after 60 seconds ends on the timeout message (#315)", async (env) => {
    try {
        await sendEthToWait(env);
        // Lookups run every ten seconds and answer "no receipt", so the one
        // that ends the wait comes about 60 seconds after the broadcast.
        await visible(env.page, "#view-error-tx", 90000);
        const message = (
            await env.page.locator("#error-tx-message").innerText()
        ).trim();
        assert(
            message ===
                "Transaction was not confirmed within 60 seconds. It may still confirm later — check Etherscan.",
            "the wait did not end on the timeout message: " +
                JSON.stringify(message),
        );
        await env.page.click("#btn-error-tx-done");
        await visible(env.page, "#view-address");
    } finally {
        await backToAddressAfterSend(env);
    }
 });
 test("six failed receipt lookups in a row end on the unreachable-network message (#315)", async (env) => {
    // Each failed lookup is logged through log.errorf, i.e. console.error.
    // Exactly six are declared: a wait that ended sooner leaves one unmatched,
    // and one that went on logs a seventh, and either fails this test.
    for (let i = 1; i <= 6; i++) {
        env.errors.expect(
            "failed receipt lookup " + i + " of 6",
            /poll receipt failed/,
        );
    }
    env.routeOpts.failReceiptLookup = true;
    try {
        await sendEthToWait(env);
        await visible(env.page, "#view-error-tx", 90000);
        const message = (
            await env.page.locator("#error-tx-message").innerText()
        ).trim();
        assert(
            message ===
                "The network could not be reached to check this transaction — 6 lookups failed in a row. Check the RPC URL in Settings. The transaction may still have confirmed — check Etherscan.",
            "the wait did not end on the unreachable-network message: " +
                JSON.stringify(message),
        );
        await env.page.click("#btn-error-tx-done");
        await visible(env.page, "#view-address");
    } finally {
        env.routeOpts.failReceiptLookup = false;
        await backToAddressAfterSend(env);
    }
 });
 // ------------------------------------------- hostile token symbol (#307)
 //
 // The reproduction from the issue, in the real browser against the real
@@ -4525,10 +4392,6 @@ async function main() {
        ethBalanceWei: null,
        failGasEstimate: false,
        holdGasEstimate: false,
        // Whether Blockscout requests are held unanswered, and whether an
        // address's transaction list fails as a network error (#218).
        holdBlockscout: false,
        failTransactionList: false,
        // What decimals() answers for the stub token, when it is to answer
        // something other than the value the same fixture reports through
        // Blockscout. The token that lies about its scale (#305).
@@ -4539,8 +4402,6 @@ async function main() {
        // Whether eth_getTransactionReceipt confirms a transaction rather than
        // answering "not mined yet".
        seedReceipt: false,
        // Whether eth_getTransactionReceipt fails instead of answering (#315).
        failReceiptLookup: false,
        // Every raw signed transaction handed to eth_sendRawTransaction, in
        // order. The dApp transaction round trip asserts against these bytes
        // rather than against anything the extension reported about them.
@@ -45,9 +45,9 @@ describe("vendored blocklist", () => {
        // than loudly, so the ordering the search depends on is asserted here
        // against the committed file rather than assumed of the generator.
        // One assertion at the end rather than one per entry: 100k+ expect()
-        // calls cost seconds, and make test is capped at 60 seconds for the
+        // calls cost seconds, and make test is capped at 30 for the whole
-        // whole suite. The index of the first offender is reported, so a
+        // suite. The index of the first offender is reported, so a failure
-        // failure still says where.
+        // still says where.
        let previous = "";
        let outOfOrderAt = -1;
        for (let i = 0; i < vendored.count; i++) {
@@ -1,89 +0,0 @@
 // Every method in PROXY_METHODS is sent to the RPC node.
 //
 // handleRpc answers some methods itself before it reaches its proxy branch. A
 // method listed in PROXY_METHODS but answered earlier never reaches the node,
 // so the list would name a method that is not proxied
 // (https://git.eeqj.de/sneak/AutistMask/issues/326). Each method is sent from
 // a page here and must come back with what the node answered.
 const { makeStorageStub } = require("./support/storageStub");
 async function settle() {
    for (let i = 0; i < 50; i++) await Promise.resolve();
 }
 afterEach(() => {
    delete global.chrome;
    delete global.fetch;
 });
 test("every method in PROXY_METHODS reaches the RPC node", async () => {
    jest.resetModules();
    jest.doMock("../src/shared/balances", () => ({
        getProvider: () => ({}),
        refreshBalances: jest.fn(async () => {}),
    }));
    jest.doMock("../src/shared/phishingDomains", () => ({
        isPhishingDomain: () => false,
    }));
    jest.doMock("../src/shared/alarms", () => ({
        BALANCE_REFRESH_ALARM: "balance",
        BALANCE_REFRESH_PERIOD_MINUTES: 1,
        ensureRecurringAlarms: jest.fn(async () => {}),
        registerAlarmHandlers: jest.fn(),
    }));
    // The node answers each method with a value naming that method.
    global.fetch = jest.fn(async (url, opts) => ({
        status: 200,
        json: async () => ({
            jsonrpc: "2.0",
            id: 1,
            result: "node answered " + JSON.parse(opts.body).method,
        }),
    }));
    let messageListener = null;
    global.chrome = {
        storage: makeStorageStub({
            autistmask: {
                networkId: "mainnet",
                wallets: [],
                allowedSites: {},
                deniedSites: {},
            },
        }),
        runtime: {
            getURL: (path) => "chrome-extension://autistmask/" + path,
            onMessage: {
                addListener: (fn) => {
                    messageListener = fn;
                },
            },
            onConnect: { addListener: () => {} },
            lastError: null,
        },
        windows: { onRemoved: { addListener: () => {} } },
        action: { setPopup: () => {} },
    };
    const { PROXY_METHODS } = require("../src/background/index");
    const answers = {};
    const expected = {};
    for (const method of PROXY_METHODS) {
        messageListener(
            { type: "AUTISTMASK_RPC", method, params: [] },
            { origin: "https://dapp.example" },
            (r) => {
                answers[method] = r;
            },
        );
        await settle();
        expected[method] = { result: "node answered " + method };
    }
    expect(PROXY_METHODS.length).toBeGreaterThan(0);
    expect(answers).toEqual(expected);
 });
@@ -12,8 +12,8 @@
 // interactive parameters, which the module hardcodes. The parameters are not
 // weakened or overridden anywhere in this file — they are pinned by the "key
 // derivation cost" tests, since they are the vault's only defence against an
-// offline attack on a stolen blob. The suite is kept inside the 60-second
+// offline attack on a stolen blob. The suite is kept inside script/test's
-// make test cap by sharing one encrypted fixture across the tamper cases
+// 30-second budget by sharing one encrypted fixture across the tamper cases
 // instead of re-encrypting per test.
 const sodium = require("libsodium-wrappers-sumo");
@@ -275,15 +275,7 @@
  resolved "https://registry.npmjs.org/@bcoe/v8-coverage/-/v8-coverage-0.2.3.tgz"
  integrity sha512-0hYQ8SB4Db5zvZB4axdMHGwEaQjkZzFjQiN9LVYvIFB2nSUHW9tYpxWriPrWDASIxiaXax83REcLxuSdnGPZtw==
-"@emnapi/core@^1.10.0":
+"@emnapi/core@^1.4.3", "@emnapi/core@^1.7.1", "@emnapi/core@^1.8.1":
  version "1.11.3"
  resolved "https://registry.yarnpkg.com/@emnapi/core/-/core-1.11.3.tgz#5e95348a42cd1e06f0b9aa380cd74091daa4d520"
  integrity sha512-zLpS5asjEb7lq8jYLq37N6XKaE41DIexlY1rF/z4/tIl3wo13Sqm28fRyfIsKZD+NZ8mM5RoKkpW/rBcuoSZSg==
  dependencies:
    "@emnapi/wasi-threads" "1.2.3"
    tslib "^2.4.0"
 "@emnapi/core@^1.4.3":
  version "1.8.1"
  resolved "https://registry.yarnpkg.com/@emnapi/core/-/core-1.8.1.tgz#fd9efe721a616288345ffee17a1f26ac5dd01349"
  integrity sha512-AvT9QFpxK0Zd8J0jopedNm+w/2fIzvtPKPjqyw9jwvBaReTTqPBk9Hixaz7KbjimP+QNz605/XnjFcDAL2pqBg==
@@ -291,34 +283,20 @@
    "@emnapi/wasi-threads" "1.1.0"
    tslib "^2.4.0"
-"@emnapi/runtime@^1.10.0":
+"@emnapi/runtime@^1.4.3", "@emnapi/runtime@^1.7.1", "@emnapi/runtime@^1.8.1":
  version "1.11.3"
  resolved "https://registry.yarnpkg.com/@emnapi/runtime/-/runtime-1.11.3.tgz#84257ae3b0531eb2aec1ffa23d70700da007ba95"
  integrity sha512-Xz4Tpyki7XyrpbUK1jR1AhdAdaXyhhY4lZ3neLodmhpuWfy2PAQN5B46sAiU4liOXGLkHypn/qU+jvfWSCYYLA==
  dependencies:
    tslib "^2.4.0"
 "@emnapi/runtime@^1.4.3":
  version "1.8.1"
  resolved "https://registry.yarnpkg.com/@emnapi/runtime/-/runtime-1.8.1.tgz#550fa7e3c0d49c5fb175a116e8cd70614f9a22a5"
  integrity sha512-mehfKSMWjjNol8659Z8KxEMrdSJDDot5SXMq00dM8BN4o+CLNXQ0xH2V7EchNHV4RmbZLmmPdEaXZc5H2FXmDg==
  dependencies:
    tslib "^2.4.0"
-"@emnapi/wasi-threads@1.1.0":
+"@emnapi/wasi-threads@1.1.0", "@emnapi/wasi-threads@^1.1.0":
  version "1.1.0"
  resolved "https://registry.npmjs.org/@emnapi/wasi-threads/-/wasi-threads-1.1.0.tgz"
  integrity sha512-WI0DdZ8xFSbgMjR1sFsKABJ/C5OnRrjT06JXbZKexJGrDuPTzZdDYfFlsgcCXCyf+suG5QU2e/y1Wo2V/OapLQ==
  dependencies:
    tslib "^2.4.0"
 "@emnapi/wasi-threads@1.2.3", "@emnapi/wasi-threads@^1.2.1":
  version "1.2.3"
  resolved "https://registry.yarnpkg.com/@emnapi/wasi-threads/-/wasi-threads-1.2.3.tgz#c9bf72fd4be5b928aee894820e8d814ed73916e9"
  integrity sha512-ELEBe8PsLvvJ6QMr0zLt8ffvOHW/dc1m3CEzNMg7aJUv3bMaoDtw2TXyDAwkYBuroxxuHEwhRTLJSe5sya547g==
  dependencies:
    tslib "^2.4.0"
 "@esbuild/aix-ppc64@0.27.3":
  version "0.27.3"
  resolved "https://registry.yarnpkg.com/@esbuild/aix-ppc64/-/aix-ppc64-0.27.3.tgz#815b39267f9bffd3407ea6c376ac32946e24f8d2"
@@ -824,12 +802,14 @@
    "@emnapi/runtime" "^1.4.3"
    "@tybys/wasm-util" "^0.10.0"
-"@napi-rs/wasm-runtime@^1.1.4":
+"@napi-rs/wasm-runtime@^1.1.1":
-  version "1.2.5"
+  version "1.1.1"
-  resolved "https://registry.yarnpkg.com/@napi-rs/wasm-runtime/-/wasm-runtime-1.2.5.tgz#8c728c07e2543d80e55ccb34158c4ae9d6bd13e8"
+  resolved "https://registry.yarnpkg.com/@napi-rs/wasm-runtime/-/wasm-runtime-1.1.1.tgz#c3705ab549d176b8dc5172723d6156c3dc426af2"
-  integrity sha512-HshSvXzmBxNzqejd3k/KemgQ3hdREUYFRRrgxOZ+gPljDIsO2SDZrVZMd4Z/HsxudQbE62OVyVFE8z9BCurfjA==
+  integrity sha512-p64ah1M1ld8xjWv3qbvFwHiFVWrq1yFvV4f7w+mzaqiR4IlSgkqhcRdHwsGgomwzBH51sRY4NEowLxnaBjcW/A==
  dependencies:
-    "@tybys/wasm-util" "^0.10.3"
+    "@emnapi/core" "^1.7.1"
    "@emnapi/runtime" "^1.7.1"
    "@tybys/wasm-util" "^0.10.1"
 "@noble/curves@1.2.0":
  version "1.2.0"
@@ -843,94 +823,94 @@
  resolved "https://registry.npmjs.org/@noble/hashes/-/hashes-1.3.2.tgz"
  integrity sha512-MVC8EAQp7MvEcm30KWENFjgR+Mkmf+D189XJTkFIlwohU5hcBbn1ZkKq7KVTi2Hme3PMGF390DaL52beVrIihQ==
-"@parcel/watcher-android-arm64@2.5.1":
+"@parcel/watcher-android-arm64@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-android-arm64/-/watcher-android-arm64-2.5.1.tgz#507f836d7e2042f798c7d07ad19c3546f9848ac1"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-android-arm64/-/watcher-android-arm64-2.5.6.tgz#5f32e0dba356f4ac9a11068d2a5c134ca3ba6564"
-  integrity sha512-KF8+j9nNbUN8vzOFDpRMsaKBHZ/mcjEjMToVMJOhTozkDonQFFrRcfdLWn6yWKCmJKmdVxSgHiYvTCef4/qcBA==
+  integrity sha512-YQxSS34tPF/6ZG7r/Ih9xy+kP/WwediEUsqmtf0cuCV5TPPKw/PQHRhueUo6JdeFJaqV3pyjm0GdYjZotbRt/A==
-"@parcel/watcher-darwin-arm64@2.5.1":
+"@parcel/watcher-darwin-arm64@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-darwin-arm64/-/watcher-darwin-arm64-2.5.1.tgz#3d26dce38de6590ef79c47ec2c55793c06ad4f67"
+  resolved "https://registry.npmjs.org/@parcel/watcher-darwin-arm64/-/watcher-darwin-arm64-2.5.6.tgz"
-  integrity sha512-eAzPv5osDmZyBhou8PoF4i6RQXAfeKL9tjb3QzYuccXFMQU0ruIc/POh30ePnaOyD1UXdlKguHBmsTs53tVoPw==
+  integrity sha512-Z2ZdrnwyXvvvdtRHLmM4knydIdU9adO3D4n/0cVipF3rRiwP+3/sfzpAwA/qKFL6i1ModaabkU7IbpeMBgiVEA==
-"@parcel/watcher-darwin-x64@2.5.1":
+"@parcel/watcher-darwin-x64@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-darwin-x64/-/watcher-darwin-x64-2.5.1.tgz#99f3af3869069ccf774e4ddfccf7e64fd2311ef8"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-darwin-x64/-/watcher-darwin-x64-2.5.6.tgz#bf05d76a78bc15974f15ec3671848698b0838063"
-  integrity sha512-1ZXDthrnNmwv10A0/3AJNZ9JGlzrF82i3gNQcWOzd7nJ8aj+ILyW1MTxVk35Db0u91oD5Nlk9MBiujMlwmeXZg==
+  integrity sha512-HgvOf3W9dhithcwOWX9uDZyn1lW9R+7tPZ4sug+NGrGIo4Rk1hAXLEbcH1TQSqxts0NYXXlOWqVpvS1SFS4fRg==
-"@parcel/watcher-freebsd-x64@2.5.1":
+"@parcel/watcher-freebsd-x64@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-freebsd-x64/-/watcher-freebsd-x64-2.5.1.tgz#14d6857741a9f51dfe51d5b08b7c8afdbc73ad9b"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-freebsd-x64/-/watcher-freebsd-x64-2.5.6.tgz#8bc26e9848e7303ac82922a5ae1b1ef1bdb48a53"
-  integrity sha512-SI4eljM7Flp9yPuKi8W0ird8TI/JK6CSxju3NojVI6BjHsTyK7zxA9urjVjEKJ5MBYC+bLmMcbAWlZ+rFkLpJQ==
+  integrity sha512-vJVi8yd/qzJxEKHkeemh7w3YAn6RJCtYlE4HPMoVnCpIXEzSrxErBW5SJBgKLbXU3WdIpkjBTeUNtyBVn8TRng==
-"@parcel/watcher-linux-arm-glibc@2.5.1":
+"@parcel/watcher-linux-arm-glibc@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-arm-glibc/-/watcher-linux-arm-glibc-2.5.1.tgz#43c3246d6892381db473bb4f663229ad20b609a1"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-arm-glibc/-/watcher-linux-arm-glibc-2.5.6.tgz#1328fee1deb0c2d7865079ef53a2ba4cc2f8b40a"
-  integrity sha512-RCdZlEyTs8geyBkkcnPWvtXLY44BCeZKmGYRtSgtwwnHR4dxfHRG3gR99XdMEdQ7KeiDdasJwwvNSF5jKtDwdA==
+  integrity sha512-9JiYfB6h6BgV50CCfasfLf/uvOcJskMSwcdH1PHH9rvS1IrNy8zad6IUVPVUfmXr+u+Km9IxcfMLzgdOudz9EQ==
-"@parcel/watcher-linux-arm-musl@2.5.1":
+"@parcel/watcher-linux-arm-musl@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-arm-musl/-/watcher-linux-arm-musl-2.5.1.tgz#663750f7090bb6278d2210de643eb8a3f780d08e"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-arm-musl/-/watcher-linux-arm-musl-2.5.6.tgz#bad0f45cb3e2157746db8b9d22db6a125711f152"
-  integrity sha512-6E+m/Mm1t1yhB8X412stiKFG3XykmgdIOqhjWj+VL8oHkKABfu/gjFj8DvLrYVHSBNC+/u5PeNrujiSQ1zwd1Q==
+  integrity sha512-Ve3gUCG57nuUUSyjBq/MAM0CzArtuIOxsBdQ+ftz6ho8n7s1i9E1Nmk/xmP323r2YL0SONs1EuwqBp2u1k5fxg==
-"@parcel/watcher-linux-arm64-glibc@2.5.1":
+"@parcel/watcher-linux-arm64-glibc@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-arm64-glibc/-/watcher-linux-arm64-glibc-2.5.1.tgz#ba60e1f56977f7e47cd7e31ad65d15fdcbd07e30"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-arm64-glibc/-/watcher-linux-arm64-glibc-2.5.6.tgz#b75913fbd501d9523c5f35d420957bf7d0204809"
-  integrity sha512-LrGp+f02yU3BN9A+DGuY3v3bmnFUggAITBGriZHUREfNEzZh/GO06FF5u2kx8x+GBEUYfyTGamol4j3m9ANe8w==
+  integrity sha512-f2g/DT3NhGPdBmMWYoxixqYr3v/UXcmLOYy16Bx0TM20Tchduwr4EaCbmxh1321TABqPGDpS8D/ggOTaljijOA==
-"@parcel/watcher-linux-arm64-musl@2.5.1":
+"@parcel/watcher-linux-arm64-musl@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-arm64-musl/-/watcher-linux-arm64-musl-2.5.1.tgz#f7fbcdff2f04c526f96eac01f97419a6a99855d2"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-arm64-musl/-/watcher-linux-arm64-musl-2.5.6.tgz#da5621a6a576070c8c0de60dea8b46dc9c3827d4"
-  integrity sha512-cFOjABi92pMYRXS7AcQv9/M1YuKRw8SZniCDw0ssQb/noPkRzA+HBDkwmyOJYp5wXcsTrhxO0zq1U11cK9jsFg==
+  integrity sha512-qb6naMDGlbCwdhLj6hgoVKJl2odL34z2sqkC7Z6kzir8b5W65WYDpLB6R06KabvZdgoHI/zxke4b3zR0wAbDTA==
-"@parcel/watcher-linux-x64-glibc@2.5.1":
+"@parcel/watcher-linux-x64-glibc@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-x64-glibc/-/watcher-linux-x64-glibc-2.5.1.tgz#4d2ea0f633eb1917d83d483392ce6181b6a92e4e"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-x64-glibc/-/watcher-linux-x64-glibc-2.5.6.tgz#ce437accdc4b30f93a090b4a221fd95cd9b89639"
-  integrity sha512-GcESn8NZySmfwlTsIur+49yDqSny2IhPeZfXunQi48DMugKeZ7uy1FX83pO0X22sHntJ4Ub+9k34XQCX+oHt2A==
+  integrity sha512-kbT5wvNQlx7NaGjzPFu8nVIW1rWqV780O7ZtkjuWaPUgpv2NMFpjYERVi0UYj1msZNyCzGlaCWEtzc+exjMGbQ==
-"@parcel/watcher-linux-x64-musl@2.5.1":
+"@parcel/watcher-linux-x64-musl@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-x64-musl/-/watcher-linux-x64-musl-2.5.1.tgz#277b346b05db54f55657301dd77bdf99d63606ee"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-linux-x64-musl/-/watcher-linux-x64-musl-2.5.6.tgz#02400c54b4a67efcc7e2327b249711920ac969e2"
-  integrity sha512-n0E2EQbatQ3bXhcH2D1XIAANAcTZkQICBPVaxMeaCVBtOpBZpWJuf7LwyWPSBDITb7In8mqQgJ7gH8CILCURXg==
+  integrity sha512-1JRFeC+h7RdXwldHzTsmdtYR/Ku8SylLgTU/reMuqdVD7CtLwf0VR1FqeprZ0eHQkO0vqsbvFLXUmYm/uNKJBg==
-"@parcel/watcher-win32-arm64@2.5.1":
+"@parcel/watcher-win32-arm64@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-win32-arm64/-/watcher-win32-arm64-2.5.1.tgz#7e9e02a26784d47503de1d10e8eab6cceb524243"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-win32-arm64/-/watcher-win32-arm64-2.5.6.tgz#caae3d3c7583ca0a7171e6bd142c34d20ea1691e"
-  integrity sha512-RFzklRvmc3PkjKjry3hLF9wD7ppR4AKcWNzH7kXR7GUe0Igb3Nz8fyPwtZCSquGrhU5HhUNDr/mKBqj7tqA2Vw==
+  integrity sha512-3ukyebjc6eGlw9yRt678DxVF7rjXatWiHvTXqphZLvo7aC5NdEgFufVwjFfY51ijYEWpXbqF5jtrK275z52D4Q==
-"@parcel/watcher-win32-ia32@2.5.1":
+"@parcel/watcher-win32-ia32@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-win32-ia32/-/watcher-win32-ia32-2.5.1.tgz#2d0f94fa59a873cdc584bf7f6b1dc628ddf976e6"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-win32-ia32/-/watcher-win32-ia32-2.5.6.tgz#9ac922550896dfe47bfc5ae3be4f1bcaf8155d6d"
-  integrity sha512-c2KkcVN+NJmuA7CGlaGD1qJh1cLfDnQsHjE89E60vUEMlqduHGCdCLJCID5geFVM0dOtA3ZiIO8BoEQmzQVfpQ==
+  integrity sha512-k35yLp1ZMwwee3Ez/pxBi5cf4AoBKYXj00CZ80jUz5h8prpiaQsiRPKQMxoLstNuqe2vR4RNPEAEcjEFzhEz/g==
-"@parcel/watcher-win32-x64@2.5.1":
+"@parcel/watcher-win32-x64@2.5.6":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher-win32-x64/-/watcher-win32-x64-2.5.1.tgz#ae52693259664ba6f2228fa61d7ee44b64ea0947"
+  resolved "https://registry.yarnpkg.com/@parcel/watcher-win32-x64/-/watcher-win32-x64-2.5.6.tgz#73fdafba2e21c448f0e456bbe13178d8fe11739d"
-  integrity sha512-9lHBdJITeNR++EvSQVUcaZoWupyHfXe1jZvGZ06O/5MflPcuPLtEphScIBL+AiCWBO46tDSHzWyD0uDmmZqsgA==
+  integrity sha512-hbQlYcCq5dlAX9Qx+kFb0FHue6vbjlf0FrNzSKdYK2APUf7tGfGxQCk2ihEREmbR6ZMc0MVAD5RIX/41gpUzTw==
-"@parcel/watcher@2.5.1":
+"@parcel/watcher@^2.5.1":
-  version "2.5.1"
+  version "2.5.6"
-  resolved "https://registry.yarnpkg.com/@parcel/watcher/-/watcher-2.5.1.tgz#342507a9cfaaf172479a882309def1e991fb1200"
+  resolved "https://registry.npmjs.org/@parcel/watcher/-/watcher-2.5.6.tgz"
-  integrity sha512-dfUnCxiN9H4ap84DvD2ubjw+3vUNpstxa0TneY/Paat8a3R4uQZDLSvWjmznAY/DoahqTHl9V46HF/Zs3F29pg==
+  integrity sha512-tmmZ3lQxAe/k/+rNnXQRawJ4NjxO2hqiOLTHvWchtGZULp4RyFeh6aU4XdOYBFe2KE1oShQTv4AblOs2iOrNnQ==
  dependencies:
-    detect-libc "^1.0.3"
+    detect-libc "^2.0.3"
    is-glob "^4.0.3"
    micromatch "^4.0.5"
    node-addon-api "^7.0.0"
    picomatch "^4.0.3"
  optionalDependencies:
-    "@parcel/watcher-android-arm64" "2.5.1"
+    "@parcel/watcher-android-arm64" "2.5.6"
-    "@parcel/watcher-darwin-arm64" "2.5.1"
+    "@parcel/watcher-darwin-arm64" "2.5.6"
-    "@parcel/watcher-darwin-x64" "2.5.1"
+    "@parcel/watcher-darwin-x64" "2.5.6"
-    "@parcel/watcher-freebsd-x64" "2.5.1"
+    "@parcel/watcher-freebsd-x64" "2.5.6"
-    "@parcel/watcher-linux-arm-glibc" "2.5.1"
+    "@parcel/watcher-linux-arm-glibc" "2.5.6"
-    "@parcel/watcher-linux-arm-musl" "2.5.1"
+    "@parcel/watcher-linux-arm-musl" "2.5.6"
-    "@parcel/watcher-linux-arm64-glibc" "2.5.1"
+    "@parcel/watcher-linux-arm64-glibc" "2.5.6"
-    "@parcel/watcher-linux-arm64-musl" "2.5.1"
+    "@parcel/watcher-linux-arm64-musl" "2.5.6"
-    "@parcel/watcher-linux-x64-glibc" "2.5.1"
+    "@parcel/watcher-linux-x64-glibc" "2.5.6"
-    "@parcel/watcher-linux-x64-musl" "2.5.1"
+    "@parcel/watcher-linux-x64-musl" "2.5.6"
-    "@parcel/watcher-win32-arm64" "2.5.1"
+    "@parcel/watcher-win32-arm64" "2.5.6"
-    "@parcel/watcher-win32-ia32" "2.5.1"
+    "@parcel/watcher-win32-ia32" "2.5.6"
-    "@parcel/watcher-win32-x64" "2.5.1"
+    "@parcel/watcher-win32-x64" "2.5.6"
 "@pkgjs/parseargs@^0.11.0":
  version "0.11.0"
@@ -961,131 +941,124 @@
  dependencies:
    "@sinonjs/commons" "^3.0.1"
-"@tailwindcss/cli@4.3.1":
+"@tailwindcss/cli@^4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/cli/-/cli-4.3.1.tgz#bc00e49e2b70baad223969071e4e380da7123afe"
+  resolved "https://registry.npmjs.org/@tailwindcss/cli/-/cli-4.2.1.tgz"
-  integrity sha512-ZWPy20rF+TBfTImxDMG3Wr75Y3RpaPlo9lc+oJbInlMyjT+XPkTVKVIL5RZ7JirXuIahcfHoLNFRmDorKi+JQQ==
+  integrity sha512-b7MGn51IA80oSG+7fuAgzfQ+7pZBgjzbqwmiv6NO7/+a1sev32cGqnwhscT7h0EcAvMa9r7gjRylqOH8Xhc4DA==
  dependencies:
-    "@parcel/watcher" "2.5.1"
+    "@parcel/watcher" "^2.5.1"
-    "@tailwindcss/node" "4.3.1"
+    "@tailwindcss/node" "4.2.1"
-    "@tailwindcss/oxide" "4.3.1"
+    "@tailwindcss/oxide" "4.2.1"
-    enhanced-resolve "5.21.6"
+    enhanced-resolve "^5.19.0"
    mri "^1.2.0"
    picocolors "^1.1.1"
-    tailwindcss "4.3.1"
+    tailwindcss "4.2.1"
-"@tailwindcss/node@4.3.1":
+"@tailwindcss/node@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/node/-/node-4.3.1.tgz#77402afcfa29c4b48b8494d0edfc4428d0a504ba"
+  resolved "https://registry.npmjs.org/@tailwindcss/node/-/node-4.2.1.tgz"
-  integrity sha512-6NDaqRoAMSXD1mr/RXu0HBvNE9a2n5tHPsxu9XHLws8o4Twes5rBM2205SUUiJ9goAtadrN6xTGX0UDEwp/N4A==
+  integrity sha512-jlx6sLk4EOwO6hHe1oCGm1Q4AN/s0rSrTTPBGPM0/RQ6Uylwq17FuU8IeJJKEjtc6K6O07zsvP+gDO6MMWo7pg==
  dependencies:
    "@jridgewell/remapping" "^2.3.5"
-    enhanced-resolve "5.21.6"
+    enhanced-resolve "^5.19.0"
-    jiti "^2.7.0"
+    jiti "^2.6.1"
-    lightningcss "1.32.0"
+    lightningcss "1.31.1"
    magic-string "^0.30.21"
    source-map-js "^1.2.1"
-    tailwindcss "4.3.1"
+    tailwindcss "4.2.1"
-"@tailwindcss/oxide-android-arm64@4.3.1":
+"@tailwindcss/oxide-android-arm64@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-android-arm64/-/oxide-android-arm64-4.3.1.tgz#83c6762cd383a2ebc6e01897b0f35f19225e6653"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-android-arm64/-/oxide-android-arm64-4.2.1.tgz#a7c24919b607e7f884e6ab97799d12c7fb5b47bd"
-  integrity sha512-SVlyf61g374l5cHyg8x9kf5xmLcOaxvOTsbsqDnSsDJaKOEFZ7GCvi84VAVGpxojYOs1+3K6M0UjXfqPU8vmOQ==
+  integrity sha512-eZ7G1Zm5EC8OOKaesIKuw77jw++QJ2lL9N+dDpdQiAB/c/B2wDh0QPFHbkBVrXnwNugvrbJFk1gK2SsVjwWReg==
-"@tailwindcss/oxide-darwin-arm64@4.3.1":
+"@tailwindcss/oxide-darwin-arm64@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-darwin-arm64/-/oxide-darwin-arm64-4.3.1.tgz#2558b7e835889ad721823e4dcb50dd5071d747d8"
+  resolved "https://registry.npmjs.org/@tailwindcss/oxide-darwin-arm64/-/oxide-darwin-arm64-4.2.1.tgz"
-  integrity sha512-hVnWLwv+e/l7c4WKyVtHVrIPvYdqWHjRB3MDIqARynzFtnQg85kmQEFCbV9Ja0VVx4xXTIiDWY60Y7iz/iNoDA==
+  integrity sha512-q/LHkOstoJ7pI1J0q6djesLzRvQSIfEto148ppAd+BVQK0JYjQIFSK3JgYZJa+Yzi0DDa52ZsQx2rqytBnf8Hw==
-"@tailwindcss/oxide-darwin-x64@4.3.1":
+"@tailwindcss/oxide-darwin-x64@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-darwin-x64/-/oxide-darwin-x64-4.3.1.tgz#d987957b87a26668b6d0117ccd4a8a4d1a318a2b"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-darwin-x64/-/oxide-darwin-x64-4.2.1.tgz#1e59ef0665f6cb9e658bf0ebcb3cb50f21b2c175"
-  integrity sha512-Cf7abu0WVgbhU7ANgPUnSAvm7nCvMweusHb8FnaHlLfv/Caq4GYaEZg7ZImzzmjx4lIAfuS8q+eLIS7A7IzxIg==
+  integrity sha512-/f/ozlaXGY6QLbpvd/kFTro2l18f7dHKpB+ieXz+Cijl4Mt9AI2rTrpq7V+t04nK+j9XBQHnSMdeQRhbGyt6fw==
-"@tailwindcss/oxide-freebsd-x64@4.3.1":
+"@tailwindcss/oxide-freebsd-x64@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-freebsd-x64/-/oxide-freebsd-x64-4.3.1.tgz#75b342c81a07b1afa437976ec82f86d372431da7"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-freebsd-x64/-/oxide-freebsd-x64-4.2.1.tgz#6b0c75e9dac7f1a241cb9a5eaa89f0d9664835b6"
-  integrity sha512-ZZqzX2Y+GXtXXfqSfpJhDm60OoZfvLHLCgm+J7NVqgHHJjG/m9ugZI77RwTsVd4fnBJuCFP6Ae6kTJb71UdS8g==
+  integrity sha512-5e/AkgYJT/cpbkys/OU2Ei2jdETCLlifwm7ogMC7/hksI2fC3iiq6OcXwjibcIjPung0kRtR3TxEITkqgn0TcA==
-"@tailwindcss/oxide-linux-arm-gnueabihf@4.3.1":
+"@tailwindcss/oxide-linux-arm-gnueabihf@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-arm-gnueabihf/-/oxide-linux-arm-gnueabihf-4.3.1.tgz#6730adc6d17187eeeff2f14f6a914d009749cb97"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-arm-gnueabihf/-/oxide-linux-arm-gnueabihf-4.2.1.tgz#717044d8fe746b1f0760485946c0c9a900174f7b"
-  integrity sha512-/Ah/xik0LaMYfv9DZ0S/t4pBlBNYOcqtRwusjgovHkvT8ixueWCLyJjsaF5kQIckjb4IT8Q6K6p/iPmZMixYgg==
+  integrity sha512-Uny1EcVTTmerCKt/1ZuKTkb0x8ZaiuYucg2/kImO5A5Y/kBz41/+j0gxUZl+hTF3xkWpDmHX+TaWhOtba2Fyuw==
-"@tailwindcss/oxide-linux-arm64-gnu@4.3.1":
+"@tailwindcss/oxide-linux-arm64-gnu@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-arm64-gnu/-/oxide-linux-arm64-gnu-4.3.1.tgz#869d16b3d9bd8097b797a3dd876db0368c07eae3"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-arm64-gnu/-/oxide-linux-arm64-gnu-4.2.1.tgz#f544b0faf166d80791347911b2dd4372a893129d"
-  integrity sha512-gqdFoVJlw444GvpnheZLHmvTzSxI/cOUUh2KSNejQjTcYkW062SVD+En0rUgD+QV91bz1XGIGtt1HJd48xUGbQ==
+  integrity sha512-CTrwomI+c7n6aSSQlsPL0roRiNMDQ/YzMD9EjcR+H4f0I1SQ8QqIuPnsVp7QgMkC1Qi8rtkekLkOFjo7OlEFRQ==
-"@tailwindcss/oxide-linux-arm64-musl@4.3.1":
+"@tailwindcss/oxide-linux-arm64-musl@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-arm64-musl/-/oxide-linux-arm64-musl-4.3.1.tgz#ab110680ce3c7a2a135656db4402dffc1fb9c1d7"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-arm64-musl/-/oxide-linux-arm64-musl-4.2.1.tgz#9fbaf8dc00b858a2b955526abb15d88f5678d1ef"
-  integrity sha512-Bwv9KwOvE0VKa86xPFif9b9c3Y1NxOV1P0gLti/IYaWEsQYZXDlxfGEtA8mdDZ7SG3wyNXAWYT5SIn3giL57oA==
+  integrity sha512-WZA0CHRL/SP1TRbA5mp9htsppSEkWuQ4KsSUumYQnyl8ZdT39ntwqmz4IUHGN6p4XdSlYfJwM4rRzZLShHsGAQ==
-"@tailwindcss/oxide-linux-x64-gnu@4.3.1":
+"@tailwindcss/oxide-linux-x64-gnu@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-x64-gnu/-/oxide-linux-x64-gnu-4.3.1.tgz#422a4175a76ae60dd9d17946eec3584cb636352f"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-x64-gnu/-/oxide-linux-x64-gnu-4.2.1.tgz#6ab4e6b8d308d037a1155b8443df5941dbfa6aa1"
-  integrity sha512-Ymi8O8T15HYQdOUWUtTI6ldN0neHP85FC+Qz32xTcZ7iJXtem/x8ITev0o1e9e5rkqj4lONZfTRLvkmin1+tKg==
+  integrity sha512-qMFzxI2YlBOLW5PhblzuSWlWfwLHaneBE0xHzLrBgNtqN6mWfs+qYbhryGSXQjFYB1Dzf5w+LN5qbUTPhW7Y5g==
-"@tailwindcss/oxide-linux-x64-musl@4.3.1":
+"@tailwindcss/oxide-linux-x64-musl@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-x64-musl/-/oxide-linux-x64-musl-4.3.1.tgz#f4c714a653a0e742955d2af2c53d0064b4c500d1"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-linux-x64-musl/-/oxide-linux-x64-musl-4.2.1.tgz#52c55593394dff85f1fa88172f69f8fdcde182b6"
-  integrity sha512-M+P/91qJ6uILLw4k2G93GMDRAXj61SMvFQYt39AqvUqYgExXpLL5aepfns7sj4HiAQeolirQF9E0lzRvdf4zPQ==
+  integrity sha512-5r1X2FKnCMUPlXTWRYpHdPYUY6a1Ar/t7P24OuiEdEOmms5lyqjDRvVY1yy9Rmioh+AunQ0rWiOTPE8F9A3v5g==
-"@tailwindcss/oxide-wasm32-wasi@4.3.1":
+"@tailwindcss/oxide-wasm32-wasi@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-wasm32-wasi/-/oxide-wasm32-wasi-4.3.1.tgz#32172ca8b2427b9c2bb09c97756960185b7d4fc0"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-wasm32-wasi/-/oxide-wasm32-wasi-4.2.1.tgz#7401e35f881d3654b6180badd1243d75a2702ea5"
-  integrity sha512-zsM8uOeqvVGHsAXsJxsT28ttosFahLJKCLOTUBqRAtKnVgGSRitds9T432QiT8b77Yga7JIBkulIRRlJPtYhRA==
+  integrity sha512-MGFB5cVPvshR85MTJkEvqDUnuNoysrsRxd6vnk1Lf2tbiqNlXpHYZqkqOQalydienEWOHHFyyuTSYRsLfxFJ2Q==
  dependencies:
-    "@emnapi/core" "^1.10.0"
+    "@emnapi/core" "^1.8.1"
-    "@emnapi/runtime" "^1.10.0"
+    "@emnapi/runtime" "^1.8.1"
-    "@emnapi/wasi-threads" "^1.2.1"
+    "@emnapi/wasi-threads" "^1.1.0"
-    "@napi-rs/wasm-runtime" "^1.1.4"
+    "@napi-rs/wasm-runtime" "^1.1.1"
-    "@tybys/wasm-util" "^0.10.2"
+    "@tybys/wasm-util" "^0.10.1"
    tslib "^2.8.1"
-"@tailwindcss/oxide-win32-arm64-msvc@4.3.1":
+"@tailwindcss/oxide-win32-arm64-msvc@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-win32-arm64-msvc/-/oxide-win32-arm64-msvc-4.3.1.tgz#07a11b6eb1f578d012460e6ad6f2352a28d32514"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-win32-arm64-msvc/-/oxide-win32-arm64-msvc-4.2.1.tgz#63a502e7b696dcd976aa356b94ce0f4f8f832c44"
-  integrity sha512-aiNvSq9BsVk8V513lDKlrCFAgf8qBMPZTpgEhInL+NwQqs97mYmupVMrPrgBBSL8Pv/0zXu9MrMF9rMun1ZeNg==
+  integrity sha512-YlUEHRHBGnCMh4Nj4GnqQyBtsshUPdiNroZj8VPkvTZSoHsilRCwXcVKnG9kyi0ZFAS/3u+qKHBdDc81SADTRA==
-"@tailwindcss/oxide-win32-x64-msvc@4.3.1":
+"@tailwindcss/oxide-win32-x64-msvc@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-win32-x64-msvc/-/oxide-win32-x64-msvc-4.3.1.tgz#60c6095d97b141c02de36bb52a16c358d9bdaa98"
+  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide-win32-x64-msvc/-/oxide-win32-x64-msvc-4.2.1.tgz#8cc59b28ebc4dc866c0c14d7057f07f0ed04c4a8"
-  integrity sha512-xDEyu1rg290472FEGaKHnzyDyh5QH+AlWvsU5hMoMtPpzmKlRI0jaYKCgSHDYtaQWZOYbMaduSyCwFwY4n1HmA==
+  integrity sha512-rbO34G5sMWWyrN/idLeVxAZgAKWrn5LiR3/I90Q9MkA67s6T1oB0xtTe+0heoBvHSpbU9Mk7i6uwJnpo4u21XQ==
-"@tailwindcss/oxide@4.3.1":
+"@tailwindcss/oxide@4.2.1":
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/@tailwindcss/oxide/-/oxide-4.3.1.tgz#6fdd28b3abf785e2c2cac31f52c4755875826828"
+  resolved "https://registry.npmjs.org/@tailwindcss/oxide/-/oxide-4.2.1.tgz"
-  integrity sha512-yVPyo8RNkabVr3O2EhHEE0Rewu7YKzc1DhIqfL46LKveFrmu9XbDazNOJY7/GRuvw1h6u3utWnR29H/p5JPlgA==
+  integrity sha512-yv9jeEFWnjKCI6/T3Oq50yQEOqmpmpfzG1hcZsAOaXFQPfzWprWrlHSdGPEF3WQTi8zu8ohC9Mh9J470nT5pUw==
  optionalDependencies:
-    "@tailwindcss/oxide-android-arm64" "4.3.1"
+    "@tailwindcss/oxide-android-arm64" "4.2.1"
-    "@tailwindcss/oxide-darwin-arm64" "4.3.1"
+    "@tailwindcss/oxide-darwin-arm64" "4.2.1"
-    "@tailwindcss/oxide-darwin-x64" "4.3.1"
+    "@tailwindcss/oxide-darwin-x64" "4.2.1"
-    "@tailwindcss/oxide-freebsd-x64" "4.3.1"
+    "@tailwindcss/oxide-freebsd-x64" "4.2.1"
-    "@tailwindcss/oxide-linux-arm-gnueabihf" "4.3.1"
+    "@tailwindcss/oxide-linux-arm-gnueabihf" "4.2.1"
-    "@tailwindcss/oxide-linux-arm64-gnu" "4.3.1"
+    "@tailwindcss/oxide-linux-arm64-gnu" "4.2.1"
-    "@tailwindcss/oxide-linux-arm64-musl" "4.3.1"
+    "@tailwindcss/oxide-linux-arm64-musl" "4.2.1"
-    "@tailwindcss/oxide-linux-x64-gnu" "4.3.1"
+    "@tailwindcss/oxide-linux-x64-gnu" "4.2.1"
-    "@tailwindcss/oxide-linux-x64-musl" "4.3.1"
+    "@tailwindcss/oxide-linux-x64-musl" "4.2.1"
-    "@tailwindcss/oxide-wasm32-wasi" "4.3.1"
+    "@tailwindcss/oxide-wasm32-wasi" "4.2.1"
-    "@tailwindcss/oxide-win32-arm64-msvc" "4.3.1"
+    "@tailwindcss/oxide-win32-arm64-msvc" "4.2.1"
-    "@tailwindcss/oxide-win32-x64-msvc" "4.3.1"
+    "@tailwindcss/oxide-win32-x64-msvc" "4.2.1"
-"@tybys/wasm-util@^0.10.0":
+"@tybys/wasm-util@^0.10.0", "@tybys/wasm-util@^0.10.1":
  version "0.10.1"
  resolved "https://registry.yarnpkg.com/@tybys/wasm-util/-/wasm-util-0.10.1.tgz#ecddd3205cf1e2d5274649ff0eedd2991ed7f414"
  integrity sha512-9tTaPJLSiejZKx+Bmog4uSubteqTvFrVrURwkmHixBo0G4seD0zUxp98E1DzUBJxLQ3NPwXrGKDiVjwx/DpPsg==
  dependencies:
    tslib "^2.4.0"
 "@tybys/wasm-util@^0.10.2", "@tybys/wasm-util@^0.10.3":
  version "0.10.4"
  resolved "https://registry.yarnpkg.com/@tybys/wasm-util/-/wasm-util-0.10.4.tgz#3e85ecb266f9d1722250e89bc69528615720b154"
  integrity sha512-W3c4gRigFS0T/Ma4qIYF3GDAc5AQdHb1yL5znJT1Zv1YaD9Kitx656wBjvr19qbiosmZT8lWDM5BEMynUqX65A==
  dependencies:
    tslib "^2.4.0"
 "@types/babel__core@^7.20.5":
  version "7.20.5"
  resolved "https://registry.npmjs.org/@types/babel__core/-/babel__core-7.20.5.tgz"
@@ -1609,11 +1582,6 @@ deepmerge@^4.3.1:
  resolved "https://registry.npmjs.org/deepmerge/-/deepmerge-4.3.1.tgz"
  integrity sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A==
 detect-libc@^1.0.3:
  version "1.0.3"
  resolved "https://registry.yarnpkg.com/detect-libc/-/detect-libc-1.0.3.tgz#fa137c4bd698edf55cd5cd02ac559f91a4c4ba9b"
  integrity sha512-pGjwhsmsp4kL2RTz08wcOlGN83otlqHeD/Z5T8GXZB+/YcpQ/dgo+lbU8ZsGxV0HIvqqxo9l7mqYwyYMD9bKDg==
 detect-libc@^2.0.3:
  version "2.1.2"
  resolved "https://registry.npmjs.org/detect-libc/-/detect-libc-2.1.2.tgz"
@@ -1654,13 +1622,13 @@ emoji-regex@^9.2.2:
  resolved "https://registry.npmjs.org/emoji-regex/-/emoji-regex-9.2.2.tgz"
  integrity sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==
-enhanced-resolve@5.21.6:
+enhanced-resolve@^5.19.0:
-  version "5.21.6"
+  version "5.19.0"
-  resolved "https://registry.yarnpkg.com/enhanced-resolve/-/enhanced-resolve-5.21.6.tgz#aa207b43cf658e6ab3ba06896edc00c13c3127c6"
+  resolved "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-5.19.0.tgz"
-  integrity sha512-aNnGCvbJ/RIyWo1IuhNdVjnNF+EjH9wpzpNHt+ci/m9He9LJvUN8wrCcXjp9cWsGNAuvSpVFTx/vraAFQ8qGjQ==
+  integrity sha512-phv3E1Xl4tQOShqSte26C7Fl84EwUdZsyOuSSk9qtAGyyQs2s3jJzComh+Abf4g187lUUAvH+H26omrqia2aGg==
  dependencies:
    graceful-fs "^4.2.4"
-    tapable "^2.3.3"
+    tapable "^2.3.0"
 error-ex@^1.3.1:
  version "1.3.4"
@@ -2501,10 +2469,10 @@ jest@^30.2.0:
    import-local "^3.2.0"
    jest-cli "30.2.0"
-jiti@^2.7.0:
+jiti@^2.6.1:
-  version "2.7.0"
+  version "2.6.1"
-  resolved "https://registry.yarnpkg.com/jiti/-/jiti-2.7.0.tgz#974228f2f4ca2bc21885a1797b45fea68e950c64"
+  resolved "https://registry.npmjs.org/jiti/-/jiti-2.6.1.tgz"
-  integrity sha512-AC/7JofJvZGrrneWNaEnJeOLUx+JlGt7tNa0wZiRPT4MY1wmfKjt2+6O2p2uz2+skll8OZZmJMNqeke7kKbNgQ==
+  integrity sha512-ekilCSN1jwRvIbgeg/57YFh8qQDNbwDb9xT/qu2DAHbFFZUicIl4ygVaAvzveMhMVr3LnpSKTNnwt8PoOfmKhQ==
 js-tokens@^4.0.0:
  version "4.0.0"
@@ -2581,79 +2549,79 @@ libsodium-wrappers-sumo@^0.8.2:
  dependencies:
    libsodium-sumo "^0.8.0"
-lightningcss-android-arm64@1.32.0:
+lightningcss-android-arm64@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-android-arm64/-/lightningcss-android-arm64-1.32.0.tgz#f033885116dfefd9c6f54787523e3514b61e1968"
+  resolved "https://registry.yarnpkg.com/lightningcss-android-arm64/-/lightningcss-android-arm64-1.31.1.tgz#609ff48332adff452a8157a7c2842fd692a8eac4"
-  integrity sha512-YK7/ClTt4kAK0vo6w3X+Pnm0D2cf2vPHbhOXdoNti1Ga0al1P4TBZhwjATvjNwLEBCnKvjJc2jQgHXH0NEwlAg==
+  integrity sha512-HXJF3x8w9nQ4jbXRiNppBCqeZPIAfUo8zE/kOEGbW5NZvGc/K7nMxbhIr+YlFlHW5mpbg/YFPdbnCh1wAXCKFg==
-lightningcss-darwin-arm64@1.32.0:
+lightningcss-darwin-arm64@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-darwin-arm64/-/lightningcss-darwin-arm64-1.32.0.tgz#50b71871b01c8199584b649e292547faea7af9b5"
+  resolved "https://registry.npmjs.org/lightningcss-darwin-arm64/-/lightningcss-darwin-arm64-1.31.1.tgz"
-  integrity sha512-RzeG9Ju5bag2Bv1/lwlVJvBE3q6TtXskdZLLCyfg5pt+HLz9BqlICO7LZM7VHNTTn/5PRhHFBSjk5lc4cmscPQ==
+  integrity sha512-02uTEqf3vIfNMq3h/z2cJfcOXnQ0GRwQrkmPafhueLb2h7mqEidiCzkE4gBMEH65abHRiQvhdcQ+aP0D0g67sg==
-lightningcss-darwin-x64@1.32.0:
+lightningcss-darwin-x64@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-darwin-x64/-/lightningcss-darwin-x64-1.32.0.tgz#35f3e97332d130b9ca181e11b568ded6aebc6d5e"
+  resolved "https://registry.yarnpkg.com/lightningcss-darwin-x64/-/lightningcss-darwin-x64-1.31.1.tgz#f7482c311273571ec0c2bd8277c1f5f6e90e03a4"
-  integrity sha512-U+QsBp2m/s2wqpUYT/6wnlagdZbtZdndSmut/NJqlCcMLTWp5muCrID+K5UJ6jqD2BFshejCYXniPDbNh73V8w==
+  integrity sha512-1ObhyoCY+tGxtsz1lSx5NXCj3nirk0Y0kB/g8B8DT+sSx4G9djitg9ejFnjb3gJNWo7qXH4DIy2SUHvpoFwfTA==
-lightningcss-freebsd-x64@1.32.0:
+lightningcss-freebsd-x64@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-freebsd-x64/-/lightningcss-freebsd-x64-1.32.0.tgz#9777a76472b64ed6ff94342ad64c7bafd794a575"
+  resolved "https://registry.yarnpkg.com/lightningcss-freebsd-x64/-/lightningcss-freebsd-x64-1.31.1.tgz#91df1bb290f1cb7bb2af832d7d0d8809225e0124"
-  integrity sha512-JCTigedEksZk3tHTTthnMdVfGf61Fky8Ji2E4YjUTEQX14xiy/lTzXnu1vwiZe3bYe0q+SpsSH/CTeDXK6WHig==
+  integrity sha512-1RINmQKAItO6ISxYgPwszQE1BrsVU5aB45ho6O42mu96UiZBxEXsuQ7cJW4zs4CEodPUioj/QrXW1r9pLUM74A==
-lightningcss-linux-arm-gnueabihf@1.32.0:
+lightningcss-linux-arm-gnueabihf@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-linux-arm-gnueabihf/-/lightningcss-linux-arm-gnueabihf-1.32.0.tgz#13ae652e1ab73b9135d7b7da172f666c410ad53d"
+  resolved "https://registry.yarnpkg.com/lightningcss-linux-arm-gnueabihf/-/lightningcss-linux-arm-gnueabihf-1.31.1.tgz#c3cad5ae8b70045f21600dc95295ab6166acf57e"
-  integrity sha512-x6rnnpRa2GL0zQOkt6rts3YDPzduLpWvwAF6EMhXFVZXD4tPrBkEFqzGowzCsIWsPjqSK+tyNEODUBXeeVHSkw==
+  integrity sha512-OOCm2//MZJ87CdDK62rZIu+aw9gBv4azMJuA8/KB74wmfS3lnC4yoPHm0uXZ/dvNNHmnZnB8XLAZzObeG0nS1g==
-lightningcss-linux-arm64-gnu@1.32.0:
+lightningcss-linux-arm64-gnu@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-linux-arm64-gnu/-/lightningcss-linux-arm64-gnu-1.32.0.tgz#417858795a94592f680123a1b1f9da8a0e1ef335"
+  resolved "https://registry.yarnpkg.com/lightningcss-linux-arm64-gnu/-/lightningcss-linux-arm64-gnu-1.31.1.tgz#a5c4f6a5ac77447093f61b209c0bd7fef1f0a3e3"
-  integrity sha512-0nnMyoyOLRJXfbMOilaSRcLH3Jw5z9HDNGfT/gwCPgaDjnx0i8w7vBzFLFR1f6CMLKF8gVbebmkUN3fa/kQJpQ==
+  integrity sha512-WKyLWztD71rTnou4xAD5kQT+982wvca7E6QoLpoawZ1gP9JM0GJj4Tp5jMUh9B3AitHbRZ2/H3W5xQmdEOUlLg==
-lightningcss-linux-arm64-musl@1.32.0:
+lightningcss-linux-arm64-musl@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-linux-arm64-musl/-/lightningcss-linux-arm64-musl-1.32.0.tgz#6be36692e810b718040802fd809623cffe732133"
+  resolved "https://registry.yarnpkg.com/lightningcss-linux-arm64-musl/-/lightningcss-linux-arm64-musl-1.31.1.tgz#af26ab8f829b727ada0a200938a6c8796ff36900"
-  integrity sha512-UpQkoenr4UJEzgVIYpI80lDFvRmPVg6oqboNHfoH4CQIfNA+HOrZ7Mo7KZP02dC6LjghPQJeBsvXhJod/wnIBg==
+  integrity sha512-mVZ7Pg2zIbe3XlNbZJdjs86YViQFoJSpc41CbVmKBPiGmC4YrfeOyz65ms2qpAobVd7WQsbW4PdsSJEMymyIMg==
-lightningcss-linux-x64-gnu@1.32.0:
+lightningcss-linux-x64-gnu@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-linux-x64-gnu/-/lightningcss-linux-x64-gnu-1.32.0.tgz#0b7803af4eb21cfd38dd39fe2abbb53c7dd091f6"
+  resolved "https://registry.yarnpkg.com/lightningcss-linux-x64-gnu/-/lightningcss-linux-x64-gnu-1.31.1.tgz#a891d44e84b71c0d88959feb9a7522bbf61450ee"
-  integrity sha512-V7Qr52IhZmdKPVr+Vtw8o+WLsQJYCTd8loIfpDaMRWGUZfBOYEJeyJIkqGIDMZPwPx24pUMfwSxxI8phr/MbOA==
+  integrity sha512-xGlFWRMl+0KvUhgySdIaReQdB4FNudfUTARn7q0hh/V67PVGCs3ADFjw+6++kG1RNd0zdGRlEKa+T13/tQjPMA==
-lightningcss-linux-x64-musl@1.32.0:
+lightningcss-linux-x64-musl@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-linux-x64-musl/-/lightningcss-linux-x64-musl-1.32.0.tgz#88dc8ba865ddddb1ac5ef04b0f161804418c163b"
+  resolved "https://registry.yarnpkg.com/lightningcss-linux-x64-musl/-/lightningcss-linux-x64-musl-1.31.1.tgz#8c8b21def851f4d477fa897b80cb3db2b650bc6e"
-  integrity sha512-bYcLp+Vb0awsiXg/80uCRezCYHNg1/l3mt0gzHnWV9XP1W5sKa5/TCdGWaR/zBM2PeF/HbsQv/j2URNOiVuxWg==
+  integrity sha512-eowF8PrKHw9LpoZii5tdZwnBcYDxRw2rRCyvAXLi34iyeYfqCQNA9rmUM0ce62NlPhCvof1+9ivRaTY6pSKDaA==
-lightningcss-win32-arm64-msvc@1.32.0:
+lightningcss-win32-arm64-msvc@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-win32-arm64-msvc/-/lightningcss-win32-arm64-msvc-1.32.0.tgz#4f30ba3fa5e925f5b79f945e8cc0d176c3b1ab38"
+  resolved "https://registry.yarnpkg.com/lightningcss-win32-arm64-msvc/-/lightningcss-win32-arm64-msvc-1.31.1.tgz#79000fb8c57e94a91b8fc643e74d5a54407d7080"
-  integrity sha512-8SbC8BR40pS6baCM8sbtYDSwEVQd4JlFTOlaD3gWGHfThTcABnNDBda6eTZeqbofalIJhFx0qKzgHJmcPTnGdw==
+  integrity sha512-aJReEbSEQzx1uBlQizAOBSjcmr9dCdL3XuC/6HLXAxmtErsj2ICo5yYggg1qOODQMtnjNQv2UHb9NpOuFtYe4w==
-lightningcss-win32-x64-msvc@1.32.0:
+lightningcss-win32-x64-msvc@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss-win32-x64-msvc/-/lightningcss-win32-x64-msvc-1.32.0.tgz#141aa5605645064928902bb4af045fa7d9f4220a"
+  resolved "https://registry.yarnpkg.com/lightningcss-win32-x64-msvc/-/lightningcss-win32-x64-msvc-1.31.1.tgz#7f025274c81c7d659829731e09c8b6f442209837"
-  integrity sha512-Amq9B/SoZYdDi1kFrojnoqPLxYhQ4Wo5XiL8EVJrVsB8ARoC1PWW6VGtT0WKCemjy8aC+louJnjS7U18x3b06Q==
+  integrity sha512-I9aiFrbd7oYHwlnQDqr1Roz+fTz61oDDJX7n9tYF9FJymH1cIN1DtKw3iYt6b8WZgEjoNwVSncwF4wx/ZedMhw==
-lightningcss@1.32.0:
+lightningcss@1.31.1:
-  version "1.32.0"
+  version "1.31.1"
-  resolved "https://registry.yarnpkg.com/lightningcss/-/lightningcss-1.32.0.tgz#b85aae96486dcb1bf49a7c8571221273f4f1e4a9"
+  resolved "https://registry.npmjs.org/lightningcss/-/lightningcss-1.31.1.tgz"
-  integrity sha512-NXYBzinNrblfraPGyrbPoD19C1h9lfI/1mzgWYvXUTe414Gz/X1FD2XBZSZM7rRTrMA8JL3OtAaGifrIKhQ5yQ==
+  integrity sha512-l51N2r93WmGUye3WuFoN5k10zyvrVs0qfKBhyC5ogUQ6Ew6JUSswh78mbSO+IU3nTWsyOArqPCcShdQSadghBQ==
  dependencies:
    detect-libc "^2.0.3"
  optionalDependencies:
-    lightningcss-android-arm64 "1.32.0"
+    lightningcss-android-arm64 "1.31.1"
-    lightningcss-darwin-arm64 "1.32.0"
+    lightningcss-darwin-arm64 "1.31.1"
-    lightningcss-darwin-x64 "1.32.0"
+    lightningcss-darwin-x64 "1.31.1"
-    lightningcss-freebsd-x64 "1.32.0"
+    lightningcss-freebsd-x64 "1.31.1"
-    lightningcss-linux-arm-gnueabihf "1.32.0"
+    lightningcss-linux-arm-gnueabihf "1.31.1"
-    lightningcss-linux-arm64-gnu "1.32.0"
+    lightningcss-linux-arm64-gnu "1.31.1"
-    lightningcss-linux-arm64-musl "1.32.0"
+    lightningcss-linux-arm64-musl "1.31.1"
-    lightningcss-linux-x64-gnu "1.32.0"
+    lightningcss-linux-x64-gnu "1.31.1"
-    lightningcss-linux-x64-musl "1.32.0"
+    lightningcss-linux-x64-musl "1.31.1"
-    lightningcss-win32-arm64-msvc "1.32.0"
+    lightningcss-win32-arm64-msvc "1.31.1"
-    lightningcss-win32-x64-msvc "1.32.0"
+    lightningcss-win32-x64-msvc "1.31.1"
 lines-and-columns@^1.1.6:
  version "1.2.4"
@@ -2712,9 +2680,9 @@ merge-stream@^2.0.0:
  resolved "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz"
  integrity sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==
-micromatch@^4.0.5, micromatch@^4.0.8:
+micromatch@^4.0.8:
  version "4.0.8"
-  resolved "https://registry.yarnpkg.com/micromatch/-/micromatch-4.0.8.tgz#d66fa18f3a47076789320b9b1af32bd86d9fa202"
+  resolved "https://registry.npmjs.org/micromatch/-/micromatch-4.0.8.tgz"
  integrity sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==
  dependencies:
    braces "^3.0.3"
@@ -2905,7 +2873,7 @@ picomatch@^2.0.4, picomatch@^2.3.1:
  resolved "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz"
  integrity sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==
-picomatch@^4.0.2:
+picomatch@^4.0.2, picomatch@^4.0.3:
  version "4.0.3"
  resolved "https://registry.npmjs.org/picomatch/-/picomatch-4.0.3.tgz"
  integrity sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==
@@ -3166,15 +3134,15 @@ synckit@^0.11.8:
  dependencies:
    "@pkgr/core" "^0.2.9"
-tailwindcss@4.3.1:
+tailwindcss@4.2.1, tailwindcss@^4.2.1:
-  version "4.3.1"
+  version "4.2.1"
-  resolved "https://registry.yarnpkg.com/tailwindcss/-/tailwindcss-4.3.1.tgz#78ee06f6186bc8fb9603f8083eb703dc7dd96a10"
+  resolved "https://registry.npmjs.org/tailwindcss/-/tailwindcss-4.2.1.tgz"
-  integrity sha512-hk+TB1m+K8CYNrP6rjQaq/Y+4Zylwpa87mLYBKCunwnnQ9p+fHb7kmSfGqyEJoxF/O6CDyABWVFEafNSYKll+Q==
+  integrity sha512-/tBrSQ36vCleJkAOsy9kbNTgaxvGbyOamC30PRePTQe/o1MFwEKHQk4Cn7BNGaPtjp+PuUrByJehM1hgxfq4sw==
-tapable@^2.3.3:
+tapable@^2.3.0:
-  version "2.3.3"
+  version "2.3.0"
-  resolved "https://registry.yarnpkg.com/tapable/-/tapable-2.3.3.tgz#5da7c9992c46038221267985ab28421a8879f160"
+  resolved "https://registry.npmjs.org/tapable/-/tapable-2.3.0.tgz"
-  integrity sha512-uxc/zpqFg6x7C8vOE7lh6Lbda8eEL9zmVm/PLeTPBRhh1xCgdWaQ+J1CUieGpIfm2HdtsUpRv+HshiasBMcc6A==
+  integrity sha512-g9ljZiwki/LfxmQADO3dEY1CbpmXT5Hm2fJ+QaGKwSXUylMybePR7/67YW7jOrrvjEgL1Fmz5kzyAjWVWLlucg==
 test-exclude@^6.0.0:
  version "6.0.0"