9e827685f2
Holographic now ships from itpartypattaya/hermes-plugin-holographic through the plugin catalog (plugin-catalog/holographic.yaml, v0.6.1 @ 46b6f908, a fork of Nous's archived handoff copy). It keeps the provider name, memory_store.db and plugins.hermes-memory-store, and memory_provider_migration already lists holographic in _LEFT_CORE. Deleting the in-tree copy and its tests lets `hermes update` and agent start install the catalog plugin for every home that has memory.provider: holographic. Host code that still releases memory-store handles on profile unserve/delete resolves the store through import_provider_module, the same way profiles.py already does, and no longer imports plugins.memory.holographic. Tests that used holographic as "a bundled provider" now use byterover. The journal-mode contract drops the holographic row because the plugin owns that store now. People who installed the archived Nous repo by URL have no catalog record, so `hermes plugins update` kept pulling the archive. read_catalog_sidecar now adopts an install from that repo as the holographic catalog entry, and update re-pins it to the maintained repo at the reviewed sha. That catalog re-pin also needed the reviewed-pin scan trust that catalog installs already get. Without it, update_plugin scanned the reviewed tree as an unreviewed community source and blocked on caution findings, and that blocked every catalog re-pin of holographic (the reviewed 46b6f908 tree has 14 caution findings).
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.