5 Commits

Author	SHA1	Message	Date
Peter Steinberger	871c9e5286	fix(heartbeat): telegram accountId + cron jobId compat (#516, thanks @YuriNachos)	2026-01-08 20:47:22 +01:00
Yurii Chukhlib	4dac298ae2	fix(cron): use jobId parameter instead of id for AI tool schema ... Fixes parameter mismatch between AI tool schema and internal validation. The TypeBox schema now uses `jobId` for update/remove/run/runs actions, matching what users expect based on the returned job objects. Changes: - Changed parameter from `id` to `jobId` in TypeBox schema for update/remove/run/runs - Updated execute function to read `jobId` parameter - Updated tests to use `jobId` in input parameters The gateway protocol still uses `id` internally - the tool now maps `jobId` from the AI to `id` for the gateway call. Fixes #185 Co-Authored-By: Claude <noreply@anthropic.com>	2026-01-08 20:47:22 +01:00
Marcus Neves	67e1452f4a	Cron: normalize cron.add inputs + align channels (#256) ... * fix: harden cron add and align channels * fix: keep cron tool id params --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>	2026-01-06 02:09:48 +00:00
Peter Steinberger	a322075764	fix: use id for cron tool params	2026-01-05 02:15:11 +01:00
Clawd	17665d1732	fix(cron): pass 'id' instead of 'jobId' to gateway ... The cron tool was passing { jobId } to the gateway for update/remove/run/runs actions, but the gateway protocol schema expects { id }. This caused validation errors when trying to update or remove cron jobs via the tool. Fixes the parameter name while keeping the external tool API unchanged (still accepts 'jobId' from callers).	2026-01-04 17:18:29 +01:00