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

   > Imported from 
[luigidemasi/camel-kit#49](https://github.com/luigidemasi/camel-kit/issues/49), 
opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-06.
   > Closed by commit 
[2550cd9](https://github.com/luigidemasi/camel-kit/commit/2550cd9724f832415e66982d674e9745c494c283).
   
   ---
   
   ## Description
   
   The Bob brainstorm gate needs several optimizations to work reliably within 
Bob's 100K token context window. These were identified during testing of the 
dispatch system (luigidemasi/camel-kit#47) and are independently valuable.
   
   ## Changes
   
   ### 1. 100K context budget awareness
   Add context budget guidance to the gate header so Bob knows its token limits 
and prioritizes accordingly.
   
   ### 2. Mandatory Citrus test generation
   The plan and execute phases must explicitly require Citrus integration test 
tasks (YAML DSL format only, not Java or XML). Each route needs a corresponding 
test task with references to the test guides (`test-generation.md`, 
`test-runner.md`, `test-configuration.md`).
   
   ### 3. Valid command table
   Add an explicit table distinguishing user-invocable commands 
(`/camel-brainstorm`, `/camel-plan`, `/camel-execute`, `/camel-validate`, 
`/camel-ship`) from internal `switch_mode` targets (`camel-implement`, 
`camel-test`). Prevents Bob from hallucinating non-existent commands when 
context is exhausted.
   
   ### 4. Interview persistence
   Add step to write interview findings to `docs/interview-notes.md` so key 
decisions survive context condensation.
   
   **Note:** File naming convention enforcement and Qute escaping fixes are 
tracked in luigidemasi/camel-kit#50 (cross-agent).


-- 
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