d94769da64
* refactor(update): one predicate for serve rows outside the gateway matrix The inventory branch of `_marker_only_restart_obsolete` inlined the rule for which serve/dashboard rows the gateway matrix neither covers nor needs to (supervisor-owned, or a manual serve handed to its own reminder). The inventory-less branch needs the same rule for #118742, so it moves to `update_cmd_fleet_gatewayless.runtime_outside_gateway_evidence` and both branches will read one definition. No behaviour change. * fix(update): a Desktop-only host settles an inventory-less restart obligation A host that runs no gateway (the Desktop app alone) can be left with an inventory-less fleet-restart obligation: an updater that died before recording its inventory, or the pre-inventory writer. With no owed set, the live gateway matrix is its only evidence, and on that host the matrix is empty forever, so `_marker_only_restart_obsolete` never settled and every later `hermes update` exited 1 with "gateways are still off the checkout code" (#118742). An empty fleet alone cannot tell that host from one whose gateway the dying update stopped, so the inventory-less branch now asks the live host, never a historical receipt: `host_owes_no_gateway_restart` settles only when no profile's `gateway_state.json` claims a state other than stopped/startup_failed (a gateway that went away without a clean stop keeps the obligation) and every live runtime sits outside the gateway matrix (`runtime_outside_gateway_evidence`, shared with the inventory branch). HEAD must still contain the pulled SHA (`checkout_contains`, same rule as #119367). Probe failures keep it. Tests: the scoped-reconciliation matrix now holds its host at "the update stopped a gateway" so it keeps pinning receipt independence; a new host-evidence matrix covers Desktop-only, clean stop, carried commit, stopped gateway in a named profile, unclassified and unidentified serves, a gateway row without fleet identity, and a diverged checkout. Two manual-serve tests that assumed an empty fleet always stays pending now stub the live host and assert the manual reminder survives the gateway obligation settling. Co-authored-by: KoNit-K <124019182+KoNit-K@users.noreply.github.com> --------- Co-authored-by: KoNit-K <124019182+KoNit-K@users.noreply.github.com>
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.