4.7 KiB
Inspector actions: parent native observations
On 2026-09-22 the parent controlled candidate 14e7e6aa46 through Windows Computer Use. Launch and close receipts bind the process, packaged binary, runtime and private profile. Saved-Project comparisons reuse the frozen b10 evaluator because core and manifests are unchanged. The native file dialog inherited an old folder, but the parent entered the full path to the new candidate working copy. Old b10 sources were untouched.
Editing and recovery at 1442 × 932
The initial Project form displayed all fields and the fixed Apply/Revert row. The parent selected Saved “Service calls - Details trial”, entered Focus, selected the first Call, and opened Details → Properties. The form showed “Read primary status” and alias first_call. Scrolling in the inspector margin reached Scope and Postcondition while both actions stayed visible.
The parent replaced the quoted primary expression with quoted secondary. Checkpoint 01 confirms the disk source was still baseline before Apply. Clicking fixed Apply without scrolling back produced “Properties applied” after settling. Save produced checkpoint 02: 6,134 bytes, SHA-256 4cafcf18e45703b03b3c997080a0ed7fbbbee02d386062da3c6c00504e7be75e. With focus on the Save button, one Ctrl+Z followed by Save restored the exact baseline at 03; one Ctrl+Y and Save restored checkpoint 1 at 04. These were model history commands, not editor Undo.
The parent changed the lower expression to quoted “discard this draft”, then clicked fixed Revert without scrolling back. The field returned to secondary, the header became clean and the footer reported “Property draft reverted”. Checkpoint 05 stayed at 1.
For rejection, the parent scrolled up to the operation selector and chose SetLimit while retaining Scope. The raw secondary expression remained, with an invalid carried-address notice. After scrolling down, fixed Apply rejected the change with message_value_field: “The qualified field must be carried by the exchange, following Value record fields only.” The raw expression remained and checkpoint 06 stayed at 1. Fixed Revert recovered ReadStatus/Scope/secondary and a clean header; checkpoint 07 stayed at 1. This tests incompatible carried-field rejection, not isolated Reply-only invalidity.
From lower Properties, Connections displayed references without the Properties action row. Returning to Properties kept Scope and Postcondition in view. This demonstrates retention of the visible lower position, not internal offset-bit equality or independent scroll state for each tab.
Smaller window and keyboard focus
The parent resized through the Windows system Size command to an actual 1102 × 732 window. A width click reported a point over a non-target window after resizing; the parent reobserved the app and finished sizing with Return. No input was sent to another app.
At the shorter height, further scrolling exposed Scope and Postcondition with the fixed row unobscured. The parent entered quoted “small-window draft”; fixed Revert restored secondary and the clean header. No new valid Apply transaction was performed at this smaller size.
Tab after Revert focused Name and scrolled it into view; the next Tab focused Alias. No characters were entered. Focus is evidenced by the visible caret and border; the accessibility tree exposed only the window/title bar. Project properties then opened the short Project form, whose fields and action row were visible at this size. Final Save produced checkpoint 08, exactly checkpoint 1.
The parent recorded Alt+F4 on the clean app separately. The subsequent window inventory showed the app had closed; its observer exited 0 with empty stdout/stderr and unchanged immutable inputs.
Evidence and limits
Seventeen current JPEGs were captured with explicit state arguments at the two recorded window sizes. Each frame supports its captured state; the narrative also records parent-observed actions. Immediate snapshots after Apply, Save or selection could precede completion, so the parent reobserved completion before dependent actions. No images came from earlier runs.
The trial supports the targeted long Call form improvement and short Project form at these Windows sizes. Valid Apply and model Undo/Redo were tested at 1442 × 932; Revert at both sizes; rejected draft recovery and the tab roundtrip at the larger size. No new relation form, dedicated busy/modal race, keyboard activation of actions, broad accessibility, fresh reopen, other-platform or broad lifecycle claim is made. Existing distant footer diagnostics, historical save text and truncated labels remain. Linux checks are user-paused. This does not complete issue 24 or the product goal.