luigidemasi opened a new issue, #179: URL: https://github.com/apache/camel-kit/issues/179
## Description Follow-up to #164 and #167: update the existing-project guide with the additional verified live-workflow combination and the version-specific catalog limitation. Reuse the existing fixture and worked example; no second example repository, acceptance bundle or raw agent transcript publication is required. The public guide currently describes the Camel 4.8.0 / Spring Boot 3.3.4 application fixture and its seven application tests. A separate local integrated run on 2026-11-13 used Kit `a32ed765c743c5bf8d8b59bdb3bbbe99a21a48e7`, Camel 4.22.1 / Spring Boot 4.1.1 / YAML / Temurin 21.0.8 and completed design → human approval → plan → execute → validate. It passed 3 baseline tests, 16 final tests and 17 HTTP probes, with preservation and reinitialization checks. These are distinct evidence sets. [CAMEL-26926](https://issues.apache.org/jira/browse/CAMEL-26926) is fixed on Camel main by [apache/camel#29854](https://github.com/apache/camel/pull/29854), but Kit still pins `camel.mcp.version=4.22.1` at this check. The merge does not change that installed runner or establish end-to-end acceptance for older-target Spring Boot or Quarkus applications. ## Acceptance criteria - [ ] Update `docs/modules/ROOT/pages/existing-project.adoc` to distinguish fixture-level 4.8 tests from the recorded 4.22.1 live workflow and link the acceptance summary in #167. - [ ] State the verified combination and `COMPLETE_WITH_LIMITATIONS` outcome. The local example is not production certification; historical pre-edit static-analysis results were unavailable, and recorded schema/endpoint checks used working alternatives to unsupported guide commands. - [ ] Document the runtime-catalog limitation for the pinned MCP version and link CAMEL-26926. Tell users to stop version-bound validation when the catalog differs from the requested/resolved target; do not recommend silently upgrading the application. Recheck artifact availability and behavior before claiming a fixed MCP combination. - [ ] Keep broader runtime, DSL and multi-module workflow coverage explicitly outside the measured acceptance; verify the updated Antora page and relevant links after publication. **Website impact: required.** The existing guide and incoming links are already live. This follow-up owns the remaining evidence/version clarification, not a new example or a runtime implementation change. _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]
