• Rune v0.343.0
    Auto-version and Release / release (push) Successful in 26s
    deploy / deploy (push) Skipped
    CI Pipeline / best-practices (push) Successful in 14s
    CI Pipeline / rust-surface (push) Failing after 23s
    CI Pipeline / documentation (push) Successful in 8s
    TUI Release / release (push) Successful in 39s
    CI Pipeline / go-surface (push) Failing after 44s
    CI Pipeline / gitea-offline (push) Successful in 23s
    CI Pipeline / lint (push) Failing after 1m0s
    CI Pipeline / type-check (push) Failing after 50s
    CI Pipeline / canary (push) Failing after 3m30s
    CI Pipeline / unit-tests (push) Failing after 31m13s
    CI Pipeline / required-checks (push) Failing after 1s
    CI Pipeline / CI Pipeline / notify-event-bridge (push) Failing after 7s
    Stable

    conductor released this 2026-10-24 03:49:32 +01:00 | 19 commits to master since this release

    Rune v0.343.0

    What's new — plain English

    • The STREAMING ROOT-CAUSE WAVE — a turn never sits inside one blocking call again (the release server #2556, owner verdict: the 330s→480s→6x480s lineage patched the symptom).
    • The QUIT WARNING — the first ctrl+c of the D46 exit gesture swaps the message box's key hint for the literal soft hint 'press ctrl+c again to quit'; any other key or the 1s timeout restores the live key hint (the D46 timeout disarm was unreachable dead code inside the KeyPressMsg case — the reset no….
    • The SCROLLBAR wave — the fade layer's overlay splice dropped the thumb glyph on short styled rows (the common transcript shape), so no bar ever rendered; the splice now the glyph at the column even past the line's end, the thumb carries a new themes RoleScroll token (scheme-matched yet distinct, cal….
    • The LONG-ANSWER FORMAT BREAK — the table breakout's edge rows overflowed the panel width at narrow widths (edge/body geometry disagreed by the separator columns); rows and edges now share one width, an honest too-narrow drop, and the 20+ block mixed-answer repro asserts no line exceeds the pane at a….

    What you could try

    • Ask Rune about something you told it before — earlier notes should come back correctly and faster.
    • Have a normal conversation with Rune and watch how it responds.
    • Open the chat window and use the changed panel — everything you touch should look and behave normally.
    • Give Rune a task and watch it appear/complete in the task panel.

    How it was verified

    • Every change: contract opened via construction_interface before commit, walked to closed with evidence
    • Every port: truth battery generated from the live Python oracle, replayed as a hard CI gate
    • Pipeline: ruff + silent-handler ratchet (Python), go vet/gofmt/race/fuzz (Go), cargo clippy/fmt/test (Rust)
    Downloads