62 lines
3.5 KiB
Markdown
62 lines
3.5 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.
|