luigidemasi opened a new issue, #167: URL: https://github.com/apache/camel-kit/issues/167
## Description Provide the integrated acceptance evidence and public worked example for #164. Use one representative existing Camel application to demonstrate adopting Camel Kit and adding a meaningful integration capability through the complete workflow. ## Expected behavior Share the fixture with the safe-adoption, discovery/compatibility and feature-scoped workflow tasks. Start from an application with existing behavior and tests, establish its baseline, complete design -> plan -> execute -> validate, and verify the new capability alongside existing behavior. ## Acceptance criteria - [ ] A reproducible existing Camel 4 application with YAML routes and one currently supported runtime has baseline behavior and tests. Record the exact tested runtime/version combination. - [ ] The fixture completes safe adoption and the approved workflow to add a meaningful integration capability; evidence demonstrates the capability works. - [ ] Existing checks are rerun, pre-existing failures are distinguished from regressions, and unavailable checks are reported explicitly. - [ ] Verification confirms unrelated files, existing dependency versions and DSL remain unchanged and reinitialization preserves customizations. - [ ] Public documentation in `docs/modules/ROOT/**` includes setup, safe adoption/conflict handling, the worked example, supported combinations and known limitations. - [ ] Getting started, Brainstorm and the workflow overview link to the existing-project workflow/example. ## Scope and coordination Parent: #164. Initial scope: an existing Camel 4 application with YAML routes and one currently supported runtime. Broader runtime, DSL and project-layout coverage remains follow-up work. Fixture and documentation preparation can start alongside the implementation tasks; final acceptance requires their integrated behavior. Each implementation task remains responsible for its own focused tests. Coordinate with Jinal-Sarvaiya's existing work linked from #164. #164 remains the parent and must stay open until its complete acceptance criteria are met. Completing a single implementation task does not complete the parent. ## Website impact **Required.** This is the documentation follow-up for the implementation sub-issues of #164. Publish the content through the existing Antora component in `docs/modules/ROOT/**`. _AI-generated by Codex on behalf of @luigidemasi._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
