luigidemasi opened a new issue, #84: URL: https://github.com/apache/camel-kit/issues/84
> Imported from [luigidemasi/camel-kit#193](https://github.com/luigidemasi/camel-kit/issues/193), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-08-26. > Closed by [luigidemasi/camel-kit#195](https://github.com/luigidemasi/camel-kit/pull/195), merged on 2026-08-28. --- ## Description Update the README and related public documentation to match the current CLI, generated assets, workflow behavior, and published installation channels. The README is broadly accurate, but several statements have drifted from the implementation. One underlying plugin defect must also be addressed because documentation alone cannot make the advertised plugin workflow functional. Website impact: **unclear pending review**. Compare the website with the corrected public behavior and record either `required` or `not required` before closing this issue. ## Steps to Reproduce 1. Install the Camel JBang plugin using the documented `:LATEST` coordinate. 2. Compare the resulting command and agent surface with the README Quick Start. 3. Initialize a project through `camel kit init`. 4. Start a greenfield workflow that requires `camel kit nextId`, or reach a pipeline stage that invokes `camel kit doc`. ## Expected Behavior - Documented installation methods expose the described agents, options, and commands. - Generated workflow commands resolve through the selected command prefix. - Prerequisites, supported environments, workflow stages, and generated assets are described accurately. ## Actual Behavior - Maven Central `LATEST` resolves to 0.3.1, while the README primarily describes the nine-agent, Bob 2-default `0.3.2-SNAPSHOT` behavior. - The current Camel plugin registers `init`, `doctor`, `graph`, `plan`, and `ship`, but omits the required `doc` and `nextId` commands. - Docker and the Linux/Pi/Node/Camel-Main-YAML Ship constraints are missing from the prerequisites. - Gemini, Qwen, and OpenCode MCP configuration paths are stale. - `/camel-validate`, `/camel-start`, and the pipeline-phase descriptions no longer match their complete behavior. - `graph migration-context` overstates traversal completeness and direct Knowledge MCP integration. - The Knowledge description still mentions errata ingestion. - Bob 1's monolithic gate variants are not distinguished from the shared-skill architecture. ## Acceptance Criteria - [ ] Register `doc` and `nextId` under `camel kit` and add command-parity regression coverage. - [ ] Clearly distinguish stable and snapshot installation channels and their supported command/agent surfaces. - [ ] Avoid implying that `:LATEST` provides current-main behavior. - [ ] Document Docker as conditional infrastructure for full Citrus/Testcontainers verification. - [ ] Document Ship's current Linux, Pi, Node, and Camel Main/YAML requirements. - [ ] Correct the Gemini, Qwen, and OpenCode MCP configuration paths. - [ ] Correct the `/camel-validate`, `/camel-start`, execution, and pipeline-stage descriptions. - [ ] Describe `migration-context` as bounded local graph output rather than a complete dependency/MCP bridge. - [ ] Replace the obsolete errata claim with current CVE ingestion behavior. - [ ] Qualify Bob 1's monolithic gate architecture and clarify the generated-assets table. - [ ] Align affected linked guides. - [ ] Review corresponding website content; update it or record why website changes are not required. - [ ] Recheck all public and repository-relative links. ## Additional Context Verified against the tree of current `main` at merge commit `279e8ffd`. Relevant implementation areas: - `camel-jbang-plugin-kit/src/main/java/io/github/luigidemasi/camelkit/jbang/CamelKitPlugin.java` - `camel-kit-core/src/main/java/io/github/luigidemasi/camelkit/CamelKitMain.java` - `camel-kit-core/src/main/java/io/github/luigidemasi/camelkit/command/InitCommand.java` - `camel-kit-core/src/main/resources/skills/` - `camel-kit-core/src/main/resources/agents/registry/` - `camel-kit-core/src/main/resources/workflow/camel-kit-workflow.yaml` -- 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]
