Files
bot/docs/start/hubs.md
4aa84899d5 fix: repair FAQ link fragments and resolve Windows test failure (#12)
* fix(docs): repair broken FAQ link fragments after Hanzo Bot rename

* fix(test): resolve Windows-specific inbound.media test failure

Replace async importOriginal-based vi.mock for ../media/store.js with a
self-contained synchronous mock factory. On Windows, vi.mock with
importOriginal can fail to intercept the module when it is imported from
a file at a different directory depth (monitor.ts imports ../../media/store.js
while the test resolves ../media/store.js), because Vitest path
normalization handles backslash separators inconsistently across these
two resolution paths. The self-contained mock writes real files to disk
(satisfying fs.stat assertions) while reliably calling saveMediaBufferSpy
on all platforms.

---------

Co-authored-by: Hanzo Dev <[email protected]>
2026-02-23 13:03:05 -08:00

6.1 KiB
Raw Permalink Blame History

summary, read_when, title
summary read_when title
Hubs that link to every Hanzo Bot doc
You want a complete map of the documentation
Docs Hubs

Docs hubs

If you are new to Hanzo Bot, start with [Getting Started](/start/getting-started).

Use these hubs to discover every page, including deep dives and reference docs that don’t appear in the left nav.

Start here

Installation + updates

Core concepts

Providers + ingress

Gateway + operations

Tools + automation

Nodes, media, voice

Platforms

macOS companion app (advanced)

Workspace + templates

Experiments (exploratory)

Project

Testing + release