persona-harness 0.8.0-beta.21 → 0.8.0-beta.23

package/docs/current/README.md

@@ -41,7 +41,7 @@ not become current merely because they remain under `docs/current/`.
   [`docs/releases/package-index.md`](../releases/package-index.md).
 - Release operations and workflow-compatible release notes:
   [`release/README.md`](release/README.md) and
-  [`release/v0.8.0-beta.19-release-notes.md`](release/v0.8.0-beta.19-release-notes.md).
+  [`release/v0.8.0-beta.23-release-notes.md`](release/v0.8.0-beta.23-release-notes.md).
 - P3 integrity roadmap and release hold:
   [`p3-integrity-roadmap.md`](p3-integrity-roadmap.md).
 - P3-2 closure authority candidate:
@@ -118,23 +118,29 @@ not become current merely because they remain under `docs/current/`.
   policy artifact verifier remains read-only/non-authoritative, while local or
   caller-provided staged-package evidence remains
   `artifact-provenance-unavailable`.
-- `0.8.0-beta.1` through `0.8.0-beta.17` are historical staging-only Consumer
+- `0.8.0-beta.1` through `0.8.0-beta.20` are historical staging-only Consumer
   Authority Beta evidence. Beta.16's external observer accepted an exit-zero
   artifact download without an exact nonempty ZIP postcondition, so it
-  provides no reusable beta.19 transport, verification, Finish, consumption, or
-  replay fact. Beta.17's Node20/npm10 registry PUT was authorization-shaped,
-  not a package-absence claim. Beta.18 is immutable staging evidence: its
-  registry version, selected tag, SHA-1/SRI, raw SHA-256, and portable content
-  identity matched frozen canonical facts, but its readback incorrectly required
-  an unsupported registry `gitHead` metadata field. `0.8.0-beta.19` is the current source-preparation
-  candidate. It makes no package, tag, staging mapping,
-  GitHub release, original signed consumer artifact, promotion, Stable/GA, or
-  Finish authority claim. Its pre-fixture gate requires a package-visible
-  observer credential-preflight, separate caller/reusable signer binding,
-  portable canonical package-content identity, and
-  the complete public Java/Spring lifecycle to reach only
-  `trusted-authority-required` in
-  [`release/v0.8.0-beta.19-release-notes.md`](release/v0.8.0-beta.19-release-notes.md).
+  provides no reusable transport, verification, Finish, consumption, or replay
+  fact. Beta.17's Node20/npm10 registry PUT was authorization-shaped, not a
+  package-absence claim. Beta.18 is immutable staging evidence: its registry
+  version, selected tag, SHA-1/SRI, raw SHA-256, and portable content identity
+  matched frozen canonical facts, but its readback incorrectly required an
+  unsupported registry `gitHead` metadata field. `0.8.0-beta.21` is
+  non-reusable temporal final-observer evidence because online crypto and
+  identity bindings completed only after the leaf certificate window expired.
+  `0.8.0-beta.22` is historical non-reusable final-observer evidence: host
+  `gh`/XDG state created an untracked `.local` entry after the final commit.
+  `0.8.0-beta.23` is the current procedure-only source candidate. It makes no
+  package, tag, staging mapping, GitHub release, original signed consumer
+  artifact, promotion, Stable/GA, or Finish authority claim. Its pre-fixture
+  gate requires source-bound bootstrap before one final fixture commit, retention
+  of that same unpushed commit as the installed consumer CWD/HEAD, a
+  package-visible observer credential preflight, separate caller/reusable signer
+  binding, portable canonical package-content identity, and the complete public
+  Java/Spring lifecycle to reach only `trusted-authority-required`, plus v3
+  host-state isolation outside the consumer realpath, in
+  [`release/v0.8.0-beta.23-release-notes.md`](release/v0.8.0-beta.23-release-notes.md).
 - P3-9 permits separately dispatched P2 source, measurement, or report-only
   investigation. The sole product-scope exception is
   [`korean-cli-help-scope-authorization.md`](korean-cli-help-scope-authorization.md)

package/docs/current/canonical-docs-index.md

