66 lines
3.8 KiB
Markdown
66 lines
3.8 KiB
Markdown
# Packaged authoring GUI acceptance — 2026-09-11
|
|
|
|
Codex-9e8r6t `/root`, Windows. Bounded clean-package verification for
|
|
`0.2.0-preview.authoring.20260911`; the full OA/SA release remains unfinished.
|
|
|
|
## Artifact and environment
|
|
|
|
ZIP SHA256 `664F30B6217689ACA1492EB263B3D15777067D732FA890EEB028F435209DADFA`,
|
|
32,618,262 bytes, 559 files. A fresh extraction independently verified every
|
|
558 manifest entry and the exact physical inventory including SHA256SUMS.txt.
|
|
Desktop D4D9C2BD…B20C31 and libunwind F45604A1…0E1AE7D4 match the package and
|
|
earlier native authoring artifacts. The source/provenance/notice boundary is in
|
|
`release-authoring-prerelease-preparation-20260911.md`.
|
|
|
|
The first launch harness stopped before spawning any process: Python's copied
|
|
Windows environment had uppercase SYSTEMROOT, while the harness read SystemRoot.
|
|
That extracted directory is preserved. The corrected second attempt uses a new
|
|
directory and reads the existing uppercase key. No application or package file
|
|
was changed to correct this harness error.
|
|
|
|
Trial `.local/authoring-prerelease-gui-20260911-v2/` records the exact launch.
|
|
PATH contains only the extracted package, C:\Windows\System32 and C:\Windows.
|
|
LOCALAPPDATA and APPDATA point to fresh private profile directories. The desktop
|
|
was launched from the extracted package directory as PID10800, native window984068.
|
|
Loaded module inspection found only the packaged executable/libunwind outside
|
|
C:\Windows; no compiler, Cargo target or development runtime path was loaded.
|
|
This is a clean application runtime/profile on the current Windows machine,
|
|
not a claim of a fresh operating-system installation.
|
|
|
|
## Native observations
|
|
|
|
- Fresh Home showed Untitled mission, no recent models, and usable example/help
|
|
actions. The initial occluded screenshot was not used for acceptance; explicit
|
|
activation exposed the packaged window before input.
|
|
- Open water-pressure walkthrough loaded the packaged multi-file example:
|
|
94 objects, 62 links and one model check. OA architecture showed allocated
|
|
activities nested inside Control room and Field technician, with exchanges.
|
|
- Ordinary Ctrl+S completed. All 558 checksum entries still match and the exact
|
|
559-file package inventory remains unchanged, including every example source.
|
|
- Switching to System Analysis rendered the service boundary, allocated functions,
|
|
SystemActor and ports. Behavior & scenarios rendered the pressure-supervision
|
|
state machine and its editing toolbar.
|
|
- Engineering guide opened its bundled content and scenario-authoring topic.
|
|
- Alt+F4 closed the clean-package instance; a fresh window/process inventory
|
|
confirmed it had exited, while the separate native scenario trial remained open.
|
|
|
|
Screenshots, launch metadata, module inventory, post-Save exact comparison and
|
|
stdout/stderr are retained in the trial directory. No runtime error was present
|
|
in stderr during these checks. The current host's wider/minimum named creation,
|
|
source parity, Undo/Redo and recovery checks are separately tied to the same
|
|
D4D9 executable; they were not all repeated as package smoke tests.
|
|
|
|
## Limits
|
|
|
|
This milestone uses development-profile Windows x64 binaries. It includes the
|
|
desktop, server, examples, offline documentation and dependency notices. It does
|
|
not include the newer contextual-source or reference-chooser work, B4 lifetime
|
|
changes, the separately committed CLI executable, completed executable analysis/
|
|
quantity/library semantics, or a verified Linux binary. Some long labels and
|
|
state-transition text remain crowded, and scenario forms can retain a prior
|
|
scroll offset. Those limitations remain visible in the release notes.
|
|
|
|
Independent package/server/restart verification is recorded separately. This
|
|
bounded acceptance supports publishing a working prerelease, not full release
|
|
completion or optimized-build acceptance.
|