Release · 2026-08-14T16:21:07+02:00 · By Threadnote
Threadnote 4.2.4
Threadnote 4.2.4 keeps ordinary file-local TypeScript edits incremental and adds privacy-bounded diagnostics for detecting unexpectedly expensive code-graph rebuilds.
What's new
Threadnote 4.2.4 keeps ordinary file-local TypeScript edits incremental and adds privacy-bounded diagnostics for detecting unexpectedly expensive code-graph rebuilds.
Incremental graph updates for local declarations
- Adding, removing, or renaming an unexported path-local TypeScript declaration—such as a private class method or a local test callback—now rewrites only the changed files instead of replaying the full cached graph.
- Published resolution changes remain fail-closed. New exports may use the existing bounded declared-project closure; oversized or ambiguous projects still select a safe full materialization.
- Persisted activation uses the same published-surface check, and explicit global lookups, reexports, export changes, malformed facts, and deletion-only changed-file activations retain their conservative behavior.
Inefficient-rematerialization diagnostics
- Optional anonymous telemetry can emit one terminal, path-free observation for each successful graph build, with clean/dirty build kind; closed materialization, fallback, resolution-closure, and efficiency classes; and coarse file-count, fact-byte, and amplification buckets. Failed graph builds add only bounded outcome/type to that lifecycle surface and interruptions only outcome/duration; neither adds graph classifications or buckets.
- The operated dashboard shows unexpected-full percentage, fallback reasons, rewrite and cached-fact replay distributions, and recent inefficient materializations without repository, path, commit, session, or invocation identifiers.
- This is a material expansion of the optional telemetry contract. Existing telemetry consent fails closed after the upgrade; review the current preview and opt in again only if you agree:
threadnote telemetry status
threadnote telemetry enable
threadnote telemetry enable --apply
The production telemetry gateway must be upgraded and its v1/v2 storage canaries must pass before publishing the 4.2.4 application binaries.
Existing standalone installations upgrade with:
threadnote update