Assembled read-only for @jeswr. Nothing has been posted, labelled, closed, or pushed — every proposed comment below waits for a ticked checkbox. Supporting memos: repo health, TypeScript migration.
N3.js is in good release shape — semantic-release from main works, runtime dependencies are clean, and the 100% coverage gate plus the 40-job W3C spec matrix are strong quality gates — but the one thing actively hurting day-to-day operation is spec-test flakiness (#609), a diagnosed rdf-test-suite cache race that strands dependabot automerge (#610) and can silently skip releases. The backlog itself is healthier than it looks: 18 small fixes have verified root causes (several with