[ViperJuice]

Summary

• re-cut the 0.7.28 source candidate from origin/main at e6df14de50479877911b01305822f4e03dd7b3b9
• update runtime version metadata, release-facing documentation and the changelog since v0.7.27
• refresh the LEGIBLE version assumption, six v10 roadmap bindings and append-only authority history
• include the FABPUB exact pull-request reconciliation runtime required by dotfiles settlement

This PR is source preparation only. It does not create a tag, publish a package, deploy or install the runtime, or dispatch a release workflow.

Publication waits on owner-gated runtime qualification on ai, including agy requalification.

Out of scope

• agent-harness#1602 is not implemented by this release preparation.
• agent-harness#1606 is not implemented by this release preparation.

Local validation

• built phase_loop_runtime-0.7.28-py3-none-any.whl (SHA-256 19f11431f75fbb3a9bd4bc80839577a9c5730205e07f93a0249432e718b03d8a)
• built phase_loop_runtime-0.7.28.tar.gz (SHA-256 53f094990d269bae96d6b07e09795b52a53cc81837e39138bb3e2f1c0a93140c)
• exact-wheel Gate A clean-room install and both profile-plugin probe seams passed; the full standalone suite was intentionally skipped under the current sprint policy
• targeted release and LEGIBLE pytest: 117 passed, 1 skipped
• jailed-seat qualification entry pytest: 38 passed
• manifest coverage: canonical=61, registered=61, unregistered=0
• entry-document check, documentation audit, lock check, release consistency check and full-history gitleaks scan passed
• 4cbe6869 is an ancestor of the release head, and the wheel RECORD digest for exact_pr_reconciliation.py matches its installed bytes

The PR remains draft pending owner-gated runtime qualification and publication authorization.

Refs agent-harness#1779.