Contributing

Contributions should improve the toolkit without weakening CPI compatibility or security practices.

Good contribution areas

• documentation improvements
• build and packaging enhancements
• new plugin examples
• tests and validation utilities
• bug fixes in core abstractions
• clearer package examples

Development notes

• Keep package dependencies explicit.
• Preserve CPI-friendly Groovy and bytecode targets.
• Avoid adding runtime dependencies that make CPI deployment harder.
• Keep secrets out of tests and examples.
• Prefer small, reviewable changes.

Before opening a pull request

• Build the affected package.
• Run relevant tests.
• Update docs if behavior changes.
• Include examples for new package/plugin patterns when helpful.