davsclaus opened a new pull request, #26740: URL: https://github.com/apache/camel/pull/26740
Fixes https://issues.apache.org/jira/browse/CAMEL-24897 (part of CAMEL-24886) `camel_write_file` had a boolean `validate` argument, default true, and its refusal message ended with "(validate=false writes it anyway)". In the camel-jbang-mcp stepwise benchmark the local model set `validate: false` on its own: 9 of 26 writes in series s6, 26 of 337 in s3, often on the first write of a step with no refusal to provoke it. The invalid file then reloaded, the app ran without routes (a single route file has nothing to restore), and the model read the validator's report from the log instead of getting it from the write. The flag existed for a person who knows better; for an agent it is a bypass of the one deterministic check we have. The argument is gone from the shared tool definition, the MCP wrapper and the camel-jbang views' registry, the write always validates, and the refusal message no longer offers the bypass. `writeFile(ctx, dir, file, content, validate)` keeps its signature for other callers. Tests and the two doc pages updated, upgrade note added. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj -- 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]
