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

   ## Description
   
   Kit already has a workflow manifest for commands, skills and stages. Extend 
this model so a module can declare the skills, resources and providers it 
contributes, and the build can validate the complete set before initializing a 
workspace. [Workflow 
manifest](https://github.com/apache/camel-kit/blob/79f145c6ebe41dbfdf05a505fca4e357b8ec4caf/kit/camel-kit-core/src/main/resources/workflow/camel-kit-workflow.yaml)
 ยท [Strict manifest validation 
(#62)](https://github.com/apache/camel-kit/issues/62)
   
   ## Acceptance criteria
   
   - [ ] Define stable pack and contribution identifiers, dependencies, public 
contract versions and the resources or provider entries required for each 
declaration. A pack containing only instructions must be valid.
   - [ ] Resolve additions, explicit replacements and exclusions into one 
effective catalog used by installation, command generation, workflow routing 
and Doctor. A pack must be able to add guidance or a check at a named workflow 
step while retaining the rest of the skill.
   - [ ] Show that changing module or resource enumeration order produces the 
same result. Duplicate identifiers, conflicting replacements, missing 
dependencies and incompatible contracts must fail the build with a diagnostic 
identifying the declarations involved.
   - [ ] With the default modules selected, verify that the resolved catalog 
preserves the current public commands and internal skill visibility.
   
   ## Website impact
   
   Required. Add the manifest format, composition rules, diagnostics and a 
minimal working pack to the contributor and architecture guides.
   
   _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