luigidemasi commented on issue #164: URL: https://github.com/apache/camel-kit/issues/164#issuecomment-6874297305
Closing the initial YAML / single-runtime existing-project workflow scope. - Safe adoption/reinitialization, discovery/version handling and feature-scoped workflow implementation are complete in #168, #169 and #170. - #167 is now closed with the [integrated acceptance summary](https://github.com/apache/camel-kit/issues/167#issuecomment-6874292688): the installed design → approval → plan → execute → validate workflow passed on Camel 4.22.1 / Spring Boot 4.1.1, with 3 preserved baseline tests, 16 final passing tests, 17 HTTP probes, scope/file/version preservation, reinitialization checks and a caught/restored boundary mutation. - The existing fixture and worked example are already checked in. The [public guide](https://camel.apache.org/camel-kit/next/existing-project.html) and its incoming getting-started, Brainstorm and pipeline links were verified live on 2026-11-14. A second example publication is unnecessary. The acceptance is explicitly `COMPLETE_WITH_LIMITATIONS`; it does not certify production readiness, older-target Spring Boot, Quarkus, other DSLs or multi-module workflows. The detailed summary separates the 4.8 fixture tests from the 4.22.1 live run and records unavailable checks. CAMEL-26926 is merged upstream, while Kit's default MCP pin remains 4.22.1. **Website impact: required.** The remaining tested-version table and catalog/evidence clarification is carried by the linked documentation follow-up #179; the existing feature guide is published. Broader runtime coverage remains follow-up work, as stated in this issue's initial scope. No tests were rerun for closure; this records the verified November 13 evidence and today's publication/status checks. _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]