@@ -57,8 +57,12 @@ current decision inputs.
 | 0.8.0-beta.17 acceptance record | `docs/current/release/consumer-authority-beta17-acceptance.json` | Historical machine-readable source/packed lifecycle, package-root, canonical tar/content identity, bounded command/transport parser preflights, safe ZIP handoff, modeled exact-once Finish/replay, privacy, and one superseded current-version artifact residual. |
 | 0.8.0-beta.18 Consumer Authority Beta | `docs/current/release/v0.8.0-beta.18-release-notes.md` | Historical staging evidence: registry bytes matched canonical facts, but an unsupported registry gitHead predicate blocked workflow readback. |
 | 0.8.0-beta.18 acceptance record | `docs/current/release/consumer-authority-beta18-acceptance.json` | Historical machine-readable source/packed lifecycle and Node20 packer to Node24 publisher contract. |
-| 0.8.0-beta.19 Consumer Authority Beta | `docs/current/release/v0.8.0-beta.19-release-notes.md` | Current source-preparation record for workflow-bound canonical source to registry-byte reconciliation and sanitized failed-readback evidence. |
-| 0.8.0-beta.19 acceptance record | `docs/current/release/consumer-authority-beta19-acceptance.json` | Machine-readable source/packed lifecycle, package-root, canonical publisher, bounded observer plans, and one hosted registry reconciliation residual. |
+| 0.8.0-beta.19 Consumer Authority Beta | `docs/current/release/v0.8.0-beta.19-release-notes.md` | Historical staging evidence; its registry/original artifact checks do not supply current-version authority completion. |
+| 0.8.0-beta.19 acceptance record | `docs/current/release/consumer-authority-beta19-acceptance.json` | Historical machine-readable source/packed lifecycle, package-root, canonical publisher, bounded observer plans, and one superseded hosted residual. |
+| 0.8.0-beta.22 Consumer Authority Beta | `docs/current/release/v0.8.0-beta.22-release-notes.md` | Historical non-reusable procedure evidence: host gh/XDG state created an untracked `.local` entry after the final commit. |
+| 0.8.0-beta.22 acceptance record | `docs/current/release/consumer-authority-beta22-acceptance.json` | Historical machine-readable beta22 procedure record; it changes no product authority behavior. |
+| 0.8.0-beta.23 Consumer Authority Beta | `docs/current/release/v0.8.0-beta.23-release-notes.md` | Current procedure-only candidate: v3 isolates all fifteen host-state roots outside the consumer realpath and verifies clean consumer state after every pre-push stage. |
+| 0.8.0-beta.23 acceptance record | `docs/current/release/consumer-authority-beta23-acceptance.json` | Machine-readable v3 procedure, package, observer, and one hosted residual contract; it changes no product authority behavior. |
 | Consumer Authority Beta lifecycle | `docs/current/release/consumer-authority-beta.md` | Fixed tag-bound staging, exact package readback, original-artifact consumer boundary, and separately approved `next` promotion sequence. |
 | 0.7.0-rc.3 published capsule | `docs/releases/v0.7.0-rc.3/README.md` | Current npm `next` candidate with matching registry gitHead, tag, GitHub prerelease, and workflow provenance. |
 | 0.7.0-rc.2 published capsule | `docs/releases/v0.7.0-rc.2/README.md` | Previous npm `next` candidate with registry gitHead/tag/workflow provenance. |

package/docs/current/docs-inventory.md

@@ -220,7 +220,9 @@ Total indexed files: 336
 | `docs/current/release/v0.8.0-beta.16-release-notes.md` | version-specific release note | v0.8.0-beta.16 | Historical Consumer Authority Beta staging evidence. Its observer accepted an exit-zero API download without proving a nonempty exact ZIP, so it supplies no beta.17 transport or authority evidence. |
 | `docs/current/release/v0.8.0-beta.17-release-notes.md` | version-specific release note | v0.8.0-beta.17 | Historical Consumer Authority Beta source-preparation record. Its canonical tar/provenance observation ended at an authorization-shaped registry response and makes no package-absence, promotion, or Finish authority claim. |
 | `docs/current/release/v0.8.0-beta.18-release-notes.md` | version-specific release note | v0.8.0-beta.18 | Historical immutable staging evidence. Registry bytes matched canonical facts, but an unsupported registry gitHead predicate blocked workflow readback. |
