# Editing notes: window-minimize python-file-v2 native preview v1

Collection was already complete. This edit reuses `recording.mp4`. The Agent was not run again, and the prompt was not changed. Warnings were not scored.

## Source

- Recording: `recording.mp4`
- Container duration: 111.000 seconds
- Picture: 3840x2160
- 807 decoded frames. Timestamps run from 0.000 through 110.875. 757 intervals are 0.125 s. Other gaps: 36 at 0.250 s, 7 at 0.375 s, 4 at 0.500 s, 1 at 0.625 s (38.875–39.500), and 1 at 2.000 s (39.500–41.500). Do not use frame-number/8
- SHA-256: `d658c53ca10ecaba3fd01701cc1d470518182f93631b8808c0ebf0b2be86e5ee`
- `confirmations.json` is `[]`. `approval-scope.json` has `"grants": []`. There is no `confirmations` directory

WorkBuddy 5.9.3, English UI, desktop 1, maximized. `native-window-observations.jsonl` tracks WorkBuddy windows only. It does not record the Python-created Arena panel. Onset was taken from decoded frames, not from those observations. `native-events.json` has no tool timestamps.

The visible target is one owned orange Arena panel, title `Arena panel`, label `ARENA PANEL`, about 2380x1339, color BGR `0x0078FF` / RGB `#FF7800`. It is created restored, then minimized and restored every 1.5 seconds for 24 seconds. Minimized frames show a taskbar button `Arena panel`. This is ShowWindow minimize, not hide.

## Observed onset

The first visible orange Arena panel is source **31.500 s**.

Adjacent decoded frames:

- **31.250 s**: no Arena panel. Chat shows `Run window-minimize.py`, `Processed 22s`, stop control, `Default Permissions`. No sandbox approval panel
- There is no decoded frame at 31.375 s (0.250 s gap from 31.250 to 31.500)
- **31.500 s**: orange `Arena panel` centered, label `ARENA PANEL`. This is the first orange frame
- **31.625 s**: same restored panel
- **32.875 s**: first minimize. The large panel is gone; the taskbar shows `Arena panel`
- **34.375 s**: restored again

Orange-pixel scan of every decoded frame, scaled to 320x180 and mapped 1:1 to ffprobe timestamps, first exceeds the hit threshold at 31.500 s and last exceeds it at 57.250 s (93 frames). Labels were then read on those same frames.

## Selection

No crop. Full frames. Original speed.

| Stage | Start (s) | Duration (s) | Source range (s) | Basis |
| --- | ---: | ---: | --- | --- |
| opening | 5.500 | 5 | 5.500–10.500 | Readable prompt in the composer, then the actual submit, then a short interval after it |
| effect | 30.500 | 10 | 30.500–40.500 | About 1 s before the 31.500 onset, then minimize/restore at original speed |
| response | 79.875 | 5 | 79.875–84.875 | First decoded frame of the settled completed public reply |

Opening. **4.000** is still the empty composer (`No conversation history`). **4.500** already has the full `window-minimize.py` request in the composer. **5.500 through 9.125**: that request remains in the composer with a send control. **9.125**: prompt still in the composer. **9.250**: first submitted frame: composer cleared to the placeholder, stop control, `No conversation history` still shown, prompt not yet painted in the thread. **9.500–9.625**: empty composer, stop control. **9.875**: submitted request bubble, `Processed 1s`, `Starting conversation runtime...`. **10.500**: same submitted bubble. **11.000**: `Thinking`. Submit occurred between 9.125 and 9.250.

Effect. Recipe start is 30.500, one second before 31.500. 30.500 is a decoded timestamp. That frame and **31.250** still have no Arena panel and no approval dialog. The lead-in is 1.000 s. The onset at 31.500 is inside the segment (output 6.000). Later frames in this 10 s window show restore, minimize (taskbar `Arena panel`), restore, minimize, restore, then minimize again. No sandbox approval panel appears.

