luigidemasi opened a new issue, #53: URL: https://github.com/apache/camel-kit/issues/53
> Imported from [luigidemasi/camel-kit#92](https://github.com/luigidemasi/camel-kit/issues/92), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-23. > Closed by [luigidemasi/camel-kit#101](https://github.com/luigidemasi/camel-kit/pull/101), merged on 2026-06-24. --- ## Description The project currently relies on Markdown resources as part of the runtime contract: skill files, generated `AGENTS.md`, command stubs, MCP config templates, website/docs, and migration guides. Several stale tokens already exist across those resources, for example: - references to `.camel-kit/config.yaml` even though the implementation uses `.camel-kit/config.properties` - references to `graph_stats` MCP even though graph access moved to CLI commands - references to `/camel-design` as a user-facing entrypoint even though `/camel-start` is now the router - references to `/camel-verify` as a standalone primary command even though it is now mostly internal to `/camel-execute` - generated Knowledge MCP config listing tools that are not implemented by the server - stale wording such as "all 4 laws" while the current Iron Laws file defines six Because prompts/resources are a primary product surface for Camel-Kit, stale resource contracts can make agents follow the wrong workflow even when the Java implementation is correct. ## Expected Behavior The build should fail when skill/docs/templates contain known-stale contract tokens or references to commands/tools/config files that no longer exist. ## Actual Behavior The existing Java tests cover generators, graph commands, doc frontmatter, and plan analysis, but they do not currently validate the resource tree as a coherent product contract. ## Proposed Solution Add resource consistency tests that scan `camel-kit-core/src/main/resources`, `camel-kit/docs`, and relevant website/docs resources for stale or inconsistent references. Initial checks should include: - no `.camel-kit/config.yaml` references in active shipped skills/templates/docs - no `graph_stats` references in active shipped skills/templates/docs - no `/camel-design` as a user-facing next step - no generated MCP allowlist entries for tools not implemented by `KnowledgeMcpServer` - no outdated Iron Law counts - command stubs generated by `DefaultGenerator` match the skills intended to be exposed ## Acceptance Criteria - [ ] Add automated tests for shipped resource consistency - [ ] Tests fail on stale command names, config filenames, graph tool names, and Knowledge MCP tool names - [ ] Existing stale references are cleaned up or explicitly excluded if they are historical ADR/planning material - [ ] The test scope distinguishes active shipped resources from archived design notes -- 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]
