10f5530967
Follow-up to the salvaged plugin-streaming commit. The adapter read voice/model from the plugin's own tts.<name> section, so a streamed reply spoke the plugin default while synthesize() got tts.voice: the voice changed with the surface. It also skipped the sync dispatcher's routing: a same-named `type: command` provider (which wins for synthesize) lost to the plugin on the streaming path, and an is_available() == False plugin was streamed anyway. - tools/tts_tool_plugins: one routing guard (_plugin_route_key) and one voice/model/speed builder (_plugin_voice_kwargs), shared by synthesize() dispatch and the new _plugin_pcm_streaming_provider (streams_pcm + positive stream_sample_rate + is_available(), read at resolve time) - tools/tts_streaming: _PluginPCMStreamer stays a thin adapter; stream_channels/stream_sample_width dropped (the contract is int16 mono, which every sink assumes) - agent/tts_provider: streams_pcm / stream_sample_rate declared on the ABC with the contract - tests: two invariant tests next to the plugin dispatch tests (the streaming test module skips without numpy); docs for plugin authors
Website
This website is built using Docusaurus, a modern static website generator.
Reading the docs on GitHub? The Markdown under
docs/is authored for the rendered site at https://hermes-agent.nousresearch.com/docs/. Cross-page links are relative Markdown paths, so they follow through on GitHub's file viewer too. Every page on the site has an Edit this page link that opens the source file here.
Authoring links in docs/
- Link to another page with a relative Markdown path, anchors included:
[Profiles](../user-guide/profiles.md),[Bundles](../user-guide/features/skills.md#skill-bundles). Docusaurus turns the file path into the page route; GitHub follows the same path. Site routes (/user-guide/profiles,/docs/user-guide/profiles) only work on the rendered site — GitHub resolves them as repository paths and 404s, and the/docs/form also emits/docs/zh-Hans/docs/...404s in the zh-Hans build becausebaseUrlis already/docs/. python3 website/scripts/check_doc_links.pyfails on any route-style link in hand-authored pages (EN and the zh-Hans mirror);--fixrewrites them. It runs in theDocs Site Checksworkflow. Generated pages (user-guide/skills/{bundled,optional},reference/*skills-catalog.md) are produced byscripts/generate-skill-docs.py, which emits the same relative form.- Pin
{#anchor}on cross-linked headings so the zh-Hans mirror keeps the same id.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.