[emaarco]

Why

bpmn-to-code 6.x replaces the per-category nested classes (Elements, Variables, ServiceTasks, Messages, Errors) with a node-centric API. Staying on 5.2.0 keeps this blueprint out of step with the sibling engine blueprints that are already on 6.6.1.

What

• Bumps bpmn-to-code.version from 5.2.0 to 6.6.1 (plugin, bpmn-to-code-runtime, bpmn-to-code-testing).
• Regenerates adapter/process. It now holds *ProcessApi with FlowNodes.<Node> plus the shared ServiceTasks, Messages, ProcessVariables, Errors and Escalations files. Element ids are unchanged.
• Migrates the workers, LeasingProcessAdapter, TaskInboxAdapter, EngineApiConfiguration and the tests:
  • Elements.X.getValue() becomes FlowNodes.X.ELEMENT_ID
  • Variables.<Node>.X becomes FlowNodes.<Node>.Variables.X
  • ServiceTasks/Messages/Errors are now imported from the shared files
• TimerUtils.fireTimer now takes a FlowNode (same as the cibseven blueprint).
• ServiceTaskExternalTopicRule checks TaskImplementation.ExternalTask instead of the removed engine-specific property map. The validation test now uses ValidationRule.
• Excludes the new shared generated classes from PIT, the same way *ProcessApi* is already excluded.
• Updates README and AGENTS.md to describe the 6.x API.

Verification

• ./mvnw -B verify passes: 155 tests, 0 failures. That covers the architecture, unit, process and model-validation tests plus checkstyle.
• After the build, git status shows no drift in the generated adapter/process sources.