Prepare Linux delivery and correct lifecycle rendering build types

This commit is contained in:
2026-09-11 07:53:42 -07:00
parent cb611a71df
commit 29084050a7
41 changed files with 1120 additions and 25 deletions
+9 -3
View File
@@ -50,6 +50,11 @@ the owner's clarification allows domain constraints rather than arbitrary moveme
- The separate baseline-context experiment passed218 assertions; explicit
one-level overrides reduce repeated stable assumptions while complete frozen
definition environments remain necessary. Proposed syntax is not source7.
- After the user's virtualization/reboot change, supported Ubuntu26.04 install
completed exit0 and a real x86_64 WSL2 kernel shell completed. Later VM startups
timed out before apt. This establishes initial guest execution, not reliable
Linux builds or GUI acceptance; exact outcomes and next controlled trial are
in the [WSL record](release-wsl-postboot-ytr83r-20260911.md).
## Assumptions and unresolved questions
@@ -61,9 +66,10 @@ the owner's clarification allows domain constraints rather than arbitrary moveme
- Pinned package provenance must be distinguished from checked type compatibility;
unchanged quantity kinds cannot become incompatible merely through cosmetic
repackaging without a deliberate policy. Energy and Torque remain distinct.
- Which supported environment will complete current Linux GUI/service/package
execution remains a release question. Old failed or denied experiments do not
establish a current successful environment.
- Ubuntu26.04/WSL2 is the current supported Linux route; reliable repeat startup,
guest toolchain/dependencies and GUI/service/package execution remain open.
Initial shell success does not erase later startup timeouts. Old QEMU work is
retained as history, not the next route to repeat.
- Large-model human/AI task usability, cross-file refactoring, actual chooser
latency/keyboard/minimum geometry and complete native lifecycle behavior remain
to be measured. Parser admission or a widget experiment is insufficient.