-| `docs/current/release/v0.8.0-beta.19-release-notes.md` | version-specific release note | v0.8.0-beta.19 | Current Consumer Authority Beta source-preparation record for workflow-bound canonical source to registry-byte reconciliation; it makes no live publish, tag, release, promotion, or Finish authority claim. |
+| `docs/current/release/v0.8.0-beta.19-release-notes.md` | version-specific release note | v0.8.0-beta.19 | Historical Consumer Authority Beta staging evidence; it makes no current-version authority, consumption, replay, promotion, or Finish authority claim. |
+| `docs/current/release/v0.8.0-beta.22-release-notes.md` | version-specific release note | v0.8.0-beta.22 | Historical non-reusable procedure evidence: host gh/XDG state created an untracked `.local` entry after the final commit. |
+| `docs/current/release/v0.8.0-beta.23-release-notes.md` | version-specific release note | v0.8.0-beta.23 | Current procedure-only Consumer Authority Beta candidate: v3 isolates all fifteen host-state roots outside the consumer realpath and verifies clean state after every pre-push stage. |
 | `docs/current/release/consumer-authority-beta7-acceptance.json` | machine-readable release contract | v0.8.0-beta.7 | Historical source/packed lifecycle record retained with beta.7 staging evidence; it cannot satisfy beta.10 current-version authority. |
 | `docs/current/release/consumer-authority-beta8-acceptance.json` | machine-readable release contract | v0.8.0-beta.8 | Historical source/packed lifecycle and beta.7 expiry record. The later beta.8 original-artifact discovery failure is recorded by the beta.9 acceptance contract. |
 | `docs/current/release/consumer-authority-beta9-acceptance.json` | machine-readable release contract | v0.8.0-beta.9 | Historical source/packed lifecycle record for beta.8 discovery-to-binding; beta.9's independently verified original artifact and endpoint failure are recorded by the beta.10 acceptance contract. |
@@ -233,7 +235,9 @@ Total indexed files: 336
 | `docs/current/release/consumer-authority-beta16-acceptance.json` | machine-readable release contract | v0.8.0-beta.16 | Historical source/packed public initialization, root-bound exact-tar package proof, canonical no-token gh parser preflight, and modeled authority-backed Finish readiness contract. |
 | `docs/current/release/consumer-authority-beta17-acceptance.json` | machine-readable release contract | v0.8.0-beta.17 | Source/packed public initialization, root-bound exact-tar package proof, canonical no-token command and transport parser preflights, safe external ZIP handoff, and authority-backed Finish readiness contract with modeled exact-once consumption/replay and one future current-version artifact residual. |
 | `docs/current/release/consumer-authority-beta18-acceptance.json` | machine-readable release contract | v0.8.0-beta.18 | Source/packed lifecycle and package-root contract extended with the strict Node20 canonical packer, isolated Node24 publisher, exact canonical-tar dry-run, and one hosted registry PUT/readback residual. |
-| `docs/current/release/consumer-authority-beta19-acceptance.json` | machine-readable release contract | v0.8.0-beta.19 | Source/packed lifecycle and package-root contract extended with workflow-bound canonical source-to-registry-byte reconciliation and sanitized failed-readback evidence. |
+| `docs/current/release/consumer-authority-beta19-acceptance.json` | machine-readable release contract | v0.8.0-beta.19 | Historical source/packed lifecycle and package-root contract extended with workflow-bound canonical source-to-registry-byte reconciliation and sanitized failed-readback evidence. |
+| `docs/current/release/consumer-authority-beta22-acceptance.json` | machine-readable release contract | v0.8.0-beta.22 | Historical procedure-only source/packed observer contract binding the beta22 final-observer record. |
+| `docs/current/release/consumer-authority-beta23-acceptance.json` | machine-readable release contract | v0.8.0-beta.23 | Current v3 source/packed observer contract binding the immutable host-state isolation record, source-bound pre-push commit, and one hosted residual. |
 | `docs/current/release/consumer-authority-beta.md` | operational stable | - | Staging-first Consumer Authority Beta lifecycle boundary with fixed tag/readback, original-artifact consumer verification, and separately approved next promotion. |
 | `docs/current/release/production-integrity-audit.md` | operational stable | - | Fixed protected-main read-only Actions audit contract with sanitized digest-bound durable output; it cannot mutate release state or grant authority. |
 | `docs/current/rule-curation.md` | current compatibility doc | - | Compatibility/current-era doc retained in place; migrate by summary and pointer before moving. |

