One honesty check, three languages.
The same D11 status-coverage rule that ships in furqan-lint v1.0.0 (al-Basirah) runs against your Python, Rust, or Go function in the textarea below. Real subprocess, real verdict, real diagnostic. No model in the loop.
The checker reads your function's declared return type, walks
the call graph one hop deep, and asks: does any callee
declare a may-fail union the caller silently narrowed?
That shape is the same defect across str | None in
Python, Result<T, E> in Rust, and
(T, error) in Go.
Switch to Diff to run the additive-only check
across two versions of the same module. Public names you remove
fire an additive_only marad.