luigidemasi commented on issue #167:
URL: https://github.com/apache/camel-kit/issues/167#issuecomment-6874292688

   Closing the initial existing-project acceptance scope. The merged 
fixture/worked example from #175 is retained, and the additional integrated 
workflow has now been exercised.
   
   **Recorded live acceptance — 2026-11-13:** Kit 
`a32ed765c743c5bf8d8b59bdb3bbbe99a21a48e7`, Camel **4.22.1**, Spring Boot 
**4.1.1**, YAML, JUnit 6, Temurin **21.0.8**, Codex CLI **0.168.0**. A separate 
before-state was prepared from the fixture for this combination before 
adoption; versions and dependencies were then frozen throughout the 
enhancement. The original 4.8 application was preserved.
   
   The installed workflow completed **design → explicit human approval → plan → 
execute → validate**, adding `GET /api/orders/{orderId}` backed by an HTTP 
service, with ID validation, bounded requests and safe failure responses.
   
   - Clean baseline: **3/3 existing tests passed**. Final suite: **16/16 
passed**, including all three original tests, with zero failures/errors/skips 
and comparison by test identity.
   - Separate running application: **17/17 HTTP probes passed**. A 
32→33-character boundary mutation failed the expected test; exact source 
restoration was followed by a passing final suite.
   - Preservation: the 169-file post-adoption manifest showed only the approved 
properties append plus two new application files. The original properties 
remained an exact prefix; unrelated source/build files and dependency versions 
were unchanged.
   - Dry-run was non-mutating; actual reinitialization of a separate 174-file 
copy preserved original/enhanced application files and custom agent, 
constitution, MCP and additional skill content.
   - The recorded baseline bundle and three-file patch reproduced the tested 
source hashes. A separate public example or raw transcript publication is not 
needed; the existing checked-in fixture and worked example remain available.
   
   **Limits:** the outcome was `COMPLETE_WITH_LIMITATIONS`, not production 
readiness or an unconditional whole-project security/quality pass. Historical 
pre-edit static-analysis results and Forage cache coverage were unavailable; 
unsupported guide commands were recorded, with separate pinned-schema/MCP and 
actual application checks used. Authentication/deployment hardening, other 
runtime/version combinations, other DSLs and multi-module workflow acceptance 
were outside this run. The seven tests in the public Camel 4.8 fixture are a 
separate evidence set and are not this 16-test live run.
   
   The [worked-example 
page](https://camel.apache.org/camel-kit/next/existing-project.html) and its 
incoming links from getting started, Brainstorm and the pipeline were verified 
live on 2026-11-14. **Website impact: required; existing documentation is 
published.** The remaining tested-version/evidence clarification is tracked in 
#179.
   
   [CAMEL-26926](https://issues.apache.org/jira/browse/CAMEL-26926) is fixed 
upstream by [apache/camel#29854](https://github.com/apache/camel/pull/29854); 
Kit still pins MCP 4.22.1, so the merge does not establish a fixed default 
runner or older-target acceptance. This does not invalidate the scoped 4.22.1 
result above.
   
   Tests were not rerun solely for this closure; the results above come from 
the retained November 13 acceptance evidence.
   
   _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]

Reply via email to