Documentation pages - let's get some sort of wiki-style (doesn't actua

v1 DONE (branch flower/docs-pages off master) — full suite green (481 passed, 1 pre-existing skip, 3450 assertions), pint clean, `npm run build` compiles, and I visually verified /docs + a doc page in a browser (bloom-native prose, working NOTE callout, ASCII pipeline diagram, accent wiki-links, active-page sidebar highlight). NOT merged — handing back for review/merge. Fully additive: 20 files, 1331 insertions, 0 deletions. ## Three per-unit commits (each `Brief: #37`) 1. ead8e7a — DocsService + DocsMarkdownExtension: file-based markdown under resources/docs → HTML via league/commonmark (already in composer, no new dep). Front-matter (title/section/order/slug/summary, with filename + first-heading fallbacks), grouped nav tree, `[[slug]]`/`[[slug|Label]]`/`[[slug#frag]]` wiki-links → /docs/{slug}, relative *.md links rewritten, GitHub-style `> [!NOTE]` callouts, heading anchor ids. Content-independent unit test. 2. a324e2f — six real, cross-linked starter docs across 3 sections: Getting started (What is flower?, Core concepts/primitives), Guides (Briefs & dispatch lifecycle, Daemons & roster + heartbeat model, The ingest pipeline), Reference (Using the flower MCP, adapted from docs/USING-FLOWER-MCP.md). ASCII flow diagrams, callouts, tables — drawn from the codebase so it's accurate. 3. 9ffc977 — /docs + /docs/{slug} routes; Livewire Docs\Index (section/page landing) + Docs\Show (404s unknown slugs); grouped docs sidebar w/ active highlight; scoped .docs-prose + .docs-callout bloom CSS; a "Docs" top-nav entry (new book icon). HTTP render tests (index lists sections; a page resolves wiki/.md links + renders callouts; unknown slug 404s). ## Scope I trimmed for a clean v1 (flag for your call) - **Codex-generated images / visuals** — the brief mentions "use codex for generated images where appropriate." I did NOT generate any (can't run codex from here, and binary image assets add review weight). Diagrams are done as styled ASCII/box art in code blocks instead — crisp, themeable, zero-dependency, and edit-in-a-PR friendly. If you want real generated diagrams, that's a good follow-up brief once the content settles. - **Mermaid / interactive flowcharts** — skipped to avoid adding a JS lib + build step to a low-risk additive change. The ASCII diagrams cover the "map out flow" intent for v1; mermaid can be layered on later. - **Search across docs, prev/next pager, on-this-page TOC, doc rendering cache** — all deferred; the corpus is small so no cache in v1. Docs are NOT yet indexed into recall (they're a separate reader surface); wiring resources/docs into the ingest/chunk pipeline so `recall_search` finds them is a natural next step but was out of the additive/low-risk scope. - **Auth/visibility** — /docs is open like the rest of the local UI. Before you share externally you'll want access control; flagging since you mentioned sharing with 1-2 people. Everything else from the dispatch is in: markdown rendering, /docs index + /docs/{slug} with left-nav sidebar + rich internal linking + code/callout styling, real seed docs, top-nav entry, render tests, green suite, pint.

Documentation pages - let's get some sort of wiki-style (doesn't actually have to be wiki just documentation with good navigation and rich linking between pages) documentation - complete with visuals (use codex for generated images where appropriate) to describe how this whole thing works, define the primitives (Briefs, Projects, Sessions, Segments, etc) and map out/show flow charts for things where it makes sense/helps explain things. I'm likely going to start sharing this with 1-2 people at some point here (not yet, needs more polish) and I figure it can't hurt to get started on the docs/getting-started type content.