3.7 KiB
Confirmed save-diagnostics preview publication
Gitea release 9
is published, draft false / prerelease true. Its immutable tag/evidence checkpoint
is e144e32e9984477a258759a9dcc75f6e499fc224. Desktop source 0e83157e, reused
server source 715036e, and package documentation ef28f178 retain their
distinct provenance in the verified release record.
This is scoped #46 delivery, not complete OA/SA or the separately owned union.
The new draft's three assets were uploaded without replacing anything, downloaded and matched before publication. Publishing rechecked all three downloads, updated only this new draft, and confirmed exact notes/tag/source, draft false and prerelease true. A separate Gitea MCP read confirms the published release target. Releases 7/8 still have their original targets and published prerelease state; no old tag, release body or asset was modified.
| Asset ID | File | Bytes | SHA256 |
|---|---|---|---|
| 36 | Studio ZIP | 34,191,561 | 8b4e353e075f22350a07794ee47a02cf85725501223299cf367134aa1f5b63b7 |
| 37 | ZIP checksum | 150 | de08984ea2cbaf95b6241ac817f1ad8459a0b863adf7ee9fe51de0834bcd2d54 |
| 38 | VALIDATION.md | 2,930 | de5ecaf07b5a0014318e809cea152c738dfdfc55ff0aa8ed3d7ef78b701df9e4 |
Upload readback, published readback, exact published notes and portable validation retain the full download URLs, identities and source scopes. File identities cover the 12 copied publication records/helpers. The earlier raw packet remains exact and separately inventoried; later publication records are outside that inventory. Independent publication-record review reconciles all copied records with their originals and staged bytes. Its stale contribution-note finding was corrected and rechecked before this delivery checkpoint.
Commands used bundled Python from the recorded environment:
python .local/package46/prepare-release-assets.py
python .local/package46/prepare-release-notes.py
python .local/package46/prepare-fresh-release-assets.py
python .local/package46/prepare-release-assets-ready01.py
python .local/package46/release-assets-ready01.py upload 9 e144e32e9984477a258759a9dcc75f6e499fc224
python .local/package46/release-assets-ready01.py publish 9 e144e32e9984477a258759a9dcc75f6e499fc224
The first preparation failed safely: the input preparation helper had already
created an empty release-assets scaffold, while the asset preparer required a
new directory. No file was overwritten. Root verified that scaffold was empty,
preserved it and the failed helper, then used a new release-assets-ready01
directory with unchanged artifact/clean-source guards. A separate draft was
created but remained unpublished until assets passed.
A parent check mistakenly read JSON display escaping as two actual backslashes in the backend command. The failed checker asserted before any write. A subsequent raw-byte check confirmed exactly one backslash and zero doubled separators in the portable validation. No correction was needed; the originally prepared file was uploaded unchanged. These are preserved tooling assumptions, not product defects or weakened gates.
All runtime/compiler/independent review claims retain their preceding source and environment limits. Publication establishes artifact availability and integrity; it adds no new GUI/REST, Linux, full-suite, clean-machine or complete-release claim.