package/docs/current/release/README.md

@@ -81,33 +81,54 @@ incorrectly required an unsupported registry `gitHead` metadata field.
 `0.8.0-beta.20` is immutable staging-only evidence: live authority fetch reached
 `trusted/unconsumed`, then Finish correctly blocked before consumption because
 the observer had not initialized the same consumer workflow state.
-`0.8.0-beta.21` is the next strict-prerelease source-preparation candidate; it
-has no source-level claim of a tag, publish, channel movement, GitHub release,
-or original signed consumer artifact. Its release contract requires
-package-visible observer credential preflight, separate caller/reusable signer
-binding, and a complete public Java/Spring readiness route whose default Finish
-is blocked only by `trusted-authority-required` before a fixture may be
-authorized. Beta21 binds that readiness to one exact Git-backed consumer
-CWD/HEAD and isolated HOME/store, requires trusted/unconsumed recheck in that
-same consumer before one Finish/replay, and forbids lifecycle reset or consumer
-switch after fetch. The preflights use a host-derived credential only inside its fixed
-read-only GitHub Actions worker; they do not pass that credential to `ph`, npm,
-archive tooling, or the consumer HOME. Its package evidence also starts from the
-exact complete-history bundle, not an ambient working directory: detached
-checkout, Git/manifest/lock/npm-prefix binding, normal prepack, and fresh
-installed CLI identity must all agree before the tarball is eligible for
-independent package review. The beta21 release contract additionally owns
-no-token/no-artifact attestation and artifact transport parser preflights. The
-transport plan binds the caller repository/run/artifact endpoint, exact ZIP
-bytes, and safe members before it hands an original ZIP to the separate reusable
-signer command plan. The package proof invokes plain `npm` from that bound
-detached checkout, never `npm --prefix ... pack`, and uses the exact resulting
-tarball for both source-built and fresh installed consumer contracts. Its release
-handoff keeps the Node20/npm10 canonical packer separate from the isolated
-Node24/npm11 publisher, which dry-runs and then publishes the same canonical
-tarball only. Postpublish reconciliation binds protected workflow source
-preflight to registry version, selected tag, SHA-1/SRI, raw SHA-256, and portable
-content identity; it does not require registry `gitHead`.
+`0.8.0-beta.21` is non-reusable temporal final-observer evidence: its online
+crypto and identity bindings passed only after the leaf certificate window
+expired, so authenticated fetch, Finish consumption, and replay were not run.
+`0.8.0-beta.22` is non-reusable final-observer evidence: host `gh`/XDG state
+created an untracked `.local` entry after the final commit. `0.8.0-beta.23` is
+the next strict-prerelease procedure-only source candidate;
+it has no source-level claim of a tag, publish, channel movement, GitHub
+release, or original signed consumer artifact. Beta23 records the governed v3
+future final-observer procedure without changing product fetch, authority,
+Finish, transport, workflow, or CI behavior.
+
+The beta23 release contract requires package-visible observer credential
+preflight, separate caller/reusable signer binding, and a complete public
+Java/Spring readiness route whose default Finish is blocked only by
+`trusted-authority-required` before a fixture may be authorized. Source-bound
+bootstrap must finish before the final fixture commit. That one commit may
+contain only declared source-bound bootstrap outputs and the immutable reusable
+pin; the same unpushed final fixture commit is retained as the installed
+consumer CWD/HEAD. Later slow preparation may modify only excluded runtime or
+build state. Immediately before its one normal push, the remote parent, CWD,
+Git top-level, HEAD, and source identity must still bind to that final commit.
+No lifecycle reinitialization, consumer switch, or source reset is permitted
+after fetch. It also requires `env -i`, explicit absolute `gh`/Git/Node/npm
+paths, and fifteen external host-state roots outside the consumer realpath.
+At baseline, source-bound preparation, credential handoff, observer child, and
+immediately before push, CWD/Git top-level/HEAD/source identity plus empty
+porcelain and `git clean -ndx` must remain unchanged. `.local`, `.config`, and
+`.cache` are never allowlisted; slow preparation completes before the one push,
+and the certificate validity deadline is non-relaxable.
+
+The preflights use a host-derived credential only inside their fixed read-only
+GitHub Actions worker; they do not pass that credential to `ph`, npm, archive
+tooling, or the consumer HOME. Beta23 retains the no-token/no-artifact
+attestation and artifact transport parser preflights. The transport plan binds
+the caller repository/run/artifact endpoint, exact ZIP bytes, and safe members
+before it hands an original ZIP to the separate reusable signer command plan.
+Its package evidence starts from the exact complete-history bundle, not an
+ambient working directory: detached checkout, Git/manifest/lock/npm-prefix
+binding, normal prepack, and fresh installed CLI identity must all agree before
+the tarball is eligible for independent package review. The package proof uses
+plain `npm` from that bound detached checkout, never `npm --prefix ... pack`,
+and uses the exact resulting tarball for both source-built and fresh installed
+consumer contracts. Its release handoff keeps the Node20/npm10 canonical packer
+separate from the isolated Node24/npm11 publisher, which dry-runs and then
+publishes the same canonical tarball only. Postpublish reconciliation binds
+protected workflow source preflight to registry version, selected tag, SHA-1/SRI,
+raw SHA-256, and portable content identity; it does not require registry
+`gitHead`.
 `0.7.0-rc.2` remains an earlier published `next` record.
 
 The staged-package artifact producer is a controlled future-run source:

