Skip to content

1.32.0

Latest

Choose a tag to compare

@github-actions github-actions released this 17 Nov 14:54
· 1 commit to main since this release
38ea854

🌟 Karpathy LLM Wiki v1.32.0

Highlights

  • The Related list became one system. It was several independent rules stacked: an orphan sibling rule, a note-grounded list, a new cross-source projection. This release gives it a budget, a ceiling that records the projection separately, a comparator that ranks by evidence instead of alphabet, a gate that throws out hub-strength targets, and an exclusion that stops same-note pairs from being called "cross-source". It is the largest single thing this release changed.
  • A page move no longer reads as an edited note, and the move leaves a record. The drift check hashed the literal body, so a link-safe rename made a note report "Note changed since ingest" with nothing to suggest why. Pages now carry a second fingerprint with every wikilink reduced to its display text, and the ingest log names the move — from what, to what, and why — so the vault's own changelog answers the question the lint report raised.
  • Dutch, Polish and Thai ship. The interface is native in fourteen languages, and so is the wiki output — including the page-section headings and every notice the ingest emits. Three languages (zh-Hant, it, ru) that were selectable but silently falling back to English were found by a new parity guard and fixed in the same change. Fourteen READMEs, verified section by section against the English one.
  • Cross-source relations can now be rescued on a full page, and cannot leak across notes. A projection whose page already met the note ceiling gets its own above-ceiling allowance sized by what it produced. And a same-note pair is no longer offered as a cross-source relation — 96.9 % of the projection's chosen pairs shared a source page with their subject on a 525-page vault before the fix, 0 % after.
  • The release was reviewed before it shipped. The independent pass over the four risky files found one correctness defect (a first-time page in a re-ingest dropped the same-note exclusion) and five smaller ones; all six are fixed in this release, on the branch, with tests.

What's in this release

