Kgnot/spring-kernel-architecture — reverse-engineered prompt

Build me a small Java Spring demo that shows a plugin based microkernel architecture in a way that’s easy to understand and run locally.

I want a central kernel that owns the main rules and lifecycle, and separate plugins that can be added without changing the core. Make it feel like a real backend app, not just a toy loader. It should include a basic app layer, shared models or utilities, database persistence, notifications, RabbitMQ based messaging, and websocket updates so I can see events flow through the system. Add one or two example plugins that do something simple but useful, like reacting to events and sending a notification.

Please include a few endpoints so I can test the main flow, register or trigger plugin behavior, and confirm that the core stays independent from the plugin features. Keep the setup straightforward, with sensible defaults, sample data if needed, and clear instructions for how to start everything and verify it works. If something is unclear, check current docs online and make reasonable choices.