# v0.8.0-beta.23 Release Notes

## V3 Final Observer Procedure

This package-visible procedure-only candidate advances the immutable observer
record to `0.8.0-beta.23`. It changes no Persona Harness authority, Fetch,
Finish, artifact transport, workflow runtime, registry channel, tag, release,
or fixture behavior.

`0.8.0-beta.22` is non-reusable final-observer evidence. Its host `gh`/XDG
state created `.local/state/gh/device-id` after the final commit. That result
does not establish a product defect and must not be retried. The v3 procedure
record is bound by SHA-256
`24eeeb198a683cdbdade04142aa2dca2479f94fb06bc4f39c1633d16c5286c8b`;
no local absolute path is a source of truth.

The package-visible
[`consumer-authority-beta23-acceptance.json`](consumer-authority-beta23-acceptance.json)
is the strict record for the next one-shot observation.

## Required Isolation

Every host credential, `gh`, Git, Node, and npm process uses `env -i` with
explicit absolute tool paths. The following fifteen state roots must be
absolute and outside the consumer realpath: `HOME`, `GH_CONFIG_DIR`,
`XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_STATE_HOME`, `XDG_CACHE_HOME`,
`XDG_RUNTIME_DIR`, `TMPDIR`, `APPDATA`, `LOCALAPPDATA`, `USERPROFILE`,
`GIT_CONFIG_GLOBAL`, `GIT_CONFIG_SYSTEM`, `NPM_CONFIG_USERCONFIG`, and
`NPM_CONFIG_CACHE`.

The host credential is retrieved silently outside the consumer and is handed
only to the fixed read-only observer child. It is never passed to `ph`, npm,
archive tooling, or public output. `.local`, `.config`, and `.cache` are never
allowlisted consumer mutations.

At baseline, after source-bound preparation, after credential handoff, after
the observer child, and immediately before push, the observer must prove the
same consumer CWD, Git top-level, HEAD, and source identity, plus empty
`git status --porcelain` and empty `git clean -ndx`. Any deviation abandons the
consumer before a live fetch. Slow preparation completes before the one normal
push; no arbitrary outer timeout may replace the leaf-certificate deadline.
Online verification remains required before certificate `notAfter` without a
validity relaxation.

## Remaining Hosted Evidence

After the normal gates, the sole remaining action is one separately authorized
v3 fixture commit and normal push. The already prepared same consumer then
immediately acquires and verifies current original bytes online, performs one
authenticated fetch, consumes Finish once, and verifies immediate replay
rejection. A local modeled result never substitutes for that artifact, online
crypto, or authority evidence.