Changelog - 2026-10-27
devz check purity ships in dev-configs
EnhancementIn one line. The browser-purity gate that ran from one repository's scripts is now devz check purity --claims <file>, so other repositories use the same engine instead of copies. Nothing changes for an application. Ships in 0.4.4.
What changed
devz check purity --claims <file> [package] [--json]. Probes every entry the claims file lists as browser-pure. The report is the same as the old script's, and a package filter that matches nothing exits 1.@venizia/dev-configs/checks. A new export withbuildManifest,deriveEntries,assertNoWorkspaceExternal,assertBrowserEsmEntry,probeEntryandcheckPurityfor a repository that wants the engine in its own tests.--json. Prints the verdict per entry (verdict, size, builtins, globals) with the repository root replaced by<root>, so two machines on one commit print the same text.- The gate is one check stricter. An entry whose bundle contains
@venizia/dev-configsfails: that package is Bun-only tooling and must never reach a browser. - The scratch file moved from the system temp to
.agents/local/tmpunder the folder the command runs in.
Who is affected
Nobody who only uses IGNIS. A repository that copied the old scripts replaces them with a claims file that exports PURITY_CLAIMS; the guide is in Checking browser purity.