From 5b518d1181f54e615521576151eaf4687af70e94 Mon Sep 17 00:00:00 2001 From: YokiiroBW Date: Mon, 27 Jul 2026 06:16:55 +0800 Subject: [PATCH] feat(chat): carry voice and other non-image attachments end to end MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit F-33. A voice reply produced nothing at all: no marker, no event, no error. Four independent gates each dropped it, and fixing any one alone would have changed nothing observable. The mapper reached `map_media` for image, record, file and video alike, but its only emitting branch was gated on the frame being an image, and the `attachment_saved` fallback rejected every other type outright. Both now carry whatever type arrived, with the frame type as the marker's alt text so the renderer knows what to expect before any bytes exist. `pending_media` was also a single slot, so a second attachment in one reply overwrote the first before it was paired; it is a bounded queue now, and an `attachment_saved` with no id no longer consumes the media frame still waiting for one. The download judged a candidate path successful only if the bytes sniffed as an image — this server answers unknown paths with its own text under HTTP 200, so sniffing is load-bearing and cannot simply be dropped. Audio and video signatures are recognised now, and a declared Content-Type is trusted when it names media rather than only images. SILK is included deliberately: it is what AstrBot relays for QQ and WeChat voice, no browser decodes it, and recognising it is what lets the UI say so instead of rendering a player whose play button does nothing. The CSP had no `media-src`, so it fell back to `default-src 'self'` and an `