decf192176
tabro bundles a prebuilt Windows .exe (relay-native-host-0.4.2.exe) in its plugin tree. The install scanner cannot read machine code, and the SHA-256 the plugin checks it against is committed in the same commit, so it only proves the file was not changed after that commit, not where it came from. A reviewer cannot tell it matches the in-repo C++ source. That is a precedent worth closing before someone ships a binary that is not benign. - Delists tabro (deletes plugin-catalog/tabro.yaml). Existing installs keep working; not added to removed.yaml — there is no evidence of malice, only no way to verify the binary. An attested build (rule 17) is the way back. - Adds admission rule 17: no compiled binaries, committed Python bytecode, or archives hiding either, detected by file header not extension. A native component is allowed only with a GitHub build-provenance attestation tying it to the plugin repo's own workflow at the pinned commit; a setup-time download is allowed only from the tool's official source, pinned by checksum and disclosed. Mirrored into the docs submission guide (the mirror test enforces identical text). A full-content scan of all 543 pinned entries found tabro is the only one with a native executable. The enforcing gate ships in a follow-up PR.
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.