7a40c28750
CI run 36189416163 failed after "git: unpacking": executing the cached fetch-<sha> PortableGit PE in place left it handle-held (Defender on-execute scan / the stub's RunProgram child chain) past pm's ~2 s _remove_entry retry, so download cleanup raised WinError 32. Review (teknium1, 5 threads) adds the rest: - Git.unpack now copies the artifact into a .sfx-* dir beside the staging tree and executes the copy; pm's .staging-* teardown (ignore_errors) owns that path, so any hold lands on a disposable path and the cache dir only ever holds read handles - refuse off-Windows with the cross-host trade-off stated instead of a raw PermissionError; documented in package-management.md and the PR - the extractor is a GUI-subsystem stub that is silent under -y: error messages now carry the exit code and the usual causes (disk full, path length, antivirus) instead of promising captured output; the docstring no longer claims "no GUI" and records that the stub shows an Extracting window and runs the vendor post-install - install.ps1: WaitForExit(600000) + Kill() mirrors pm's timeout=600, Fail reports the exit code and the silence - tests: the OS-refused-exec assertion and the not-in-text change detectors are replaced by subprocess-argv invariants (scratch copy location, exit-code message, off-Windows guard before any execution) Related to #122512 (cherry picked from commit adaf76a286bebe30c89aee4174df27f1945b60c9)
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.