V1-RELEASE-PUBLICATION.md markdown
94 lines 5.8 KB
Raw
sha256:f88ec0083b3bcac6a4b7b99c8cc196194ef376aab2c4f2f63e8dfe26256ac6b7 docs: reconcile v1 prerelease publication and operating guides Human 7 days ago

Bounded v1 prerelease publication — completed

v1.0.0-rc.1 is published. GitHub release ID 408458432, published 2026-10-10T00:36:33Z, is a prerelease and is not Latest. At final publication verification, Latest remained v0.1.0, ID 353819945. This completes the authorized prerelease publication; it does not declare stable or complete-product readiness.

The owner authorized the exact five-asset prerelease, and publication is complete. The public release and published manifest identify the result. Owner statements, draft responses and independent download logs remain retained operator records, not public attachments. The historical approved proposal remains preserved at SHA-256 1c23c340f70ce816cce0b4f62dab9d9b509b1cd6926c7d698127ff9ef59da61d; its asset inventory digest is 88add045950c568d035aefb0fe43786f19ea4b9a25167d1870160c929c04b4c9. This public closeout summarizes those records; it does not change their bytes.

Exact published identity

The lightweight tag refs/tags/v1.0.0-rc.1 points directly to accepted GitHub commit 293e79eb96dc9b94b76fa28ffad5e9e0a6e85b30, tree 735b2eb9248148e5c11d377fa79fb1f4dc11b75f. It was created without force after fresh checks established the tag and release were absent. The actual mirror remains 9c9db93b47ceabd9a021a1d0679cb696d65cc6c2, preserving both original parent histories. Frozen recovery Git remains 32254cd939885d9d6f40634997ea5b9c37ea776c.

Accepted Muse remains the recorded source revision sha256:106ef9e12cca7f3be3ffb2a6bd3abfa76f032dce453c9e5010d732a8d86f2e14, snapshot sha256:36037a7bad29f82f50c7ea6442672dc5df306278859119da5c1e393fead3c0aa. No Muse operation was needed for this tag/release step, and no source revision or local isolated Muse ref was advanced.

Executed sequence and verification

  1. Checked the exact proposal and five local assets, accepted tree, main/mirror/ feature/artifact refs, artifact variable, absent tag/release and prior Latest.
  2. Created and read back the exact lightweight tag.
  3. Created draft release 408458432 with prerelease enabled and latest disabled; uploaded exactly the five approved assets and used the exact notes as its body.
  4. Downloaded all five draft attachments independently and verified every byte count and SHA-256. Verified draft settings, release body and tag target.
  5. Published that same verified draft under the existing owner authorization.
  6. Downloaded all five published attachments again and verified their sizes and hashes, exact body, tag target, unchanged branch heads and unchanged Latest.
Published attachment Asset ID Bytes SHA-256
overseer-kit-1.0.0-rc.1-source.tar.gz 626585165 1,764,495 c82768a175d94fa83ccce8b73cac74de85a08932f690a0e8ac673c5de44a5b95
RELEASE-NOTES.md 626585166 5,529 519ea2dca83edcb7f9c25f72ee6e8a65d729bd09b2023a322319ca0e1e7b70d7
INSTALL-AND-ROLLBACK.md 626585168 10,566 117e77acc94a27ca02af2901e78b1e540d1d31385af9cd7ebe5fbfe755579383
release-manifest.json 626585170 2,838 558f616d5709d64e9628982bab9eda547fccd7e74d10aa388d69449b742a7e11
SHA256SUMS 626585167 365 4e4801341dd6f778a255eb2d11af77e49e5821a136b75c225bcdb74f3a622dd9

The source archive retains all 861 accepted files and ten executable modes; companion guidance remains separate from the tagged source. The three retained hosted runs each passed 156 / 156 / 289 tests, with zero reported failures, errors or skips. No unresolved supported-test failure remains. No unchanged suite or closed review was repeated, and no workflow was manually dispatched.

The first read-only repository API request used a trailing slash and returned 404. Correcting that local URL construction completed preflight before any remote write. No candidate, guard, pin or destination changed. All write stages completed and were read back; no partial publication remains unresolved.

Preserved state and remaining work

Main, mirror, recovery feature and artifact branch remain at their approved heads. The recovery checkout, original refs/edits, isolated Muse feature/main and clean held release 06f988e5a078ede81c9dc664520833980a9a19a3 remain preserved. The old held release was not published. Recovery pins and the existing immutable wheel URL at artifact commit bff17390675358b764d43f31f71233ed11a673b0 are unchanged; the wheel/source ZIP were linked, not re-uploaded or replaced.

Declared prerelease limits remain visible: native rc5 clone omitted 19 empty directories while all 861 file bytes matched; Muse provenance is a labelled recovery build rather than an upstream release; historical source guidance is superseded by the attached guide; source version still reports 1.0.0 under the rc.1 tag/manifest. Permanent Git-only operation and explicit Muse adoption remain intact. No deployment, consumer access, production trust reset, automatic hook or OCI operation was performed.

The later documentation closeout is a separate docs/v1-publication-closeout proposal. It was not included in the published tag or archive and has no source revision, commit or PR from this local planning action. Its own reviewed Muse source and GitHub PR must preserve the rc.1 tag and all five asset bytes. Permanent Git-only operation and explicit Muse adoption remain unchanged.

Public evidence and deliberate replacements for local log references are listed in the evidence index. The unchanged release notes and companion guide are copied from the published attachments; their pre-publication conditional wording is historical.

File History 1 commit
sha256:f88ec0083b3bcac6a4b7b99c8cc196194ef376aab2c4f2f63e8dfe26256ac6b7 docs: reconcile v1 prerelease publication and operating guides Human 7 days ago