Using the macOS release binary from a TypeWhisper plugin

[scriptease]

Hi! I'm building a TypeWhisper plugin for live dictation with Confucius4-R2T2, using audiocpp_server and its live transcription route. TypeWhisper's maintainer has approved a version where the plugin manages the server itself, following the same pattern as their Cohere plugin with CrispASR (discussion):

• the plugin downloads a pinned audio.cpp release asset (audio-<tag>-bin-macos-arm64-metal.tar.gz), with the exact version, size and SHA-256 fixed in source and no "latest" lookup
• it runs audiocpp_server --config as a supervised child process on 127.0.0.1 and a random port, and stops it when TypeWhisper quits
• the Apache-2.0 license and credit are shown in the plugin settings
• a user-run server stays as an option

Before I build it, a few questions:

1. Is it OK for a plugin to download your release assets like this? Once a release is published, do its assets stay unchanged, or can they be replaced, as with the hotfix tags?
2. Are the audiocpp_server command-line options and the server.json format stable enough to depend on across releases?
3. Is a release planned that includes the R2T2 K-quant change (955c872)? That's the version I'd pin first, since it lets users pick the 1.2 GB Q4_K_M quant.

Thanks for audio.cpp and for the quick responses on #618 and #678!

[0xShug0]

@scriptease Thank you for integrating audio.cpp into other projects!

1. It should be fine. A release will not be changed once published.
2. Yes. The schema may be extended, but backward compatibility will be maintained.
3. The next release is planned for next week, unless there are other significant regression bugs like the Audio8-TTS one.

Also if you like you can host the K-quant packages yourself and open a PR to add the links to the spec. If @davidxifeng prefers to host them later, we’ll just need to update the spec.