sorokin.oleg.edu/ARCADIA-Studio
1
0
Fork 0
Code Issues 37 Pull Requests 2 Packages Projects Releases 9 Wiki Activity

Record corrected Windows diagnostic replay and final gates

Browse Source
This commit is contained in:
sorokin.oleg.edu
2026-09-13 02:32:46 -07:00
parent 9fd76aef3a
commit 32368713ef
156 changed files with 20130 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files
harness/experiments/text-diagnostics-20260913/README.md
+36 -8
View File
@@ -1,6 +1,6 @@
# Text diagnostic evidence, 2026-09-13
This archive preserves CPU tests, source captures, reviews, failed experiments and Windows dependency-notice checks for the diagnostic underline/hover candidate. It does not establish native GUI, packaged runtime or release acceptance. Publication remains the integration/release owner's responsibility.
This archive preserves CPU tests, source captures, reviews, failed experiments and Windows dependency-notice checks for the diagnostic underline/hover candidate. It includes a bounded corrected Windows native trial with explicit parent acceptance and independent stored-image review; it does not establish integrated, packaged runtime or release acceptance. Publication remains the integration/release owner's responsibility.
## Verify without executing the historical tools
@@ -49,7 +49,7 @@ The passing Clippy run's input-manifest SHA-256 is `1483d0d67756ee6c6b4dff640150
The [final source-delta review](reviews/final-source-delta-review.md) verifies the only two changes from the optimized/manual evidence: an equivalent nested-guard collapse and seven equivalent range-slice arguments. It supports reuse of the prior geometry/manual/performance evidence without claiming final-byte performance was remeasured. Its statement that the final desktop/CLI run was still pending is preserved as historical context; the later receipt supplies the result above. Its native-recorder section is static review; the helper is now archived under `native-preparation`, and neither the helper nor that review establishes native acceptance.
The closed original Windows build and initial native trial are included below. The trial confirms a correct visible underline and tooltip box whose body/footer text stayed blank. This is blocking native negative evidence, not acceptance. A subsequent ownership correction and its closed gates are now captured separately; the corrected build and strict Clippy attempts failed on disk-full conditions, so corrected native acceptance remains pending. No packaged result or current-source equivalence is implied after a captured candidate changes.
The closed original Windows build and initial native trial are included below. The trial confirms a correct visible underline and tooltip box whose body/footer text stayed blank. This is blocking native negative evidence, not acceptance. A subsequent ownership correction first encountered disk-full build/lint failures; its canonical formatting, strict Clippy, full tests, build and saved CLI oracle have now passed in separately captured runs. Corrected native acceptance remains pending. No packaged result or current-source equivalence is implied after a captured candidate changes.
## Closed build and saved CLI oracles
@@ -96,17 +96,23 @@ All five runs below bind one new 604-input capture: manifest SHA-256 `49e02d011f
| windows-build-final-2 | Build exit 101: `rustc-LLVM ERROR: IO failure on output stream: No space left on device` |
| strict-clippy-4 | Strict Clippy exit 101: query-cache write failed with Windows disk-full error 112 |
The last two rows are infrastructure failures, not successful corrected binary or strict-lint evidence. No successful corrected development build, corrected native trial or release is claimed. The prior successful build and original native failure stay bound to their original capture.
The last two rows are infrastructure failures, not successful corrected binary or strict-lint evidence. Subsequent successful canonical retries appear below; they do not erase the failures. No corrected native trial or release acceptance is claimed. The original build and native failure stay bound to their original capture.
The [ZIP reclamation receipt](resource-recovery/source-zip-reclaim-1.json) records removal of eleven duplicate private gate ZIPs after exact comparison with the already archived copies, reclaiming 26,121,904 bytes. Literal original and retained paths are preserved. This archive remains self-contained: verification resolves retained captures and never attempts to read or recreate the missing private ZIPs. Restore a retained copy to its exact original path only if later authorized to execute a historical path-based helper; no restoration was performed here.
Parent reports that automatic review rejected a proposed old-cache deletion before execution; no cache deletion followed. The separately archived read-only cache audit is not proof of deletion. The actual [compression receipt](resource-recovery/older-cache-compression-result.json) records lossless NTFS compression of 1,040 files in two older cache roots, both commands exiting 0 and all file bytes unchanged. Its [before inventory](resource-recovery/older-cache-compression-before.json) has exact per-file hashes and a logical total of 1,381,604,275 bytes. Archive verification checks receipt counts, totals and containment, not current external cache bytes or physical disk allocation.
Parent reports that automatic review rejected the agent's proposed old-cache deletion before execution. Those agent attempts did not delete caches; the later user action is recorded separately below. The separately archived read-only cache audit is not proof of deletion. The actual [compression receipt](resource-recovery/older-cache-compression-result.json) records lossless NTFS compression of 1,040 files in two older cache roots, both commands exiting 0 and all file bytes unchanged. Its [before inventory](resource-recovery/older-cache-compression-before.json) has exact per-file hashes and a logical total of 1,381,604,275 bytes. Archive verification checks receipt counts, totals and containment, not current external cache bytes or physical disk allocation.
The subsequently closed [second compression receipt](resource-recovery/lossless-compression-2-result.json), its [plan](resource-recovery/lossless-compression-candidates-2.json) and [before inventory](resource-recovery/lossless-compression-2-before.json) are also preserved. Nine operations over seven retained executables and two closed cache roots succeeded; the receipt records all 1,048 files unchanged, 2,273,210,127 logical bytes, and 809,324,544 free bytes at receipt time. The GUI hard link is counted once. These are original operation records: the verifier checks the plan hash, exact planned binary pins, inventory membership/totals and recorded outcomes, without touching the external files or treating the free-space snapshot as current. No cache deletion or binary content change is claimed.
The subsequently closed [second compression receipt](resource-recovery/lossless-compression-2-result.json), its [plan](resource-recovery/lossless-compression-candidates-2.json) and [before inventory](resource-recovery/lossless-compression-2-before.json) are also preserved. Nine operations over seven retained executables and two closed cache roots succeeded; the receipt records all 1,048 files unchanged, 2,273,210,127 logical bytes, and 809,324,544 free bytes at receipt time. The GUI hard link is counted once. These are original operation records: the verifier checks the plan hash, exact planned binary pins, inventory membership/totals and recorded outcomes, without touching the external files or treating the free-space snapshot as current. These compression operations did not delete caches or change binary contents.
The [later user-removal verification](resource-recovery/user-cache-removal-verification.json) records a different actor and action. The user reported executing the supplied removal commands; at 08:55:13 UTC the parent verified that exactly the two earlier desktop cache paths `arcadia_studio-1w2zwfyvx4chp` and `arcadia_studio-00a1ywde8514v` were absent, with 1,285,787,648 free bytes. The parent observed absence, not the execution of Remove-Item. This supersedes any current blanket claim that no caches were deleted; the blocked agent attempts remain distinct. The portable verifier binds these paths to the earlier two-root receipt and does not inspect their current existence.
The [core compression result](resource-recovery/core-cache-compression-result.json) records four successful `*.o`-only NTFS compression operations on checked inactive local core cache roots. Historical session attribution remains unproved. Its unchanged-byte readback scope is all 2,086 inventoried files; the [inventory](resource-recovery/core-cache-compression-before.json) contains 2,048 `.o` files (585,498,872 logical bytes), 24 `.bin`, eight `.lock` and six `.rmeta` files. The remaining files were covered by the byte-preservation check, not the object-only compression filter. The recorded free-space snapshot is 1,546,002,432 bytes at 08:58:39 UTC.
The original core compression receipt deliberately retains `bytes: null`: PowerShell Measure-Object did not enumerate the OrderedDictionary keys. The [separate correction](resource-recovery/core-cache-compression-total-correction.json) pins the inventory SHA-256 `41f0cae50cb9fb1db7c81a0533cd0f7175f6ea4497bbd2f4dcb78180eb7f53fc` and original result `b231319690c3c750b42ca54d531c84d89507586b4bebc68160c0ead965820588`, deriving 1,986,200,805 total logical bytes. The verifier recomputes that arithmetic and checks the four-root inventory containment and recorded outcomes; it neither rewrites the original nor rehashes external cache/binary files, repeats compression, or treats logical totals as space saved.
`prepared-recovery-helpers/gate-no-incremental.py` and `build-and-preserve-no-incremental.py` were first captured **prepared, not executed**. The new runner sets `CARGO_INCREMENTAL=0` only in its process environment, records that flag and its own helper hash, and leaves the original helpers untouched. A closed formatting run now supplies execution evidence for the exact already archived runner bytes, as described below. Preparation alone did not establish a successful retry. These remain historical private-path tools and must not be executed blindly from the archive.
## Canonical source and execution-pinned formatting/Clippy
## Canonical source and execution-pinned gates
`format-final-3` completed `cargo fmt --all -- --check`, exit 0 with empty logs, unchanged 604 inputs and `CARGO_INCREMENTAL=0`. Its receipt pins the runner to SHA-256 `3c9b21fa243c618a190c6746fcfc67442a51f84afc6c0fda6b9afed2b77abe74`; the verifier resolves that pin to the identical archived `prepared-recovery-helpers/gate-no-incremental.py`. This specific receipt supports execution provenance for those helper bytes; it does not retroactively add helper pins to older gates.
@@ -116,7 +122,13 @@ The canonical input-manifest SHA-256 is `129607a08fea6f9eeae0d40982111c7513b243f
The [staged integration review](reviews/final-staged-integration-review.md) is preserved with its actual scope and pending canonical gate/native statements. It notes that its author also authored the tooltip lifetime correction, so that portion is not an additional independent review. It also records two upstream trailing-space exceptions in the unchanged vendored button source; a blanket staged whitespace-check pass is not claimed.
Canonical desktop-cli-final-3 and windows-build-final-3 were still running when this extension was authorized and are excluded. Corrected native acceptance remains pending. Parent reports that the same bounded cache-removal proposal was again blocked by automatic policy before execution, despite explicit user authorization; there is no removal receipt and no cache deletion. The actual resource-recovery claims remain ZIP deduplication and lossless compression only.
`desktop-cli-final-3` subsequently completed, exit 0: 906 passed (894 desktop + 12 CLI), zero failed, six ignored. The [acceptance receipt](gate-acceptance/desktop-cli-final-3-acceptance.json) binds result SHA-256 `1a0625733e00e19a9a353af4b7bdab0be5ed59d24c95596adab1b8d39defdebd`. The verifier independently compares all 912 named outcome lines with the prior mixed-line-ending corrected full gate, including both new weak-paragraph tests; names and outcomes match exactly. This does not claim that the ignored tests ran in the full gate.
`windows-build-final-3` also completed, exit 0, producing two non-test artifacts on the same canonical 604 input bytes. [Preserved artifact receipts](native-preparation/windows-build-final-3-binaries/preserved.json) pin the corrected GUI at 114,221,056 bytes / SHA-256 `9cff5a094e3015d95a2c5fdb8b1ceaf03aced6a09670de32a4ec5ff8dcc94900`, and CLI at 20,233,728 bytes / `684988efd2faeffc3e087e941bce927f53d46ab6630c23cb82bbead46af96c7a`. Build-result SHA-256 is `bba89a5c91682eca8fc1b1f5046c5c3f4853b3132a0dbd662cf1ca923946487d`. Receipt/helper binding confirms the executed preservation helper is the exact earlier prepared 1,814-byte file, SHA-256 `45965ef15326ebc6cc08d349867f6139bdee2fef6b2e5e879caf6692fbea4198`; no helper replacement or duplicate copy is necessary. Binary bytes remain external and are not rehashed by this verifier.
[Current-oracle-3](native-preparation/current-oracle-3/result.json), receipt SHA-256 `0824f5478e86e6db0464b3a47461d7677abf958cd5504eabf14c825b02f29382`, ran the exact canonical CLI against fresh saved missing/complete fixtures. Its build/source receipts, runner, artifact, fixture hashes, raw reports and preservation flags are bound. It again reports two missing-include errors (exit 3) and five complete-file warnings (exit 0). The verifier checks all saved ranges and line/column coordinates. This remains saved-source evidence, not native tooltip or transient editor acceptance.
Native trial 2 is now closed and its bounded captures, parent observations and post-exit receipts are included. The closed candidate-oracle-3 and launch-manifest-final-3 preparation are also included. The independent corrected native review and parent acceptance with explicit scope limits are now included. Parent reports that the bounded cache-removal proposal was again blocked by automatic policy before agent execution despite explicit user authorization. No agent removal receipt was generated; the later user-reported removal and parent's absence check are recorded separately above. Resource recovery therefore includes ZIP deduplication, lossless compression, and the explicitly attributed user action.
Coordination clarification: remote Gitea Codex contributors run on separate computers. An earlier assumption that a remote contributor's native trial blocked this machine was incorrect; historical raw reviews are preserved without extending that assumption. Locally spawned agents share this worktree filesystem. Disk-recovery records concern this computer only.
@@ -140,6 +152,22 @@ The adopted vendor tree has 71 files. All 68 common files match the probe tree;
`notices/scripts/` contains the collector, synthetic tests, manifest and supplements for reproduction after supplying a scratch checkout, the external dependency cache and LLVM runtime. The recorded invocation was `Get-ArcadiaNotices` with repository `C:/ar-text-9e8r6t`, target `x86_64-pc-windows-gnullvm`, manifest `scripts/windows-notices/manifest.json` and the recorded LLVM-MinGW root. Inspect the exact arguments in `notices/notices-actual-2/run.ps1`; adapt paths only in a new scratch helper. The checked vendor has its own LICENSE and ARCADIA-PATCH notice, `source = null`, local path provenance and no registry checksum. This evidence does not imply all cached packages will be available elsewhere.
Historical `gate-helpers/`, notice helpers and `environment/env.ps1` are raw provenance, **not portable launch scripts**. Do not execute them blindly: some contain absolute private paths. The environment file was inspected and contains only relative toolchain/PATH/linker settings, no credentials. Historical gate receipts did not independently pin their runner's bytes; archived runner bytes must not be presented as cryptographically proved execution inputs.
Historical `gate-helpers/`, notice helpers and `environment/env.ps1` are raw provenance, **not portable launch scripts**. Do not execute them blindly: some contain absolute private paths. The environment file was inspected and contains only relative toolchain/PATH/linker settings, no credentials. Earlier gate receipts without a helper field did not independently pin their runner's bytes; those archived runner bytes must not be presented as cryptographically proved execution inputs. The later no-incremental runner's explicit receipt pins are checked separately.
`cleanup/` preserves failed/superseded candidate records and actual completion receipts. `index.json` retains the original restoration references and their pinned counterpart identities; it does not package the referenced release ZIPs, executables or caches. Some old paths no longer exist after documented cleanup. Verifying those older inventories requires restoration from the exact referenced counterparts. Do not amend historical receipts to hide removals, infer deletion from a candidate list, or treat this archive's successful verification as revalidation of external restoration artifacts.
The canonical candidate receipt (`native-preparation/candidate-oracle-3/result.json`, SHA-256 `11902b3817c43e6deb252690b6fcc8fe0cf986259806e38c0f2746bba1cc1769`) records two expected exit-1 saved syntax checks: token bytes `[1127,1128)` and EOF `[1164,1164)`. Its prior receipt is current-oracle-3; the verifier checks the exact original-plus-suffix fixture bytes, parsed/raw reports, source and build bindings. These are saved CLI checks, not unsaved-editor or native tooltip acceptance.
`native-preparation/launch-manifest-final-3.json` (SHA-256 `ff80f32504cb3f427520534c2d796a13fb9797d0ab611095dc4b39126b0afd7c`) pins the executed `prepare-launch-3.py` (SHA-256 `7d469a7df729be59a95ac8b99be72034fad9323443107ffc1d2ea2746e1ec650`). The earlier `prepare-launch.py` remains preserved unchanged as the earlier preparation, with its own original manifest binding. They are different helper versions; the new helper was not substituted into historical records. The new manifest binds strict-clippy-5, format-final-3, desktop-cli-final-3, windows-build-final-3, current-oracle-3, preservation and launch helpers. Candidate-oracle-3 is a separate completed receipt, not an item in this manifest. `nativeReady: true` records admission to launch a development trial only. The portable verifier validates all referenced archived evidence and recorded binary identities without reading external executables or executing preparation helpers.
## Closed corrected native trial 2
`native-trials/trial-diagnostic-2/observations.md` preserves the parent's observations and limits. `reviews/native-trial-2-review.md` and `.json` preserve the independent stored-image/receipt review; `native-trials/trial-diagnostic-2/acceptance.json` records the parent's `accepted_with_explicit_scope_limits` decision. The raw record contains 49 metadata files and 53 JPEGs, the recorded inline recorder function definitions, launch/manifest/closure, close UI observation, post-exit verification, and two work-fixture files. No application executable, DLL, profile or cache is copied. The manifest binds canonical build3 GUI `9cff5a094e3015d95a2c5fdb8b1ceaf03aced6a09670de32a4ec5ff8dcc94900` to the already verified final-3 build/gate receipts.
The immediate Discard UI observation at 09:23:48.326 UTC still lists the app window. The later launcher receipt establishes PID1164 exit0 at 09:23:49.269580 UTC, empty logs and unchanged actual/preserved GUI and DLL. The post-exit receipt (SHA-256 `48dd193b1d873f64f62957e07d4f212c5049ab925d2355ba779124b6d35806bf`) pins its executed `native-preparation/check-trial-2-closure.py`, closure, every capture and exact equality of the two disk fixtures with original inputs. The portable verifier rechecks these archived byte relationships, exact capture membership and chronology. It neither reads external binaries nor executes the historical postcheck helper. Disk equality does not establish transient model equality; no Save/Apply is a parent action-record statement.
Parent observations cover readable corrected tooltip body/footer, real overlapping warnings, wrapped and scrolled markers, token and zero-width EOF errors, edit invalidation, selection replacement/Undo, Find Escape and modal suppression. They explicitly limit the zero-delta wheel pointer experiment and window-chrome-only accessibility. The first scroll/resize attempts did not change the view; actual changes occur later. Requested triple-click did not establish line selection. Back after Problems navigation did not return to the included file. Restore first produced a capture failure before recovery. Find Close was not separately exercised. Preserve these limits when using the screenshots: archive verification and process exit alone do not establish UI acceptance, full application behavior or packaged release acceptance.
The native2 acceptance receipt pins independent review JSON `92da9da3dd9e184280b468ffecf6361f5e32244ae09f6f27b6cd2f2e328de51d`, post-exit verification, canonical source inputs and GUI identity. The verifier validates those bindings and the review's exact capture/oracle references. It reports the recorded decision without reevaluating UI behavior. This bounded trial acceptance does not close peer integration, packaging, release or issue #12 by itself.