Record scalar review correction checks and frozen platform binaries

This commit is contained in:
2026-09-06 06:32:45 +03:00
parent e7fa061e23
commit 767634aea5
+68
View File
@@ -88,3 +88,71 @@ The directory also contains `SHA256.txt`. No desktop process was launched. The
build target is idle and returned to the lead. Linux integrated checks, native
semantic acceptance, independent scalar-review follow-ups and the structured
semantic desktop milestone remain separate required work.
## Scalar review correction integrated on Windows and Linux
The lead's complete Linux baseline run at `d114a5d` is confirmed from the logs in
`D:/CodexBuilds/Capella2-data-linux-target`: **721 passed, 0 failed, 1 intentionally
ignored** inheritance probe, across 39 summaries. Strict workspace all-target
Clippy and the optimized workspace build also completed successfully. The source
logs are `semantic-workspace-test.log`, `semantic-workspace-clippy.log` and
`semantic-release-build.log`. These were root-run checks, followed by this task's
log inspection; they are not newly rerun workspace checks after the scalar fix.
Cherry-picked the reviewed scalar correction `5a51a7572e8edee6b0bb85fe6aded3a8380e0edd`
as `e7fa061`. The affected forms and semantic files merged automatically, preserving
DATA's recursive browser and direct behavior changes. The Linux checkout fetched
DATA locally and fast-forwarded to the exact same commit. No core or server code
changed. The correction preserves unfinished scoped inputs during structural edits,
uses the combined review candidate for dependent controls, and disambiguates keyed
fact headings with qualified paths and identity. See `release-semantic-gui.md`.
Post-fix verification passed on both platforms: **322 desktop tests passed, zero
failed or ignored**; strict all-target desktop Clippy; whole-workspace formatting;
and optimized desktop builds. Windows build took 1m38s; Linux took 1m33s. The five
additional test functions and expanded cases exercise scoped draft retention,
dependent type/storage/mechanism controls, exact source/history and qualified
fact headings alongside all existing desktop tests.
Commands used on Windows from DATA, with the existing assigned target:
```powershell
$env:CARGO_TARGET_DIR='D:/CodexBuilds/Capella2-data-target'
cargo test --locked --offline -p oa-desktop
cargo clippy --locked --offline -p oa-desktop --all-targets -- -D warnings
cargo fmt --all -- --check
cargo build --locked --offline -p oa-desktop --release
```
Matching commands inside Ubuntu 24.04 WSL:
```sh
cd /mnt/d/CodexBuilds/Capella2-data-linux-review
export PATH=/home/sorokinoleg/.cache/arcadia/rust/bin:$PATH
export CARGO_TARGET_DIR=/mnt/d/CodexBuilds/Capella2-data-linux-target
cargo test --locked --offline --config target/linux-cargo.toml -p oa-desktop
cargo clippy --locked --offline --config target/linux-cargo.toml -p oa-desktop --all-targets -- -D warnings
cargo fmt --all -- --check
cargo build --locked --offline --config target/linux-cargo.toml -p oa-desktop --release
```
Logs share the names `scalar-fix-desktop-test.log`,
`scalar-fix-desktop-clippy.log`, `scalar-fix-fmt.log` and
`scalar-fix-desktop-build.log`. Windows logs are in the target's
`semantic-integration` directory; Linux logs are directly in its assigned target.
Both command sessions completed with exit status 0.
Separate native trial directories under
`D:/CodexBuilds/Capella2-release1-01a06e2e` now contain frozen `e7fa061` executables:
- `ui-semantic-windows-e7fa061/arcadia-studio.exe` SHA256
`3E46F001711948FB60E3F65C49810DF5C177228D5DFA609ED9DF3F8C96081F34`
- `ui-semantic-linux-e7fa061/arcadia-studio` SHA256
`94C39037AF47C95FA6EE6515C3EB3B4FFBAC59730286E6EDB5F14B16E7874826`
Each has a `verification.json` manifest. Both frozen hashes equal their build
outputs, and Linux executable access was verified without launching it. Both
checkouts and build targets are returned to the lead. No native input was used,
and no STATE, TASK_LEDGER, README or other native ledger was staged by this task.
Scalar native acceptance and the remaining structured review milestone still
belong to the lead's release plan.