luigidemasi opened a new issue, #169:
URL: https://github.com/apache/camel-kit/issues/169

   ## Description
   
   Discover the existing application's actual structure and compatibility 
constraints before designing a new capability. Supply this context to the 
workflow without replacing it with distribution defaults.
   
   ## Expected behavior
   
   Inspect relevant modules, runtime, Camel/platform versions, DSL, routes, 
beans, configuration, interface contracts and tests. Reuse the existing graph 
where it provides coverage and inspect source where coverage is absent or 
incomplete. Ask only for unresolved information.
   
   Bind design and catalog checks to the detected runtime and versions. Do not 
silently upgrade dependencies or convert the DSL. Record the existing 
build/test baseline and distinguish pre-existing failures from later 
regressions.
   
   ## Acceptance criteria
   
   - [ ] Discovery records the actual runtime, versions, DSL, relevant 
modules/routes/contracts and build/test baseline for the representative 
application.
   - [ ] Missing or ambiguous information and unsupported combinations produce 
actionable results rather than guessed defaults.
   - [ ] Existing dependency versions and DSL remain unchanged; downstream 
checks use the discovered compatibility constraints.
   - [ ] Automated coverage exercises supported input, ambiguous/unsupported 
input and incomplete graph coverage, with focused regression coverage for 
existing discovery paths.
   
   ## 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.
   
   Coordinate interface-contract discovery with #111 and broader Java DSL 
support with #52; this task does not duplicate those broader efforts. Its 
output supplies the feature-scoped workflow. Coordinate implementation with 
Jinal-Sarvaiya's existing work linked from #164.
   
   ## Website impact
   
   **Required.** Document discovery behavior, supported combinations and 
actionable limitations in `docs/modules/ROOT/**`; the documentation follow-up 
is #167.
   
   _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