304cf75bbd
The PR filtered a foreign tenant root only in hermes_cli.gateway.host_multiplexer_serving; the seam `gateway run` actually goes through had no cross-tenant path, so tenant B's gateway still never started: host_attach.decide() answered ATTACH (exit 0, nothing running) on tenant A's record "serving default", and run._claim_host_gateway_role lost the per-OS-user host lock to A and refused 75 forever (a race B can never win). * gateway/host_attach.py: one predicate, launched_by_other_tenant(owner_home, our_home), used by decide() (foreign owner -> START), by the lock-loss branch of _claim_host_gateway_role (start beside it, WARNING), by host_multiplexer_serving (replaces its inline copy) and by host_topology._from_host_record (doctor / cron status / dashboard ladder no longer report a foreign tenant's process as this tenant's host gateway). * gateway/host_topology.py + gateway/status.py: HostGatewayTopology carries the launch home, and multiplexer_liveness_for_profile reads the multiplexer's gateway_state.json from THAT home, so a named-hosted multiplexer no longer projects a stale standalone record from the default root. * hermes_cli/gateway_multiplex_mode.py: recorded_standalone_warning_lines gates on gateway_state + live PID only; a paused/wedged-heartbeat live gateway still warns. * docs: `hermes -p X gateway restart` on a parked profile with no live gateway behaves as start. Tests: one regression per finding (decide()+lock loss; topology home+tenant filter), both red on the PR head. tests/gateway/test_host_gateway_lock_refusal.py publishes its record from the process home instead of an arbitrary tmp dir (the home was never consulted before; assertions unchanged). test_gateway_multiplex_mode case 3 flips to "stale heartbeat + live PID still warns".
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.