Danny Avila 7dddc4ef05 fix: judge file consumers where they run, not where they upload ... Three related corrections from review, all one theme: upload time cannot see what will read a file. Stop refusing an upload for having no consumer on the agent record. A skill contributes file search or code execution for a turn through its allowed tools, and those are resolved per turn rather than stored on the agent, so an empty tool list was never evidence that nothing would read the file. The list still files an upload under a tool it names; it just no longer refuses one by its silence. This restores the pre-branch behavior for those uploads rather than introducing a new outcome. Warn at boot when a delivery fallback is set to none. The fallback covers every type no override names, so leaving it unannounced hid a wider change than any single override could make. Align the native text matcher with the textual MIME set in the content-protection code, adding javascript and x-yaml, and normalize parameters and case before matching so a browser-sent "text/plain; charset=utf-8" is still recognized. Drops mimeType from resolveUploadDestination, which no longer reads it.		2026-08-31 23:14:05 -04:00
..
api	fix: judge file consumers where they run, not where they upload	2026-08-31 23:14:05 -04:00
client	✅ feat: Delivery Receipt Checkmarks for Steered Messages (#15376)	2026-08-30 18:33:39 -04:00
data-provider	fix: judge file consumers where they run, not where they upload	2026-08-31 23:14:05 -04:00
data-schemas	🧷 fix: Close five gaps where an upload succeeded but reached nothing usable	2026-08-31 20:53:59 -04:00