package/docs/current/release/consumer-authority-beta.md

@@ -6,17 +6,22 @@ user-scoped consumer authority route; neither one automatically promotes a
 package or makes Finish pass.
 
 `0.8.0-beta.1` through `0.8.0-beta.20` are immutable staging-only evidence.
-Their registry and provenance observations cannot be reused as beta.21
-current-version consumer authority evidence. Beta.16's final observer accepted
+Their registry and provenance observations cannot be reused as current-version
+consumer authority evidence. Beta.16's final observer accepted
 an exit-zero API download without proving a nonempty exact ZIP, so it stopped
 before ZIP validation. Beta.17 created a canonical tarball and provenance but
 its Node20/npm10 registry PUT received an authorization-shaped E404; that is not
 a package-absence claim, and beta.16 remains present in the public registry.
 Beta.18 is immutable staging evidence: its registry bytes matched canonical
 facts, but its postpublish checker incorrectly required an unsupported registry
-`gitHead` metadata field. The active `0.8.0-beta.21` source candidate has no
-package, tag, channel movement, GitHub release, or signed consumer-project
-artifact at source preparation time.
+`gitHead` metadata field. Beta.21 is non-reusable temporal final-observer
+evidence: online crypto and identity bindings completed only after the leaf
+certificate window expired, so fetch, Finish, and replay did not run. The active
+`0.8.0-beta.22` is non-reusable procedure evidence: host `gh`/XDG state created
+an untracked `.local` entry after the final commit. The active
+`0.8.0-beta.23` procedure-only source candidate has no package, tag, channel
+movement, GitHub release, or signed consumer-project artifact at source
+preparation time.
 
 The prior beta candidates are retained as staging-only NO-GO or
 source-preparation evidence: none qualifies for promotion or issue closure
@@ -24,9 +29,10 @@ because it did not complete the full current-version public consumer route.
 Beta.20 reached a live `trusted/unconsumed` fetch but then correctly stopped at
 `workflow-state-uninitialized` because the observer had not prepared the same
 consumer's public lifecycle. That result consumed nothing and is not reusable.
