I'd like to simplify code in the adapters we ship by making them standalone files with little to no indirection, creating the CRI event data explicitly inline.

The aim is:

• Easier debugging for us.
• Serve as fully understandable/self-documented example how CRI works based on a framework the reader is familiar with. (No indirect property creation.)
• Make the code easy to be copied by people to use in other projects.
• Make the code easy to be integrated into the very package it is currently adapting for.

We can still use helpers to calculate values for some properties, but I'd like the object shapes to be completely owned by each eadapter.