Review - JSpecify

[CitralFlo]

My understanding of JSpecify for api - mostly used in Java-Kotlin communication. With NullMarked as clear way to display notnull by default. Nullmarks checked to second layer of services. Additional NotNull s from jetbrains required by intelliJ to not screen about parameter marks as notNull

[gemini-code-assist]

Code Review

This pull request introduces JSpecify annotations across the API to improve null-safety, which is a great step forward for code quality and Kotlin interoperability. The use of @NullMarked correctly sets non-null as the default for many interfaces and classes.

My review focuses on a few key areas:

• I've pointed out several places where collection return types are incorrectly marked as containing @Nullable elements, while their implementations guarantee non-null elements. This misrepresents the API contract and should be corrected.
• I've also raised a concern about removing runtime null checks from a public event constructor. While static analysis is helpful, runtime checks provide an essential safeguard against incorrect API usage from un-checked code.

Overall, the changes are positive, and addressing these points will further solidify the null-safety of the API.

[Jakubk15]

Overall good PR, minor tweaks required