-Beta21 binds the missing immutable same-consumer observer order. It cannot
-inherit beta.16's observer failure, beta.17's registry PUT result, beta.18's
-failed metadata predicate, an earlier lifecycle, or an earlier authority result.
+Beta23 binds the immutable same-consumer observer order, pre-push source
+identity, and v3 host-state isolation procedure. It cannot inherit beta.16's observer failure, beta.17's
+registry PUT result, beta.18's failed metadata predicate, beta.21's expired
+temporal result, an earlier lifecycle, or an earlier authority result.
 
 The consumer must create its own workflow state through public bootstrap and
 report/evidence commands in the exact project that later fetches authority.
@@ -37,6 +43,20 @@ After public initialization the same command must reach only
 artifact then proves one real Finish consumption and immediate replay block
 without standing in for hosted crypto evidence.
 
+For the final public fixture, source-bound bootstrap must complete before the
+final fixture commit. That one commit contains only declared source-bound
+bootstrap outputs and the immutable reusable workflow pin. The same unpushed
+final fixture commit is retained as the installed consumer CWD/HEAD; subsequent
+slow preparation may change only excluded runtime and build state. Immediately
+before the one normal push, the fixture remote parent, CWD, Git top-level, HEAD,
+and source identity must still match the final commit. Every host process uses
+`env -i` with explicit absolute `gh`, Git, Node, and npm paths. All fifteen
+host-state roots are outside the consumer realpath, and the observer verifies
+empty porcelain plus empty `git clean -ndx` after baseline, source-bound
+preparation, credential handoff, observer child, and immediately before push.
+`.local`, `.config`, and `.cache` are never allowlisted. No lifecycle or source
+reinitialization, consumer switch, or state reset is permitted after fetch.
+
 ## Fixed Sequence
 
 1. An approved protected-main source candidate has strict prerelease SemVer
@@ -139,12 +159,12 @@ authority artifact or Finish PASS.
 
 The external-attested fixture must pin the exact current package revision. The
 verifier binds the signed receipt `phVersion` to its installed CLI version, so
-an original artifact from `0.8.0-beta.1` through `0.8.0-beta.20` is a bounded
-binding mismatch or historical-evidence block for `0.8.0-beta.21`; only a future
+an original artifact from `0.8.0-beta.1` through `0.8.0-beta.22` is a bounded
+binding mismatch or historical-evidence block for `0.8.0-beta.23`; only a future
 original signed artifact for the current immutable version can exercise
 enrollment, fetch, explicit consumption, and replay rejection. The complete
 source/packed acceptance contract is the structured
-[`consumer-authority-beta21-acceptance.json`](consumer-authority-beta21-acceptance.json)
+[`consumer-authority-beta23-acceptance.json`](consumer-authority-beta23-acceptance.json)
 record; it names the exact public Java/Spring readiness route, the separate
 caller and reusable certificate identities, the independent observer credential
 and no-token command/transport plan preflights, the immutable same-consumer
@@ -157,7 +177,7 @@ than caller project source. The profile, Gradle descriptors, Git identity,
 reports, and evidence remain bound. This does not relax caller enrollment,
 reusable SHA/SAN, repository, source, run, original-archive, or digest checks.
 
-Before beta.21 package evidence is accepted, the verifier materializes the
+Before beta.23 package evidence is accepted, the verifier materializes the
 exact complete-history bundle in a detached no-local checkout. It binds one
 explicit canonical `refs/heads/...` candidate ref and
 `refs/remotes/origin/main`; the candidate ref must equal the expected candidate
@@ -205,7 +225,7 @@ is not retained.
 
 ## Live Verification Deadline
 
-Before the one natural beta.21 fixture push, an independent observer must prepare
+Before the one natural beta.23 fixture push, an independent observer must prepare
 one exact Git-backed registry consumer CWD/HEAD and one private consumer `HOME`.
 It must first complete the public bootstrap/Gradle/report/evidence/plan route and
 confirm default Finish is blocked only by `trusted-authority-required`; it may