Files
ARCADIA-Studio/harness/experiments/packaged-gui-close-865483b-20260911/README.md
T

20 lines
3.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Packaged Home, Guide and normal close — 865483b
Owner: Codex-ytr83r /root/windows_release_gap_review, 2026-09-11. This archive preserves root's closed native observations for old source `865483b4c66361a01fe0d9e731859220bafb4136`, extracted GUI **BF9C2E618D4A4AC55E6A7EBB3738736659FC35A6465522C7B5AB975238938808**, PID8680/window5702564. The archiver copied/read bytes only; it did not replay UI actions or execute the application, validator, compiler or packaging tools.
## Recorded observations
Root's `packaged-home-guide-close-complete.json` and screenshots96–100 record Home, opening the offline guide, navigating to Scenarios & alternatives with lifetime/Create/Delete guidance, and the bundled water-pressure walkthrough. Screenshot99 is the intermediate Working state; screenshot100 records Source project opened and **94 objects /62 links /1 check**. Root reports no model edit or Save to the packaged example. These are bounded navigation/load observations, not full guide-topic acceptance or complete example semantic validation.
One normal Alt+F4 requested close. `normal-close-observation.json` at20:29:47.760 UTC is the immediate historical observation: the target window was still present. The later complete receipt at20:30:26.352 UTC records a fresh inventory with no target window, an absent PID8680 query, and closed stdout/stderr of zero bytes. This supports eventual normal closure after that single request, without force termination. **No application exit code was captured; do not infer exit0 from absence or empty logs.**
`launch-packaged.json` remains byte-exact, including its original “acceptance pending” text and its then-current target/debug source path. Those describe launch-time evidence, not current acceptance or a current hash of the subsequently rebuilt target/debug executable. The closed completion receipt supersedes pending Home/Guide/close status only within the scope above. Prior child-work, header and contextual workflows retain their separate evidence/limits.
## Package integrity and archive verification
`package-readback.json` records a passed read-only comparison of the complete **559-file** extracted package to its original `extraction-readback.json` hashes and sizes, plus all **558 SHA256SUMS entries**, with zero mismatches. The checksum file itself is checked by the original extraction receipt; exact inventory comparison rejects extra or missing files. `package.json` also matches the original launch receipt. The complete comparison includes the bundled water-pressure source files and establishes their unchanged saved bytes at readback, not an independent model-validation result.
The archive copies **13 payloads / 1,407,055 bytes**: five original JPEGs, three launch/close receipts, two now-closed empty logs, the original extraction receipt and two package metadata/checksum files. No executable, DLL, ZIP, live profile or working model directory is copied. `manifest.json` records each original/copy SHA256 and size; `readback.json` records the passed fresh-process second readback of both originals and copies with an exact inventory check. `archive.py` and `verify-copy.py` are source-only archival procedures.
This is old865/BF9 evidence. It supplies no a57/69DB native acceptance, complete guide/example acceptance, contextual-source or comprehensive Unicode-header acceptance, package publication or full-goal completion. Root owns the checkpoint interpretation and publication. STATE, other documents, source, Git/index, Cargo and WSL/Linux were untouched by this archive task.