lowfire.
← The daily journal

October 20, 2026

104 merged pull requests · 47 detailed notes

Full-disk recovery, setup, calls, screen-reader behaviour and large-text layouts received extensive fixes, with release and video plans kept distinct from shipped behaviour.

New and improved

1 notes

Fixes and polish

35 notes

Designs and foundations

1 notes

Designs, contracts and foundations are work in progress; they do not by themselves mean a finished feature is available.

  • Accepted video and private-release plans

    Design work records Linux video backend choices, isolated codec work with stall recovery, and private signed Mac beta releases. These plans do not themselves ship Linux video or publish a beta download.

Behind the scenes

10 notes
Read all 10 notes behind the scenes
  • Linux memory accounting and reductions

    Linux idle-memory work records the process footprint and its contributors, with targeted reductions. The new measurement is initially reported without enforcing a pass or fail; this does not claim that all Linux workloads meet the memory target.

  • Owner decisions recorded

    The project records decisions about saved drafts, secure profile naming, Linux memory accounting, leak checks, video support and stalled-codec recovery. The record directs implementation rather than adding all of those behaviours itself.

  • Shared platform behaviour and wording

    Atomic saves, POSIX services, profile setup, clocks and timed waits now use shared implementations. Button and menu capitalisation follows a checked convention.

  • More trustworthy builds and focused verification

    Call statistics keep related observations together, and probes count the connection’s actual bytes. Test suites are selected from one table, compiler caches are bounded and track headers, builds notice older input timestamps, missing shader tools fail clearly, and drivers reject stale executables.

  • Track completed development sessions

    Coordination now records completed-session cleanup and custody of retained evidence.

  • More realistic end-to-end failure checks

    The end-to-end harness can slow connections and fill or lock local storage. Scripts wait for actual server conditions, respect Linux media capabilities and avoid sending a synthetic client address to a real remote deployment.

  • Interface tests wait for the screen they judge

    Checks judge wholly visible rows, wait for navigation to rest and unread counts to appear, and control the typing-state lifetime. Touch tests read after transitions, and large-text clipping checks use the correct rectangles.

  • Native tests respect their runtime environment

    The media hold test no longer treats a busy machine as a codec failure, Linux audio can use the continuous-check machine’s audio-policy version, and secure-key tests handle the full sanitized run.

  • More precise boundary and failure fixtures

    Checks observe queued arguments before cleanup, handle long temporary paths, and distinguish update-card controls from sidebar buttons. Update extraction is bounded by CPU work, terminal replacement is detected without a file watch, server-test output drains correctly, and failed automation launches retain their state.

  • Portable reports and fewer shared-file conflicts

    Continuous-check log fixtures work across platforms, interface-test areas have separate registry lines, and the live status distinguishes completed worktrees still awaiting cleanup.

Updated · . Expanded from the first draft to cover the full day’s reviewed work, including smaller improvements and fixes.

Back to the top ↑

Good things take care.

Lowfire is in development. These notes cover the project’s reviewed changes, grouped into plain-English topics. Pull requests are reviewed changes to the project; the counts also include maintenance and early direct commits. Internal coordination records are accounted for privately.

Designs and foundations are labelled as work in progress. Genuine screenshots show fictional demo content. Current reference captures do not recreate historical builds or imply earlier device availability.

Checked through . The latest day covers work reviewed through the pinned snapshot, not the whole calendar day. The notes were expanded on October 25 to cover the full reviewed history.

Back to the beginning ↑