Release · 2026-08-26T01:25:38+02:00 · By Threadnote

Threadnote 4.3.5

Threadnote 4.3.5 keeps accelerated one-file graph updates warm when Git refreshes only index bookkeeping, restores machine-readable release checks, and makes automatic-update failure telemetry preserve the underlying typed failure.

What's new

Stable large-repository status acceleration

A private Git-status cache now distinguishes physical index rewrites from real staged-tree changes.
On metadata-only churn, Threadnote compares a bounded digest of the raw staged entries and index flags before reusing the warmed private index.
Real staged changes, missing or malformed evidence, races, and oversized observations still fail closed to private index reinitialization or the ordinary read-only status path.

In the pinned IntelliJ investigation, a private status observation took 5.27 seconds initially, 1.48 seconds after a content-neutral index rewrite, and 272 milliseconds on the following warm observation. The exact v4.3.5 release-scale benchmark is retained separately from this component evidence.

Reliable updater checks and diagnostics

threadnote update --check --json and threadnote update --stable --check --json again emit one versioned threadnote-update-check document; threadnote update --json remains the automatic-update status shorthand.
A failed automatic-update worker now remains a failed Effect after its durable status is written, so telemetry reports outcome=failure with the existing privacy-safe error classification.
Coordinator contention remains classified as busy, while lock failures raised inside the updater retain their real failure type.

Existing standalone installations upgrade with:

threadnote update