The PR fixes a parser failure in Claude ambient tool calling where fields expected as u32 were sent as strings, causing ambient cycles to fail at deserialization and stop working.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Introduced custom deserializers that accept both string and u32 for numeric fields and applied them to EndCycleInput.memories_modified/compactions and wake_in_minutes in NextScheduleInput, ScheduleInput, and ScheduleToolInput, eliminating strict type-only parsing for these tool-call payloads.
Users and operators relying on Claude ambient tool calls can now keep ambient workflows running because calls that send numeric fields like `"0"` no longer break parsing and abort the whole ambient cycle, reducing complete mode outages after tool invocations. The technical fix is a dual-acceptance parser path for targeted u32 fields, applied only to a small set of schedule-related inputs. Next, watch whether similar stringified numeric fields appear in other tool schemas and track ambient-cycle failure/retry metrics after deployment to catch any remaining type-contract gaps.
Users and operators relying on Claude ambient tool calls can now keep ambient workflows running because calls that send numeric fields like `"0"` no longer break parsing and abort the whole ambient cycle, reducing complete mode outages after tool invocations. The technical fix is a dual-acceptance parser path for targeted u32 fields, applied only to a small set of schedule-related inputs. Next, watch whether similar stringified numeric fields appear in other tool schemas and track ambient-cycle failure/retry metrics after deployment to catch any remaining type-contract gaps.