Provenance Record

Well-structured Briefing with clear section headers (Overview, What We Know by subsystem, What We Don't Know). Technical depth is appropriate for a developer audience, code examples are syntactically correct and match the primary Kotlin documentation. The body is 205 words over the Briefing cap, which is a quality and policy concern rather than a factual one.

Three sources cited; I fetched all three. (1) https://kotlinlang.org/docs/whatsnew2320.html — PRIMARY SOURCE, fully supports every technical claim in the article: March 16 2026 release date, name-based destructuring with -Xname-based-destructuring and three modes (only-syntax, name-mismatch, complete), BTA default on Kotlin/JVM with CancellableBuildOperation, Gradle 7.6.3-9.3.0 compatibility, checkLegacyAbi/updateLegacyAbi renamed to checkKotlinAbi/updateKotlinAbi, Maven stable with <extensions>true</extensions>, Lombok Experimental to Alpha, kotlin.plugin.jpa auto-applying all-open with JPA preset (javax.persistence and jakarta.persistence Entity/Embeddable/MappedSuperclass), Wasm '4.6 times faster string interpolation', 5% smaller binaries, '20% faster StringBuilder.append()', 65% clean build / 21% incremental build improvements, @nativeInvoke with JsAction example, module instantiation breaking change replacing external _initialize(), -Xccall-mode=direct for C/Objective-C interop, crossCompilationSupported API, disableNativeCache replacing kotlin.native.cacheKind, Symbol-based TypeScript bridging, SWC via kotlin.js.delegated.transpilation=true, Map.Entry.copy() experimental API, io.vertx.codegen.annotations.Nullable support, @Unmodifiable/@UnmodifiableView warning in 2.3.20 escalating to error in 2.5.0, context receivers deprecation, and macosX64/tvosX64/watchosX64 Apple targets marked for removal next release. All confirmed. (2) https://blog.jetbrains.com/kotlin/2026/03/kotlin-2-3-20-released/ — PARTIALLY SUPPORTS CLAIMS. The blog post's actual content is very short: an opener 'The Kotlin 2.3.20 release is out! Here are the main highlights:' followed by bullets including 'Maven: Simplified setup for Kotlin projects.' Two direct quotes in the article — 'making Kotlin smoother to use across its target platforms' and 'easier to set up Kotlin in Maven build tool projects' — DO NOT appear in the blog post. Verified by WebFetch and a direct curl grep: 'smoother', 'smooth' (outside CSS), and 'easier to set up' all return zero matches. This is a factual/attribution error. (3) https://www.infoworld.com/article/4151375/kotlin-2-3-20-harmonizes-with-c-javascript-typescript.html — SUPPORTS CLAIMS. The three phrases attributed to InfoWorld were confirmed: 'match variables to property names instead of relying on position-based componentN() functions', 'interoperability mode for C or Objective-C libraries', and the InfoWorld characterization that the release 'lifts the limitation on implementing Kotlin interfaces on the JavaScript and TypeScript sides' (the article's 'lifting the limitation on...' is a grammatical adaptation of the same phrasing).

All technical facts (versions, percentages, API names, compiler flags, code examples, deprecation schedule) check out against the primary Kotlin documentation. The only factual-accuracy issue is the two fabricated direct quotes attributed to the JetBrains blog. The underlying statements are true; the problem is that they are framed as verbatim quotes from a specific source where those words do not appear.

High-quality, technically accurate release roundup built primarily on the Kotlin project's own What's New page, which verifies every substantive claim. Blocked from APPROVE by two fabricated direct quotes attributed to the JetBrains blog — a correctable misattribution rather than a systemic accuracy problem. Secondary concern: body is 205 words over the Briefing cap. Recommend REQUEST_CHANGES so the contributor can rephrase the two quoted passages and trim to the category limit.