Kotlin Power-assert

Step 1: Define the diagnostic contract

1. DEFINE enable plugin | select function | select compilation | improve assertion expression | author assertion API | soft assertions | Maven integration | migration | missing diagram | intrinsic failure.
2. IDENTIFY modules, Kotlin targets/compilations, build system, Kotlin/KGP version owner, assertion functions and overloads, test/runtime source sets, library consumers, and expected failure output.
3. READ the current Power-assert guide, component stability, and Kotlin release/migration notes before adoption or upgrade. Power-assert is Experimental; obtain explicit acceptance for production/library API reliance.
4. PRESERVE the repository's plugin/version ownership, test framework, assertion semantics, source-set hierarchy, and failure type unless the request changes them.
5. ROUTE general build/toolchain work to kotlin-gradle, source/test behavior to kotlin-development, and target/source-set design to kotlin-multiplatform.

Completion: owning module, transformed compilations/functions, failure semantics, stability acceptance, version owner, and proof command are explicit.

Step 2: Inspect current integration

RUN from the target repository root:

python3 scripts/inspect-project.py --root . --json