Files
ARCADIA-Studio/harness/experiments/text-diagnostics-20260913/native-trials/trial-diagnostic-2/observations.md
T

85 lines
5.4 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Corrected Windows diagnostic replay
Parent observations, 2026-09-13. Production source is published at
`9fd76aef3ae2810667d3f2b031fc43692fc04c89`; all 604 canonical compilation
inputs match the successful final-3 build capture. GUI SHA256
`9cff5a094e3015d95a2c5fdb8b1ceaf03aced6a09670de32a4ec5ff8dcc94900`.
This is a development Windows trial, not integrated or packaged acceptance.
The launcher records PID 1164, start 09:07:04 UTC, normal exit at 09:23:49 UTC,
empty stdout/stderr, and unchanged preserved/actual binary and runtime DLL.
The immediate UI close observation still listed the window; the later process
closure receipt establishes actual exit. No Save or Apply action was performed.
`post-exit-verification.json` independently establishes equality of the two disk
files with the immutable input fixtures and pins all 49 metadata/53 JPEG files.
It does not establish transient model equality. The visible model stayed at
zero objects/links in this repair-mode workflow.
## Observed behavior
- 006–008: missing include is marked on the include directive. Tooltip 007
contains readable `Error [missing_include]`, location 3:5, the missing path
and OS error, plus the Source problems footer. Blank space clears it.
This closes the previously observed blank-tooltip rendering defect. GUI
displays one error whereas the saved CLI producer reports two duplicates;
no whole-producer parity claim is made.
- 009–013: loading the included raw file produces five warnings. The two
no-UUID declarations are underlined across wrapped descriptions, including
Unicode and repeated alias prose. The first declaration's hover shows both
`unallocated_leaf` and `work_without_behavior_context`, location 3:1, and
Receive request. The second shows both at 7:1 and Evaluate request.
012's label is misleading: its point is beyond the short wrapped line and
correctly has no tooltip. 013 moves inside that line and shows the message.
- 016–018: double-click selects the alias; typing `receive_changed` replaces
that word and immediately clears stale bands/tooltip. Undo restores the
original alias and current warning text. No disk save occurs.
- 020–021: Ctrl+F opens Find with its input focused; Escape closes it and the
original editor selection is visible again.
- 022–033: Ctrl+End, Return, and `}` create the separately evaluated parser
candidate. After lint, 025 marks the token and 026 shows
`Error [invalid_source] · 33:1`, `Unknown declaration '}'.` The tooltip fits
above the marker near the bottom of the editor. Undo removes the token.
At the retained added newline, typing `sa_function unfinished "Unfinished" {`
produces the zero-width EOF marker. 031 shows location 33:38 and
`Expected a field, element declaration, or '}'.` Undo clears the error while
the pointer remains at its previous position; a further Undo removes the
added newline and clears the file's dirty marker.
- 034–039: Actions opens normally; no tooltip appears with the menu active.
Source problems exposes all five readable messages and locations. With the
drawer reducing editor height, scrolling moves the first declaration out
of view and clips the second at the top. Hover on the scrolled description
still identifies Evaluate request at 7:1. Scrolling back clears that tooltip
when the same pointer now lies over an ordinary comment.
- 040–041: maximizing changes the captured main image to 2245 by 1232 and
reflows descriptions with matching underline lengths. Restore input reports
a minimized-window capture failure. Recovery lists the same returned app,
activates it, rehydrates the window, and captures the restored 1442 by 932
layout with aligned bands. No coordinates from the failed capture are reused.
- 042–044: choosing the project warning navigates to project.arcadia and
selects its relevant source. Returning through the file tree restores the
included file and its own bands.
- 045–049: close confirmation owns the UI; Cancel returns to the editor,
hover works again, and Alt+F4 from an actively visible tooltip hides it as
the modal opens. Discard closes only this owned test fixture without saving.
## Limits and inconclusive attempts
Zero-delta wheel injection positions the pointer because the supported API has
no passive move method. It does not establish a pure CursorMoved event or an
unchanged interaction clock; mounted widget tests own that evidence. UIA exposes
only window chrome, so native focus/selection judgments above use visible
caret/selection and actual typing outcomes, not screen-reader accessibility.
014 does not move text because the whole fixture fits before the drawer opens.
015's border-drag resize attempt leaves the size unchanged. Actual scrolling
and resizing evidence instead comes from 037–041. 019's requested triple-click
still shows a word selection, so native full-line selection is inconclusive;
the mounted Word/Line tests remain the relevant verified evidence. 043's Back
shortcut reports no previous source location after Problems navigation; it does
not return to the included file. This trial does not claim that Problems visits
populate Back history. Find's Close button was not exercised separately from
Escape. Synthetic overlap overflow, bidi/ligature and empty-line geometry retain
their separate test scope; native overlap here covers the two real warnings per
declaration. No Linux, full application, peer integration, or release acceptance
is implied by this replay. Independent review is recorded separately.