wow-developlisted

# Develop Wow Applications ## Scope gate Use only for a downstream application; the Wow framework repository and its modules never qualify. Require scoped `me.ahoo.wow` imports, `wow-*` dependencies, or an explicit downstream request to use, adopt, configure, or explain Wow. Routine same-major non-breaking upgrades qualify; cross-major upgrades, known source/configuration/generated/runtime breaks, and Wow-managed storage/data changes belong to `wow-migrate`. Checkout-wide markers, negated/comparative mentions, and generic Kotlin, Java, Spring, Reactor, DDD, CQRS, or Event Sourcing vocabulary do not qualify. Otherwise state that this Skill does not apply and stop using it. Own the complete development task. Do not route to another Wow Skill. ## Contract - Treat the current checkout, its tests, generated contracts, and resolved dependencies as authoritative. - Treat commands as intent, domain events as committed facts, and sourced state as reconstructed memory. - Keep aggregate invariants inside the aggregate boundary and external side effects outside it. - Preserve reactive execution, serialization compatibility, module boundaries, and public contracts unless the user authorizes a breaking change. - Keep read-only requests non-mutating; enter test-first implementation only for requested code or document changes. - Use RED→GREEN→REFACTOR for behavior changes. If a change is not testable at the unit level, name the narrowest replacement evidence before editing. - Report sou