[easel]

The existing public @documentdrivendx/umf-schema-browser package has no release-bound npm publishing workflow. Add a read-only immutable-release dispatcher and a main-only OIDC publisher that uploads the original GitHub release tarball, then verifies public bytes and a clean installed consumer. Registry uploads run only in GitHub Actions; no rebuild, repack, new package version or SDK publication is introduced.

The publisher binds tag/source, the four public asset digests, package provenance and every embedded manifest/hash. It rechecks artifact handoff against the verification job output before upload, rejects version collisions, disables package scripts in the privileged job, and records an existing identical version as existing_exact_bytes rather than claiming an upload. Historical mutable releases require explicit tag, source, SHA256SUMS and tarball pins. Other UMF component releases skip the dispatcher.

Validation: 17 focused controls; actual 2.0.0 release validation and anonymous npm byte comparison; canonical inventory --check; Rust boundaries (587 checked, zero findings, nine negative controls); reference boundaries (26 files); inherited stage tests (2); Actionlint for all three workflows; diff check. The inventory preserves all 578 source-module, 127 Rust-module and 76 Rust-build-input records, adding only four host-tool scripts. Scoped independent review is clear. An actual npm version-endpoint HTTP 406 was fixed by requesting application/json and adding a regression control. Replaying the workflow’s exact public npm consumer command also caught a double-loaded /dev/null config collision; separate empty user/global config files and a fresh temporary cache now pass actual public install plus entrypoint import.

External setup is pending an exact owner grant: UMF npm environment restricted to main with no per-release reviewer; existing package trusted publisher restricted to DocumentDrivenDX/umf, publish-schema-browser-npm.yml, environment npm, direct Allow npm publish; and GitHub release immutability for future UMF releases. No stored token, broader registry access, private SDK exposure or old-release byte change. Historical 2.0.0 is already public with matching bytes; the first workflow run should truthfully skip its upload.