A visible video element may not be the actual playback target because a play button overlays it. Northstar finds the play control belonging to the chosen response instead of forcing a click on the video surface, then checks that the same result's download is ready.
Decide which video is intended first
The Gemini path narrows ready video candidates by the requested name or response group, then uses ordinal ordering to require one result within that scope. Without a target it selects the newest candidate; an explicitly named scope takes precedence. This is not an entrance that presses any download button on the page.
ChosenGroup binds later play and download controls to the same response. That avoids mixing an older video's available download with a newer result still preparing. Verifying new video generation and downloading an existing selected video are different tasks, so the intended result must be established before either operation continues.
Do not add playback if a direct download already exists
A ready direct-download control in the chosen group is used immediately. Playback is sought only when that control is absent. The implementation does not hard-code another playback for every download. Reading present controls can reduce unnecessary interaction as well as ambiguity.
When playback is needed, exactly one enabled button with a recognized play label is required. Zero or multiple candidates produce GEMINI_VIDEO_PLAY_TARGET_REQUIRED. A failed surface click does not justify forcing input onto the background or another frame. The procedure chooses the current control matching the actual native hit target.
After playback, wait for the same response’s download
After pressing play, until reads for an enabled video-download in chosenGroup. A control appearing earlier in another response cannot satisfy that condition. A fresh observation then requires exactly one download target. Playback-click success is not reported as receiving a file.
The direct-control branch also rereads its target rather than relying indefinitely on an old ref. Distinguishing playback, readiness and download initiation explains where a failure occurred. The connection matters more than the apparent convenience of keeping one earlier reference through a changing interface.
Require actual file data in the download response
Download checks the host's verified flag together with a nested file identity, name, positive integer size and SHA-256 format. A click acknowledgment without that file receipt raises GEMINI_DOWNLOAD_UNVERIFIED. Subsequent work needs inspectable identity and byte evidence for the received file.
Those checks do not decode the whole video or establish playback through every segment. Positive size and digest support stored-file evidence; actual format and usable playback may need additional inspection. Observed generation, file receipt and validation for intended use remain different outcomes rather than one broad success.
Tests inspect absence of input for invalid play candidates
The fixture includes old and new videos, an old download and a play button for the selected newer response. The normal path must click only the actual overlay control and download from the new group. With zero or two play controls, neither click nor download may occur. Another result cannot be substituted to produce apparent success.
This task read the functions and tests without generating, playing or downloading fresh real media. The independent generation observer is not a downloader either; it illustrates only the narrower distinction between declared ready media and an actual file receipt. A passing fixture is not promoted into complete service verification.
Connect verification to the result the user will actually use
A person asking for a video file needs more than a statement that a video-shaped element appeared. The record should connect which result was selected, which control opened it and which file arrived. A successful intermediate button does not remove unfinished work when the final material is absent.
I see an agent-friendly program as one making that chain readable in a compact result. Selected response, current play control, matching download and file receipt identify where to inspect before retrying. The direction is precise outcome lineage rather than more forceful clicking.