# v0.8.0-beta.18 Release Notes

## Immutable Staging Observation

`persona-harness@0.8.0-beta.18` was published to the `staging` channel from
protected main `02a127bb996b616b9c631b1d3f48798b79527b13` with tag
`v0.8.0-beta.18`. It remains immutable staging evidence only; it grants no
promotion, Stable/GA, original consumer artifact, Finish authority, or issue
closure claim.

The publisher preserved the two-runtime boundary: Node `20.19.0`/npm `10.8.2`
created the canonical tarball, and isolated Node `24.18.0`/npm `11.16.0`
published that exact tarball without repacking the workspace.

## Postpublish Readback Result

The registry package exposed the expected version, selected `staging` mapping,
SHA-1, SRI, raw tarball SHA-256, and portable package-content identity. Those
downloaded bytes matched the frozen canonical beta18 facts.

The workflow nevertheless stopped because its readback required a registry
`gitHead` field that npm version metadata did not expose. That requirement was
not a package-byte mismatch or a source-identity failure. It is not reusable
acceptance evidence and does not authorize another beta18 publish, retry, tag,
or channel mutation.

## Supersession Boundary

The package-visible beta19 contract replaces the unsupported registry-metadata
predicate with a workflow-bound source-to-canonical-tar-to-registry-byte
reconciliation. It retains the existing canonical packer/publisher route and
requires one new immutable version and one fresh hosted registry observation.