Jinal-Sarvaiya commented on code in PR #119:
URL: https://github.com/apache/camel-kit/pull/119#discussion_r4361209662
##########
camel-kit-core/src/main/resources/skills/shared/mcp-setup.md:
##########
@@ -127,22 +154,28 @@ The runtime affects which components are returned (e.g.,
Quarkus extensions vs S
### Rule 3: Bind catalog results to the resolved Camel version
-Before consuming catalog detail or list fields, call
`camel_catalog_components` with `limit=0` and the same `runtime`
-and full `platformBom` GAV. Its successful result includes the catalog's
resolved `camelVersion` without returning a
-component payload; require that value to match the project's resolved Camel
version. Record that probe and the exact call
-arguments as the version binding for subsequent catalog calls that use the
same runtime and BOM.
+The version binding comes from `.camel-kit/config.properties`
(`project.runtime`, `project.camelVersion`,
+`project.platformBomVersion`). Always pass `runtime` and the full
`platformBom` GAV derived from these properties on
+every catalog call — those parameters **are** the binding. A call without them
is answered from the catalog bundled in
Review Comment:
Done. Updated all three failing ResourceConsistencyTest methods. Replaced
limit=0 probe assertions with config.properties binding text. Updated evidence
line in designSpecsRecordCatalogEvidenceInSectionFive to runtime=[runtime];
platformBom=...; source=.camel-kit/config.properties. Added knowledge-server
routing regression coverage (camel_docs_search + camel-knowledge server
assertions in both ironLaws and mcpSetup checks). All 29
ResourceConsistencyTest and 9 ShippedAssetStructureTest tests pass.
--
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]
