RC8: integrate certified #292 runtime recovery fixes

[Jumpstile]

Purpose

Integrate the guarded-ARCADE-certified RC8 #292 candidate into main.

Certified source identity

• Head branch: review/rc8-package-runtime-ux-fixes
• Certified exact SHA: 92f17207ddb30cd0b0fc75cb346453d20613f920
• ARCADE FINAL STATUS: CERTIFIED
• Harness exit code: 0
• Run identity: 0dc82fce3a0641a894354811bd0e02c4
• IdentityValid: true
• RefMutationDetected: false
• Applicable checks: 9/9
• Pester: 1,658 total; 1,656 passed; 0 failed; 2 skipped
• Sealed run SHA-256: 43ce860bf1a6d887ddc050292f2b8e71d26b5ab718fedc8460882bc426b17bc4

Why this PR is required now

The certified SHA currently has no GitHub check runs because CI runs on pushes to main or pull requests targeting main / the RC8 review branch. Opening this PR against main should provide the required exact-head-SHA CI evidence without changing the certified commit.

Release boundary

This PR does not authorize publication. Before merge/release disposition:

1. Exact-head-SHA CI/checks must pass.
2. Independent integration review must pass.
3. Release-blocking documentation and wiki freshness gate #290 live documentation/wiki freshness audit must be completed and recorded where required.
4. After integration, package must be built and validated from the controlled accepted source identity, with ZIP SHA-256 / Release Integrity evidence.
5. Tag/draft release and publication require explicit authorization.

No package, tag, release, publication, wiki update, or Scripts mirror is performed by opening this PR.

Closes/relates to #292; keep #292 open until its remaining package-identity/release bookkeeping is satisfied.

[Jumpstile]

Independent adversarial review from Oh My Pi recorded as HOLD. Source identity matched the certified SHA and no certified-head mismatch was found. Integration remains blocked pending: (1) exact-head CI completion, (2) release-gate acceptance of this review, (3) decision on whether PR #295/#294 governance cleanup is part of the accepted RC8 source, (4) #290 live documentation/wiki freshness completion, and (5) RC8 identity/version transition plus final package/release integrity evidence. Exact-head CI run 32787088125 has since completed successfully; that specific blocker is now resolved. Do not merge or package until the remaining blockers are explicitly dispositioned.

[Jumpstile]

Release-gate disposition after Oh My Pi adversarial review: HOLD

The independent adversarial review is accepted into the gate record. Source identity for the current PR head passed: 92f17207ddb30cd0b0fc75cb346453d20613f920 remains the certified head and no source-mutation mismatch was found.

One blocker has since cleared: exact-head CI run 32787088125 completed successfully for 92f17207....

Remaining blockers before integration/release:

1. Decide the final accepted RC8 source set. PR docs: fix TPM #294 release checklist authority pointer #295 / Audit and reconcile TPM agent policies and procedures #294 governance cleanup is still open and contains the operational Release-blocking documentation and wiki freshness gate #290 freshness procedure.
2. Complete Release-blocking documentation and wiki freshness gate #290 live documentation/wiki freshness work, including affected behavior pages and recorded audit evidence.
3. Perform an explicit RC8 identity/version transition; current certified source still identifies itself as RC7. Do not package an RC8 artifact from RC7-identified source.
4. Establish one final integration candidate containing all required RC8 source/doc/governance changes, then run guarded certification against that final exact SHA.
5. Only after final source acceptance may packaging/release-integrity evidence be created (ZIP SHA-256, downloaded-asset verification, tag target, draft release, publication, Scripts mirror).

Release-gate decision: do not merge PR #298 yet. Rather than create another intermediate SHA and recertify repeatedly, assemble the final RC8 integration candidate once, then certify that final source.

No package, tag, release, publication, wiki update, or Scripts mirror is authorized by this disposition.

[Jumpstile]

Desktop reviewer integration review: PASS; overall RC8 release gate remains HOLD

Desktop reviewer independently verified the current PR #298 integration state at exact head SHA 92f17207ddb30cd0b0fc75cb346453d20613f920.

Passes

• Desktop checkout root: C:/REPOS/teknoparrot-manager
• Branch: review/rc8-package-runtime-ux-fixes
• Local/remote/head SHA: exact match
• Base: main at 0f3111b2...
• Worktree: clean
• PR: open, non-draft, mergeable/clean
• Scope: exactly the three intended commits (b64b00f2..., 8be84c09..., 92f17207...)
• 33 changed files remain within runtime recovery, certification harness/tests, governance docs, and CI configuration
• No package/ZIP/wiki/generated release artifact/Scripts mirror introduced
• git diff --check: clean
• Exact-head CI run 32787088125: success
• Quality gates job 97621103253: success
• Pester in CI: 680 passed, 0 failed, 0 skipped
• Attribution run 32787088010: success
• No review comments or unresolved threads

Disposition

The integration review itself passes.

However, overall RC8 merge/release disposition remains HOLD because #290 live documentation/wiki freshness remains incomplete, and the accepted Oh My Pi adversarial review identified additional release-phase blockers that still require explicit disposition before final RC8 source/package acceptance (notably final RC8 identity/version transition and final source-set decision including #295/#294 governance cleanup).

Do not merge/package/tag/release/publish/update wiki/mirror Scripts yet.

[Jumpstile]

Round ownership change: Oh My Pi implementing final RC8 remediation

For this round, the implementation/remediation role is explicitly assigned to Oh My Pi, not Desktop reviewer.

Desktop reviewer's completed PR #298 integration review remains valid evidence for the current certified head. Arcade reviewer remains certification-only and should stay idle until a new final RC8 integration candidate exists.

Oh My Pi is authorized this round to assemble the final RC8 candidate on a new branch from current main, reconciling:

• PR RC8: integrate certified #292 runtime recovery fixes #298 certified runtime/harness work (92f17207ddb30cd0b0fc75cb346453d20613f920)
• accepted PR docs: fix TPM #294 release checklist authority pointer #295/Audit and reconcile TPM agent policies and procedures #294 governance cleanup (888b5467cdf971aa3495951cbffe043843acd806)
• RC8 identity/version transition
• source-controlled Release-blocking documentation and wiki freshness gate #290 documentation freshness changes

Do not merge #298 in place and do not mutate the already-certified branch while claiming its certification still applies. Produce a new exact candidate SHA, validate it, and report all changed files/conflict resolutions. Live wiki updates, packaging, tagging, release publication, and Scripts mirror remain unauthorized until the new candidate clears review, #290, CI, and guarded ARCADE certification.