fdac8a1896
collect_acceptance's gh api subprocess inherited the calling process's environment, so on a multi-profile host the gate read the contract repo as the ambient (launch/default) gh login: a private repo in another org returned 404 and the broad except classified it infra with 'check gh authentication and retry', blocking green cards and holding them via the blocker_auth respawn guard (#122689). - Thread the assignee's profile home into every _api call and build the child env with served_profile_child_env(inherit_credentials=True): the profile's own GH_TOKEN/GH_CONFIG_DIR overlay, launch credential residue scrubbed (GH_CONFIG_DIR is a path, not a credential, so no scrub list saw it — drop it from the base for routed targets). - Classify a refused read (gh HTTP 401/403/404, or GraphQL resolving the repository to null) as 'auth' naming the repository, distinct from retryable infra; persist only the status code + endpoint, never stderr. - Unassigned/uninstalled cards and single-profile hosts keep the ambient env, unchanged. Fixes #122689
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.