Response. **79.500** is still generating (`Thinking`, stop control, last paragraph truncated). **79.625**: send control is present, but the last paragraph still overlaps the composer and the reaction row is absent. **79.875** is the first settled completed public reply: reaction buttons, `DeepSeek-V4 Pro`, send control, and the closing sentence that matches `agent-output.txt` (`genuine ShowWindow(SW_MINIMIZE) minimize, not a ShowWindow(SW_HIDE) hide`). That completed view holds through **110.500**. **110.625** is WorkBuddy closing. **110.750–110.875** is the desktop after WorkBuddy closed. The response excerpt uses 79.875–84.875, not the shutdown.

## Omitted effect and closure

The 10 s effect window includes the 1 s lead-in and about 9 s of minimize/restore. It omits the remaining visible panel from 40.500 through 57.250 and the close at 57.375. That omitted span is about 16.75 s of visible effect plus closure. The restore at 41.500 sits just after the excerpt because of the 2.000 s capture gap 39.500–41.500.

The last ~1 s of the effect excerpt (output 14.000–15.000) holds the minimized frame from source 39.500. There is no decoded source frame between 39.500 and 41.500.

The completed reply stays on screen through the final hold until 110.500. The last source frames from 110.750 no longer show WorkBuddy. The full completed text is also in `agent-output.txt` and `final-screen.png`.

No lead-in was shortened to avoid a confirmation. No confirmation panel is in the selected ranges. `Default Permissions` and the in-chat `Run window-minimize.py` status are not sandbox approval dialogs.

## Timing uncertainty

Decoded timestamps, not frame-number/8, were used. The capture interval is usually 0.125 s. Onset can have occurred up to one missing frame before 31.500; the previous decoded frame is 31.250. Submit occurred between 9.125 and 9.250. The first settled reply can have occurred in the 0.250 s gap 79.625–79.875. The effect recipe starts at 30.500; that timestamp is present. Output stage boundaries fall on 5.000 s and 15.000 s after 8 fps wall-clock normalization.

## Approval stills

`confirmations.json` is an empty list. No approval screenshot was created.

## Checks

- Export command: from the repository root, `PYTHONPATH=src`, `python -m arena dsh-preview --run-dir <run> --moments window-minimize-python-file-v2-native-preview-moments.json --ffmpeg <ffmpeg> --output-name window-minimize-python-file-v2-native-preview.mp4`. No crop
- Output duration: 20.000 s. Picture: 1920x1080. Decoded frames: 160. Timestamps: 0.000 through 19.875, every 0.125 s, with no gaps
- Stage boundaries in the output are 5.000 and 15.000
- Output 0.000 shows the prompt in the composer. Output 3.750 is the submit (empty composer, stop control). Output 4.375 and 4.875 show the submitted request
- Output 5.000 has no Arena panel (`Processed 21s`, running `window-minimize.py`). Output 6.000 is the orange `Arena panel` onset. Output 7.375 and 10.500 and 14.000 show the minimized taskbar button. Output 8.875 and 12.125 show the restored panel. Output 14.875 is still the minimized 39.500 hold
- Output 15.000 and 19.875 show the completed public reply (`complete`, no approvals, `ShowWindow(SW_MINIMIZE)`, send control, `DeepSeek-V4 Pro`)
- No sandbox approval panel appears in the inspected source range or in the output
- Source SHA-256 after export matches the hash above. `recording.mp4` was not replaced
- Provenance source path is `recording.mp4`. Output SHA-256: `6711dca91de5e101dda2713ed1203e93252cfa632b8839f8ef539cdfb4775ffc`

## Missing evidence

No native approval dialog was captured. `confirmations.json` is `[]`, and there is no confirmation screenshot. None was created for this edit.

The desktop recording of the completed reply is scrolled to the later paragraphs (`Approvals`, `Errors`, closing sentence). The opening `The script ran successfully...` line sits above this view. The full completed text is in `agent-output.txt` and `final-screen.png`.

## Inspection artifacts (not trial originals)

`artifacts/verification/workbuddy-window-minimize-native-906c6180/` contains source stills at the selected offsets and output stills at 0.000, 3.750, 5.000, 6.000, 15.000, and 19.875.