kotlin-jvm-engineeringlisted

# Kotlin/JVM Engineering ## Establish The Project Contract 1. Read `AGENTS.md`, `.codex/steering/kotlin-jvm-steering.md` when installed, closer-scoped guidance, module documentation, Gradle settings, and the affected build files. 2. Use the checked-in Gradle wrapper and identify the Java toolchain, Kotlin JVM target, plugin and dependency-management approach, test framework, formatting/linting tools, and CI commands. 3. Inspect neighboring source and tests before introducing a new package, abstraction, dependency, or convention. 4. Identify any public Kotlin, Java, serialization, configuration, CLI, or service contract affected by the change. 5. Treat generated sources as outputs. Change their source schema or generator, then regenerate. ## Fit The Existing Project - Preserve the established architecture and module boundaries unless the task explicitly changes them. - Keep core behavior independently testable and keep external I/O or framework integration at clear boundaries where relevant. - Keep entrypoints and adapters focused on input mapping, behavior invocation, and result mapping. - Keep library APIs narrow; hide implementation details with private or `internal` visibility. - Avoid cyclic dependencies, catch-all utility packages, speculative abstractions, and wrappers that add no meaningful boundary. - Do not introduce or replace a framework, serialization library, persistence tool, DI container, or logging stack without a concrete requirement.