Files
ARCADIA-Studio/harness/reviews/prerelease37-windows-documents-20260924.md
T

36 lines
1.9 KiB
Markdown

# Windows package document admission
Source: `897d9f049406d5be597543eb0a6755b796259302`. Parent Windows verification
on 2026-09-24, with Python 3.12.14. This is documentation/example admission only;
no Cargo build, package creation or native execution was performed here.
From the clean candidate checkout, ran:
```text
python -B scripts/package-artifacts.py docs --repository . --platform windows
```
PASS: the helper resolved the package's local documentation links and selected
66 files, totaling 1,449,245 raw bytes. Each selected file was compared to its
exact source Git blob: all 66 were byte-identical, including the virtual archive
`README.md` supplied by `scripts/package-readme.md`. Each path's filtered Git
hash also matched its tracked identity, and the checkout remained clean.
The [complete receipt](prerelease37-windows-documents-20260924.json) records
archive/source path mapping, Git object identities, lengths and raw SHA-256.
Applicability to successor `8ddfadf440b5c208b1adb6b211a97ba0c99cff04`:
Git comparison confirms no change to these package inputs or their selection
script; only an unrelated test import and harness records changed. The original
receipt remains bound to its actual measured `897d9f04` checkout.
Reuse at `715036e132677dd2bc2fb37ed316d93dc9987aec`: compared all 66 recorded
source paths and `scripts/package-artifacts.py` against the original receipt's
source; no changes. The State picker fixture/container correction and harness
records do not change package documentation. This comparison does not relabel
the original receipt or establish runtime acceptance.
The Windows closure intentionally contains linked platform reference documents
and deployment recipes. Reading those files is not a Linux build or verification.
The final package still needs its own closure/inventory readback and native
acceptance; this receipt does not establish binary/source correspondence.