test: fix gateway workflow webhook integration cooldown

[henrypark133]

Summary

• set the gateway webhook workflow test routine cooldown to 0
• document that the test intentionally fires the same routine via event_emit and webhook back-to-back
• keep production routine cooldown behavior unchanged

Root cause

The test created a system_event routine, fired it once via , then immediately asserted that the webhook path would fire it again. With the routine_create default , the second trigger was correctly suppressed, so the test expectation was stale.

Verification

• cargo test --features libsql gateway_workflow_harness_chat_and_webhook --test gateway_workflow_integration -- --nocapture
• cargo test --features libsql web_toggle_disables_system_event_routine_without_restart --test gateway_workflow_integration -- --nocapture

[gemini-code-assist]

Code Review

This pull request updates the integration tests in tests/gateway_workflow_integration.rs by setting cooldown_secs to 0 for a specific routine. This change ensures that the cooldown mechanism does not suppress events when the routine is triggered consecutively via event_emit and the webhook endpoint during the test execution. I have no feedback to provide.

[Copilot]

Pull request overview

Updates the gateway workflow integration test to avoid routine cooldown suppressing a second, immediate trigger, while leaving production cooldown behavior unchanged.

Changes:

• Set the test-created system_event routine’s cooldown_secs to 0 to allow back-to-back triggers.
• Added an inline comment documenting that the test intentionally triggers the same routine via event_emit and the webhook endpoint sequentially.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.