Added

  • Dutch, Polish and Thai. Full 797-key string tables, the four page-section label sets, four wiki-output files and four READMEs (docs/README_NL.md, _PL.md, _TH.md). A guard, wiki-output-language-parity.test.ts, fails when a selectable language is missing any of the four surfaces. (#1048)
  • The cross-source projection (Issue #729 Phase 1). Two pages are related when the vault's own link structure joins them — A → E and B → E, so A — B. Zero model input, no extra model calls, computed from the same graph the query path uses. (#781)
  • A runtime-only field never reaches disk. llmReady was persisted to data.json on every settings save although it is derived on every load. A new registry of runtime-only fields blocks any write path from serializing it, and a test fails when a write path bypasses the registry. (#1016)

Changed

  • A widely cited target no longer counts as evidence. A shared target counts only when CO_CITATION_SPECIFICITY (25) or fewer pages cite it, and one such target is enough — the gate replaces the count floor rather than adding to it. Measured on two vaults: hub-rest share falls from 69.2 % to 34.7 % on a 2,141-page vault, pages with candidates rise from 1,874 to 2,027, and the share of entries starting with "A" stays at or below the vault's base rate. K = 25 is a judgement, recorded as one in CO_CITATION_SPECIFICITY. (#1028, step 2)
  • A tie in the cross-source projection is broken by evidence rarity, then by page degree. The path used to decide 37–73 % of cuts; it now decides 9.1–11.6 %. (#1028, step 1, #1046)
  • The hub-link-density section and Fix All read the Related headings this plugin actually writes. Both compared against heading names the write path never emits, so the section was empty on every vault this plugin produced, and Fix All never had an input. Both now take the two localized headings from the section labels and keep the legacy names readable. (#1034)
  • Moved pages reaches the ingest log. Each entry carries the address the page has now, the address it left, and the classification that decided it. The old address is plain text, because a link to it would be dead the moment it was written. (#677, second half)
  • The two hub sections are disambiguated. hub-link-density measures what neighbours link to; crystallized hubs measure linking backwards. Neither list implies the other; the section header says so, in all fourteen locales. (#1025)
  • Three experimental-flag deadlines moved 1.32.0 → 1.34.0 (legacyScorer, skipMentionOnlyCandidates, gateDissentStubs), with the reason recorded in code, in docs/EXPERIMENTAL-FLAGS.md and in the changelog. Removing a flag in a MINOR with no measurement behind it is the wrong move, and legacyScorer is a MAJOR trigger.

Fixed

  • A cross-source projection adds to a page instead of taking a note's slot (#664, second half). The bounded addition shipped above replaces by arrival order, and a projection shapes last — so a page that filled the note ceiling gained nothing from cross-source. Projected entries are named as they are shaped and carried to the writer, admitted above the ceiling by an allowance the projection itself sized: a page keeps at most total note-grounded entries and may hold the projection on top. (#1039)
  • Related lists stop accepting new entries at the page budget (#664, first half). On @DocTpoint's replay of a 3,071-page vault, the fourth-onward notes refused 98.4 % of offered entries; 196 of 295 multi-note pages ended at the ceiling. Additions now stop at RELATED_BUDGET[granularity].total. Entries already in the file are never dropped — a cut needs an ordering, and the ordering belongs to #729 Phase 2. (#1032)
  • A rebuild can project cross-source relations (#1018). The run's co-citation graph is built once and never followed the writes, on an empty vault every later note read a graph without what it had already written. The graph now takes each written page's edges as it is written. Second half: a page being written has no graph entry, so the shaper now passes the links the page is about to carry, resolved against the same resolver its wikilinks use — hence passes equal exactly the set the writer will link.
  • A same-note pair is not a cross-source relation, and the source page is never offered (#1017). Before: 96.9 % of a projection's chosen pairs shared a note's source with their subject; after, 100 % of chosen entries are cross-source.
  • A first-time page in a re-ingest is again outside the same-note exclusion (v1.32.0 review, P1). The exclusion read the subject's source set from the graph only; a page being written had no graph entry, the set was empty, and the exclusion could not fire. The engine now hands the gate the note it knows.
  • An entity and a concept that share a name both keep the projection above the ceiling (v1.32.0 review, P2). The map records each page under <kind>:<nameKey> instead of nameKey alone.
  • A page whose rename cannot be re-read is at least marked, and the move is reported regardless (v1.32.0 review, P2). The branch marks the conflict on the moved page, resolves to the new address, and reports the move whether the frontmatter write succeeds or throws.
  • A failed ingest now names the pages it moved (v1.32.0 review, P2). The failure path writes no ingest log; it now enumerates the staged moves instead of clearing them silently.
  • A moved page is not an edited note (#677, first half). Every page moved through the classification decision carried a link-length delta; the drift check hashed the literal body, so untouched notes reported stale. Pages now carry a second fingerprint of the same body with every wikilink reduced to its display text: unchanged, links-only, or edited. (#1037)
  • A source page no longer carries sources: (#1038). On entities/ and concepts/ the key lists the source pages that support the page; on sources/ it listed the pages the source created — opposite direction, duplicative of source_file: and the body. Two origins make drift detection answer unknown, and 6 of 18 source pages on one vault were affected. The schema no longer offers the field; the constraint pass drops it on source pages. (#1044)

Dependencies

  • devDependencies: vitest 5.0.5 → 5.1.0 (#1041); vite 8.3.8 and jsdom 31 (#1045). No runtime dependencies changed.

Upgrading from v1.31.0

One-click update via Obsidian Settings → Community plugins. Your wiki, your settings and your data.json are untouched: no setting was renamed or removed, no command id moved, minAppVersion stays 1.11.4, and the page format is unchanged.

  • data.json: an existing llmReady key loads normally and is ignored now; the write no longer happens.
  • Moved flags: nothing you do is required; the switches you have keep working until 1.34.0.
  • Dutch, Polish and Thai: if your interface or wiki output was falling back to English, setting the language again is enough — both are single dropdowns.
  • If your vault has many pages ≥ the budget: nothing is removed; the list simply stops growing until #729 Phase 2 adds the truncation order.

What's accepted (and why)

  • Obsidian Bot pre-review passed twice — on the release commit and again on the HEAD after the review fix. Both scans returned no findings.
  • The independent code review over four files (co-citation.ts, related-shaping.ts, related-sections.ts, path-resolution.ts) found one P1 and five P2s — the P1 is why the release branch is two commits ahead of the originally reviewed tree, and why the second Bot scan was requested rather than assumed. All six are fixed with RED-first tests.
  • strict-void-return stays off. It names 18 pre-existing sites the Bot does not report. Turning it on during a release would put 18 unrelated edits in the release commit; it is tracked, not ignored.
  • eslint-plugin-obsidianmd 0.5.1 is what the Bot ran against; 0.6.0 is out and is not part of this release.
  • The specificity gate's K = 25 is a judgement made in one named constant with the measurements beside it. Only the 20/25/30/40 band was measured, on two of the three maintained vaults.
  • #729 Phase 1's allowance has a known yield trade-off: the same-note exclusion reduces the chosen pool by design. What ships is the honest version of that choice, measured.
  • Gate 1 on the release branch, all seven checks green: lint clean, arch clean (316 modules / 1,150 import edges / 0 cycles), tsc --noEmit 0, typecheck:tools 0, build clean, 5,654 tests / 413 files, css-lint 0.

Installation

  1. From Obsidian — Settings → Community plugins → Browse → search "Karpathy LLM Wiki" → Install (or Update). Then toggle Enable.
  2. From the marketplace — community.obsidian.md/plugins/karpathywiki → Add to Obsidian.
  3. Manual — only needed for a specific version or without the in-app marketplace. Take main.js, manifest.json and styles.css from this release's assets and place them in <vault>/.obsidian/plugins/karpathywiki/.

Requires Obsidian 1.11.4 or later, desktop or mobile.

Configuration

Nothing needs configuring to get the fixes. Three things are worth knowing:

  • The Related-list behaviour is configured by nothing. No new setting; the budget, the gate K and the exclusion are constants, not knobs. The next steps live on #729 Phase 2.
  • Settings → Wiki Configuration → output language and Settings → Interface language — pick Nederlands, Polski or ไทย if either was falling back before.
  • Experimental switches — the three that this release extended (legacyScorer, skipMentionOnlyCandidates, gateDissentStubs) now retire at 1.34.0; nothing else about them changed.

Tests

5,654 tests passing (413 files). Up from 5,408 / 404 at v1.31.0. The additions that matter are the ones built to fail first: the parity guard that found three selectable-but-silently-degraded languages, the "the projection exceeds the note ceiling but keeps its bounds" wiring tests, the six review-fix tests (a same-note caller-supplied set, a same-name entity/concept pair, two rename failure modes, a failed-run move trace), and the empty-boundary pins on the specificity gate.

Contributors

  • @green-dalii (Greener-Dalii) — Maintainer. This cycle: the co-citation projection and its floor, comparator and gate (#1027, #1046, #1029), the page budget and the projection's above-ceiling allowance (#1032, #1039), the same-note exclusion (#1017), the moved-page drift fix and log row (#1037, #243afee7), the source-page sources: removal (#1044), the density headings (#1035), the two-hubs disambiguation (#1036), the fourteen READMEs and the three new languages (#1048), the runtime-only persistence registry (#1031), instrument-tree type-checking wired into Gate 1 (#1026), the release-review fixes, and the three deadlines moved to 1.34.0 (#933).
  • @DocTpoint — Reported #664 and #677, with the measurements that shaped both: his 3,071-page vault replay (refusal rates rising from 1.3 % on the first note to 98.4 % on the fourth-onward) and the "a moved page is not an edited note" drift pair. Both features exist because of that evidence.
  • @dependabot — PRs #1041, #1045.

Full Changelog

1.31.0...1.32.0