Armin Ronacher 8c0ccd14b3 fix(ai,agent,coding-agent): normalize null message content at ingestion boundaries (#6343) ... The Message types require content to always be present, but untyped JS extension tools, hand-built histories, and old or hand-edited session files can violate that contract, crashing rendering, compaction, and provider request conversion with 'content is not iterable'. Normalize null/missing content to an empty array at the ingestion boundaries instead of guarding every consumer: - transformMessages (choke point before every provider request) - createToolResultMessage in the agent loop - session entry loading (message and custom_message entries) - extension custom messages (sendCustomMessage, before_agent_start) - message_end extension replacements fixes #6259, fixes #6276		2026-07-06 20:47:08 +02:00
..
agent	fix(ai,agent,coding-agent): normalize null message content at ingestion boundaries (#6343)	2026-07-06 20:47:08 +02:00
ai	fix(ai,agent,coding-agent): normalize null message content at ingestion boundaries (#6343)	2026-07-06 20:47:08 +02:00
coding-agent	fix(ai,agent,coding-agent): normalize null message content at ingestion boundaries (#6343)	2026-07-06 20:47:08 +02:00
orchestrator	Add [Unreleased] section for next cycle	2026-06-30 22:29:44 +02:00
tui	test: use quiet dot reporters and show output only for failing tests	2026-07-05 23:17:17 +02:00