Record corrected Windows diagnostic replay and final gates

This commit is contained in:
2026-09-13 02:32:46 -07:00
parent 9fd76aef3a
commit 32368713ef
156 changed files with 20130 additions and 35 deletions
@@ -1,6 +1,6 @@
# Text diagnostics: integration evidence and remaining acceptance
This contribution implements [issue 12](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/issues/12): passive source underlines and hover explanations tied to the exact displayed draft. Source and CPU test evidence is available; **corrected native tooltip acceptance is still pending**. The first Windows trial found visible underline bands but blank tooltip text. This report does not accept the newer [issue 27 integration](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/issues/27), a package, or the full application.
This contribution implements [issue 12](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/issues/12): passive source underlines and hover explanations tied to the exact displayed draft. **The corrected Windows replay confirms readable tooltip text**, wrapped/scrolled placement, word editing and Undo, actual parser-token/EOF errors, and modal suppression. Source is published at `9fd76aef3ae2810667d3f2b031fc43692fc04c89`. The first Windows trial's blank-tooltip failure remains preserved. This report does not accept the newer [issue 27 integration](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/issues/27), a package, or the full application.
The implementation builds on `b4b860f2776aa8251306d83ff58362c0359176ef`, including the [published Text workspace contribution](text-workspace-verified-20260913.md) at `2df7f580aa4bd728a728c83ac10e6ccc956ef069`. That predecessor supplies the permanent editor layout, diagnostic publication/visit guards, Find focus preservation and source navigation behavior. The diagnostic captures contain working changes over that base; the base commit alone does not contain this contribution.
@@ -25,11 +25,13 @@ The [portable evidence archive](experiments/text-diagnostics-20260913/README.md)
- Core provenance coverage passed 447 tests, with one ignored. Later UI changes are outside that core execution.
- The tooltip-corrected desktop/CLI suite passed 894 desktop plus 12 CLI tests, with six ignored overall. Two new deferred-Weak tests distinguish surviving post-draw text from the earlier eager recording test's false assurance.
- Actual-layout and mounted tests cover shaped geometry, clipping, selection/input preservation and stale admission. CPU timing experiments cover index construction and visible projection, including long wrapped lines; they do not measure native paint or GPU frame latency.
- Initial native evidence confirms underlines and the blank tooltip defect. Saved CLI missing/complete and parser-token/EOF variants retain exact raw diagnostics and fixture bytes. Saved-byte checks do not establish transient GUI model equivalence.
- Corrected native trial 2 confirms readable missing-include messages, both real overlapping warnings on each declaration, wrapped/scrolled geometry, stale clearing on word replacement and Undo, and actual token/zero-width EOF messages at 33:1 and 33:38. Window reflow and modal cancellation/suppression were exercised. Independent review inspected 22 original JPEGs; the archive retains all 49 observations and 53 JPEGs. The trial closed normally with empty logs, unchanged GUI/DLL and exact original disk fixtures. No Save or Apply was performed.
The blank tooltip resulted from draw-local paragraphs expiring before WGPU upgraded its queued weak references. Widget Tree state now owns the current body/footer paragraphs through deferred preparation and clears/replaces them during each draw. This is render-resource retention, not cached hit or publication authority. Independent static review and the new tests support the correction; a corrected native visible-text replay remains required.
The blank tooltip resulted from draw-local paragraphs expiring before WGPU upgraded its queued weak references. Widget Tree state now owns the current body/footer paragraphs through deferred preparation and clears/replaces them during each draw. This is render-resource retention, not cached hit or publication authority. The deferred-Weak regression tests and independently reviewed corrected native replay support the correction.
Canonical-LF formatting and strict workspace/all-target Clippy with warnings denied passed on the same 604 captured inputs. The canonical full-test and matching-build receipts are not included in this source checkpoint. Earlier corrected build/Clippy attempts failed on disk exhaustion; those failures are retained. Final verification must bind the same captured source and actual preserved GUI before native acceptance is added. No result is inferred from a started or prepared gate.
Canonical-LF formatting, strict workspace/all-target Clippy with warnings denied, full desktop/CLI tests (906 passed, zero failed, six ignored), and the Windows GUI/CLI build all passed on the same 604 captured inputs. The input manifest SHA256 is `129607a08fea6f9eeae0d40982111c7513b243f6bb311bea8fd59026ce388076`. Gates started before the source commit; their exact captured compilation bytes match the published commit. The replay used the preserved GUI with SHA256 `9cff5a094e3015d95a2c5fdb8b1ceaf03aced6a09670de32a4ec5ff8dcc94900`. Earlier disk-exhaustion failures are retained alongside recovery records, distinguishing user cache deletion from agent compression and read-only checks.
Native acceptance is deliberately scoped. Triple-click did not establish full-line selection; Back after a Problems visit reported no previous location. The initial scroll and border-resize attempts did not move the content or window; later drawer scrolling and maximize/recovery supply the stated geometry evidence. Restore required recovery after a minimized-window capture failure. Zero-wheel pointer placement does not isolate passive CursorMoved or interaction clocks; mounted widget tests own that evidence. Find Escape was tested, not its Close button separately. Saved CLI spans and disk equality do not establish transient GUI model equivalence. See the archive's corrected-trial observations, acceptance record and independent review for exact limitations.
## Reproduction