105 lines
6.2 KiB
Markdown
105 lines
6.2 KiB
Markdown
# Integrated checks — 2026-09-10
|
||
|
||
Root identity: Codex-9e8r6t. These are intermediate results, not release acceptance.
|
||
|
||
## First merged desktop artifact
|
||
|
||
Source: merge `057eddd` plus the checkpoint autofocus patch later committed in
|
||
`31b7dc3`. The Rust sources were frozen throughout compilation. After the 13
|
||
checkpoint tests passed, root copied the built test executable and matching
|
||
libunwind into `.local/integration-20260910/tests-057eddd/`; later source edits
|
||
could not change this running artifact. SHA256:
|
||
`D504C59BC2A5853F4FBE54A9DFA841DA0AC8DD2475342E45A91DBAA6533372B4`.
|
||
The exact additional source patch and execution metadata are retained there.
|
||
|
||
Full inventory execution ran from 18:21:36 to 18:29:26 UTC, 469.21 test seconds,
|
||
and exited 101: **615 passed, 3 failed, 0 ignored**. Failures:
|
||
|
||
- Scenario return after rename/deletion/retarget: selected identity differed
|
||
from the asserted caller/use or still-open scenario. The layout worker found
|
||
that generic retarget commands can leave a cross-owner selection, and a
|
||
same-ID selection shortcut can skip changing the active scenario on successful
|
||
Back. A narrow correction and stronger active-scenario assertion are in the
|
||
next candidate; they have not yet passed.
|
||
- Both exhaustive stored-history choice and exact-string tests failed with
|
||
UUID parsing of `NotApplicable`. Root found `seed()` using permissive shape
|
||
matching to identify that enum, so nullable UUID/string branches receive the
|
||
literal instead of null. The other host's forms owner is correcting explicit
|
||
enum admission while preserving raw invalid-input editing.
|
||
|
||
This artifact predates nullable constructor-cache fix `b6b76ef`, merged locally
|
||
in `a70de55`, and the later scenario workspace. That cache fix is distinct from
|
||
the seed defect. Gitea issue 1 comments 68–69 carry the failures and diagnosis.
|
||
No assertions were weakened or failed checks reported as acceptance.
|
||
|
||
## Specification check
|
||
|
||
On merged source, `semantic_schema.py --check --validate` passed **72 fixtures**,
|
||
**204 schemas**, **14 families** and **90 scalar leaves** using the retained
|
||
local jsonschema dependency directory. The first invocation with the bundled
|
||
Python alone lacked jsonschema; setting its task-local PYTHONPATH resolved that
|
||
environment issue without changing the script or dependencies.
|
||
|
||
Docutils 0.22.2 rendered both `docs/language.rst` and `docs/api.rst` under
|
||
`--strict`, with no warnings. API HTML was byte-identical. Language HTML was
|
||
identical after newline normalization: the Git checkout has LF and the Windows
|
||
renderer produced 2,776 CRLF lines. The rendered files remain under the local
|
||
integration directory. This establishes specification/render synchronization,
|
||
not full graphical/textual/REST runtime parity.
|
||
|
||
## Packaging integration
|
||
|
||
Commit `b98f135` includes the independently reviewed packaging changes. Root
|
||
explicitly renormalized the two Fira notices after applying their exact `-text`
|
||
attributes. The three upstream notice exceptions retain intentional original
|
||
whitespace; all other staged files passed the whitespace check. Raw and staged
|
||
bytes of all three checksum-bound notices were independently compared exactly
|
||
in `.local/packaging-20260910/root-staged-verbatim-notices.json`. The author's
|
||
separate alternate-index check covers all 25 referenced notice files through
|
||
checkout. Native Linux, a real Linux desktop/server archive, container execution
|
||
and final optimized packages remain open gates. See the packaging reports for
|
||
the explicit synthetic/full-graph versus real-Windows evidence distinction.
|
||
|
||
## Corrected immutable desktop suite — terminal result
|
||
|
||
The next combined executable, retained at
|
||
`.local/scenario-workspace-20260910/tests-81668f9/arcadia-studio-tests.exe`,
|
||
SHA256 `FF5999466032E4FBDD615969E349720EC6B29A5945F7E3A57CCF976D8A2736E7`,
|
||
completed **631 passed,0 failed,0 ignored** in408.18 test seconds. The wrapper
|
||
started2026-09-10T19:01:51.5576902Z and ended19:08:41.0622262Z,409.3798404
|
||
wall seconds, exit0. Full log and result JSON are siblings. It includes both
|
||
nullable-history fixes and the integrated scenario workspace/Back/OpenUse guards
|
||
committed in3978bbe. The previous three failures are resolved by tested source
|
||
changes, not by relaxed assertions. The creation files present in the input
|
||
manifest were not yet declared and are not covered by this executable.
|
||
|
||
Independent review then found retained Sensor state across same-size scenario
|
||
owner/document changes. The two-line key correction and real mounted regression
|
||
were committed as `d114a271c5ecffcd7960fb8aa44d45989c10dc33`; affected scenario
|
||
tests passed53/53 (579filtered), logged in `scenario-sensor-tests.log` and its
|
||
status JSON. This correction is later than the631 executable and candidate3
|
||
GUI, so those earlier artifacts must not be relabeled as covering it.
|
||
|
||
## Named creation and current combined suite — 2026-09-11
|
||
|
||
The creation integration passed20 focused tests,166 behavior tests and13
|
||
checkpoint tests before an additional reviewed owner-ancestry correction.
|
||
After that correction and guide synchronization, final creation21/21 and guide3/3
|
||
passed. Root then ran the complete immutable executable at
|
||
`.local/behavior-creation-20260911/tests-final/arcadia-studio-tests.exe`, SHA256
|
||
`864B0FE89D0DC33F19D8414531501CB4D9DC5E7527B925A16E74ACA0E1197E86`.
|
||
Result: **653 passed,0 failed,0 ignored**,362.83 test seconds; wrapper
|
||
08:41:23.6872357Z–08:47:26.6151440Z,362.9279083s,exit0. Matching source-input
|
||
manifest, exact libunwind DLL, full log and result JSON are siblings.
|
||
|
||
Strict desktop Clippy/all-targets/-Dwarnings subsequently passed after converting
|
||
one nested conditional in `forms/history_fields.rs` to an equivalent let-chain;
|
||
workspace fmt/check also passed. This is the only production change after the
|
||
full653 snapshot. Affected history **63/63** passed15.67s, and the matching GUI
|
||
rebuilt successfully19.86s. The original creation GUI40CF05…3F23 matched the
|
||
full653 source, but was not natively used. Current native stage is
|
||
`gui-verified/arcadia-studio.exe`,111163904bytes,SHA256
|
||
`D4D9C2BD937E301FF1009D7CB93A34EE5AA6DFC837FF7E87D468C85371B20C31`.
|
||
Its manifest verifies that the only changed input versus tests-final is that
|
||
history let-chain. Native creation and broader release acceptance remain pending.
|