0e430b2d82
A published recovery closure was trusted on presence alone: a power loss after the rename could leave a torn _early_recovery.py that failed every launch forever, and foreign bytes ran in place of pre's code. - publish_recovery_closure writes a MANIFEST of blob ids (ls-tree at pre, each cat-file output re-hashed against its id), fsyncs files and directories before the rename, re-verifies an existing closure instead of trusting it, and refuses a pre that is not a full commit id (no HEAD, no path under the git dir). - The minted launcher hashes every file against the manifest before importing; a missing, torn or foreign closure is discarded and rebuilt from git's objects (--no-replace-objects) and verified again. - Its git is the recorded absolute one or an absolute PATH entry, never a bare 'git' that CreateProcess (or an empty POSIX PATH entry) resolves from the current directory (m4). - A repair refused by a live writer exits 1 with the repair's own reason: no "repairing it" banner, no import traceback (m3). (cherry picked from commit 94e436325b40b5b99962c3c646d3760ecad9dc4f)
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.