Add a documentation space with a page tree #269

Status (done 2026-09-17)

Decisions in #278. Commit hashes from before 2026-09-17 changed when docs/ was removed from git history.

Live: pages with revisions in the shared numbering; moderator edits, proposals for everyone else; page_store; item_get, item_search (memories, pages with excerpt, tasks; replaced memory_search), item_history, item_archive and item_delete for pages, including permanent deletion of a page or of single earlier versions with review; recall lists top-level pages. Docs tab with title filter, full-height tree with arrow-key navigation, breadcrumbs, row menu (new subpage, move up/down, move to, one delete dialog with a permanent option, Escape closes it), restoring deleted pages for moderators, editor with Write/Preview tabs, a separate versions view, copy link, Mermaid served locally, phone layout with a tree drawer. Addresses show the structure: /docs/{number}/{parent}/{page} plus /versions and /edit; older addresses redirect.

The development documentation itself lives in the project: Architecture (#279) with its subpages and Development (#281).

Outcome

Projects hold long-form development documentation (architecture, contracts, decisions, how to build and run) as a navigable page tree, similar to an Azure DevOps wiki. Agents fetch pages by number and are pointed to them from recall. Credentials, account names, internal security details and legal matters do not belong in project documentation.

Principles

• The tree is for people, references are for agents.
• No new knowledge silo. Pages take numbers from the shared project item sequence.
• Do not grow the tool surface.
• Reviewed like memories.
• Recall points, it does not inline.