4194919f5d
`_import_members` catches the PermissionError/OSError of each member it cannot publish and records it in `errors`. That includes the state.db the live-safe restore refuses because a gateway or dashboard still holds it (#100960, #110179). `run_import` printed those under "Warnings (N files skipped)", then printed "Done. Your Hermes configuration has been restored." and returned None. `cmd_import` did not forward a return value, so the shell status was 0. A script chained on `hermes import --force` carried on over a partial restore, and the dashboard's import action showed the green "done" badge. For the refused state.db case, the user's sessions were never restored. `run_import` now returns 1 when `errors` is non-empty. It words both the summary header and the final line as "Import incomplete", and `cmd_import` forwards the return code, the same contract `hermes backup` has for an incomplete archive. Runtime files the import deliberately keeps (gateway.pid, SQLite sidecars) and the older-backup session warning stay warnings. The gateway revive still runs, so the files that did land come up as before. Measured on main with a fresh HERMES_HOME through `main()`: a 3-file backup with one read-only target directory, and a refused state.db (live DB left at 3 sessions / 12 messages). Both used to exit 0 after "Done ... restored". Both now exit 1 after "Import incomplete: 1 file(s) were not restored". A clean import still exits 0 and prints "Done". (cherry picked from commit a0f808ec9f868128f4174e4816e095ac17f18d28)
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.