# v0.8.0-beta.34 Release Notes

## Governed Republish of the beta.33 Tree

This candidate advances the Consumer Authority Beta acceptance record to
`0.8.0-beta.34` for a **procedural** reason. It carries the same tree as
`0.8.0-beta.33` and changes no Persona Harness authority, Fetch, Finish,
artifact transport, workflow runtime, registry channel, tag, release, observer,
or fixture behavior.

`0.8.0-beta.33` reached the `staging` channel outside
`.github/workflows/publish.yml`. Its source binding is correct — the registry
`gitHead` is `1d05e0592ce84966eb97a4e5ec230dd1548f00f2`, and `latest` was not
moved — but the governed publish path was bypassed, so two artifacts that path
produces do not exist for it:

- **No npm provenance attestation.** `publish.yml` publishes with
  `--provenance`; `0.8.0-beta.23`, published through it on 2026-08-03, carries
  a SLSA provenance attestation. `0.8.0-beta.33` carries none.
- **No release-registry readback record.** `scripts/release-registry-readback.mjs`
  is invoked in exactly one place in this repository — the post-publish step of
  `publish.yml` — so no record was produced.

npm does not permit republishing a version, so neither can be added to
`0.8.0-beta.33` retroactively. `0.8.0-beta.34` exists to obtain both through the
governed path.

`0.8.0-beta.33` is therefore terminal, non-reusable registry-publish evidence.
Its acceptance content carries forward unchanged; only its registry publish does
not. Every earlier terminal, non-reusable record described in the
`0.8.0-beta.33` notes remains as stated there.

The package-visible
[`consumer-authority-beta34-acceptance.json`](consumer-authority-beta34-acceptance.json)
is the beta.33 acceptance manifest with the version identity advanced and one
added record, `beta33HistoricalRegistryPublish`, stating the verified registry
facts above. No acceptance outcome, boundary, or claim is added or relaxed.

## Scope

This is a release-candidate procedure record. It is not a Stable, GA, or
`latest` claim, and it does not authorize moving the `latest` dist-tag.

## Verification

Publish through `.github/workflows/publish.yml` with `dist_tag: staging` and
`approval_scope: staging-only`. The run performs the canonical pack, the
publisher preflight, the provenance publish, and the registry readback in
sequence; the readback output is the evidence #122 and #115 consume.