docs(wiki): note retrospection learnings diffuse across the grid (agent namespace) Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(wiki): document retrospection (daily transcript replay → memory) Memory & Knowledge: a Retrospection bullet + the conflict-resolution update under "Learning from outcomes"; Configuration: memory.retrospect + retrospect_hours. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(wiki): document memory.resolve_conflicts (opt-in conflict resolver) Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(wiki): code graph is 5 languages + CLI graph subcommands + TUI/blugo/gateway surfaces Memory & Knowledge: languages now Rust/Python/Go/JS/TS (was "Currently Rust"), the new `blumi knowledge impact|callers|implementers` subcommands, and a note that the same queries are reachable from the TUI hot-spots, the gateway /api/knowledge/graph endpoint, and the blugo Code-tab Impact sheet. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(wiki): document the structural code graph, code_graph tool, RPL fan-in + rollover - Memory & Knowledge: a "Structural code graph (opt-in)" section (graph.mode + the code-graph feature + typed edges) and the code_graph agent tool (callers/callees/impact/implementers). - Configuration: knowledge.graph { mode, resolve_imports, max_edges_per_symbol, rpl_impact } and llm.wake_on_rollover. - RPL-Judgement: a note that file fan-in folds into the blast radius. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(wiki): GEO/AEO pass across all pages — answer-first intros, FAQs, question headings Optimize every wiki page for AI answer engines (GEO/AEO) and classic SEO, additively — all facts, commands, config keys, defaults, and links preserved: - Answer-first, self-contained intros so each page stands alone if an AI surfaces it with no other context (each restates what blumi is in one clause). - TL;DR / "Key facts" blocks of atomic, extractable facts near the top. - Question-style headings ("What is X?", "How do I Y?") matching natural queries. - A FAQ (Q&A) section on each substantive page — the most AI-citable format. - Consistent entity naming + acronyms expanded on first use (RAG, SEDM, RPL, BYOK, mDNS, FCM, STT/TTS, ...). - Fixed stale version (0.3.0 -> 0.5.0) on Home. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(wiki): dedicated RPL-Judgement deep-dive page (the science of the judgement) New SEO-friendly page documenting Raskolnikov's Psychological Loop in depth, grounded in the actual code: the blast-radius risk model (severity weights), the adversarial Porfiry LLM-as-a-judge + fail-open parsing, the five phases, the Error-Delta regret signal feeding memory fitness, the Dostoevsky mapping (inspired by Crime and Punishment), config reference, an FAQ, and an honest "implementation status & roadmap" (live MVP vs the reserved multi-branch ToT / worktree-sandbox knobs). Wired into the sidebar, Home nav, and cross-linked from Self-Management + Memory & Knowledge. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(wiki): v0.5.0 — memory learning-from-outcomes + RPL-Judgement Memory & Knowledge: new "Learning from outcomes" section (probationary failure→fix, value-based fitness + eviction, structure-aware/hub-suppressed recall, off-gateway curation, conflict + consensus-diffusion groundwork); heal.verify default flipped to true in the config example. Self-Management: new "RPL-Judgement" section (the five-phase Raskolnikov loop + config); updated self-healing to reflect probationary, verify-on-by-default learning. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs: add FAQ (decision-maker + developer lenses), grounded in the code A new FAQ page answering the questions that actually come up — "why blumi / what does it cost / where does our data go / vendor lock-in" for decision-makers, and "which providers, offline use, sandboxing, extensibility, the grid, memory, GPU, autonomy guardrails" for developers — plus the connectivity questions (the Tailscale/MagicDNS one, FCM-from-anywhere) and security/privacy. Every answer is grounded in shipped behavior (crates, config keys, executors, auth). Linked from the sidebar, Home guide table, and Home footer. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs: Dispatch + FCM push (Mobile-App + Configuration) - Mobile-App: "Dispatch" section — per-node isolated threads + Broadcast fan-out + fire-and-forget push, with inbox/thread/broadcast screenshots and the zero-config FCM service-account drop-in. - Configuration: "Push notifications (FCM)" section — enabled by file presence (~/.blumi/fcm-service-account.json, chmod 600), HTTP v1, token store + auto-prune, graceful no-op, never-commit secrets. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

Mobile-App: add the redesigned permission-card screenshot Show the inline approval card (Allow once / Allow session / Deny) under the gallery, with a note that safe commands auto-approve while writes and dangerous commands are gated. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

Mobile-App: blugo UI/UX redesign — welcome grid diagram + screenshots Refresh the screenshot table to the new design (welcome grid diagram, chat, control center, command palette), add a "Welcome screen — your grid at a glance" section describing the interactive node diagram (tap a saved node → Connect/Edit/Delete; tap a discovered dashed node → password-only sign-in; + to add by IP), note the shared design system, and add the grid welcome + `/` command palette to "What's inside". Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(home): polished landing page — logo banner, badges, nav cards Redesign the wiki Home as a proper front door: centered Blumi logo banner (assets/blumi-logo.svg, the Living-Rose gradient wordmark) + colorful shields.io badges (version/license/stack/platform), a 60-second quickstart, an emoji nav-card grid linking every page, a 'what blumi can do' highlights section, the three setups, and conventions. Logo vendored into the wiki repo so it renders reliably. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(config): comprehensive Configuration reference (every section) Rewrite Configuration.md into a complete, runnable reference so anyone can set up + tune blumi from one page: - Loading/layering (settings.json → project → env BLUMI_*), applying changes (reload vs restart). - Providers (preset table + kind/api_key_env/base_url) + full llm.* block. - Every section with real fields + DEFAULTS + copy-paste JSON, grouped: agent behavior (permissions, persona/personas, executor, brain, router, heal); memory & knowledge (embeddings, memory, knowledge, acceleration) incl. the enable + `blumi knowledge ingest` populate steps; surfaces (web, voice, gateway telegram/discord/slack/whatsapp, grid, remote, workspaces, git); autonomy (always_on, notify, hooks); tools (mcp_servers, lsp_servers). - A realistic "putting it together" settings.json + auto-continue + the MEMORY.md/USER.md files. Deep-dive cross-links throughout (all verified). All fields/defaults transcribed from blumi-config structs (accurate, not invented). Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(tui): /knowledge + /memories overlays (#184) CLI-Usage: add /memories (semantic memory browser) + /knowledge (code knowledge base) to the slash reference; clarify /memories vs the file-based /memory. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(gateway): 409 Conflict is now logged loudly Gateway: note the duplicate-bot guard — a 409 Conflict is logged to gateway.log (grep -i conflict) instead of silent double-replies. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(gateway): messaging-bot gateway as a service Gateway: new 'Messaging-bot gateway (blumi gateway)' section — run/install/ uninstall/start/stop/status, auto-start + crash/reboot restart, one-instance- per-token (409) caveat + upgrade-restart tip. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(gateway): gateway.telegram.voice (off by default) Configuration: document gateway.telegram {token, allowed_chats, voice}. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(notify): browser Web Push (VAPID) channel #209d — Self-Management Completion notifications: add Web Push as a server-side channel (Enable button, ~/.blumi/push.json, secure-context-only caveat). Configuration: notify bullet now lists web_push. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(notify): blugo phone completion notification #209c — Self-Management live-stream surfaces: add the blugo phone local notification (backgrounded; Android 13+ permission on first launch). Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(notify): browser in-tab completion alert #209b — Self-Management Completion notifications: add 'Live-stream surfaces' with the browser in-tab alert (title flash + favicon badge + ping + toast, backgrounded only) and the background-vs-interactive coverage note. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(notify): completion notifications (desktop + gateway bot) #209a — Self-Management: new Completion notifications section (server-side push: desktop + gateway bot, notify.* config, --notify one-off). Configuration: notify bullet. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

docs(hooks): pre_tool_use now wired (tool-blocking) #208 — Self-Management: split Lifecycle hooks into user_prompt_submit (inject context) + pre_tool_use (gate tool calls); document non-zero-exit blocks, matcher scoping, fail-open on infra errors, and reload-to-apply. Configuration: note pre_tool_use can block a tool call. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

Document lifecycle hooks (UserPromptSubmit) + config Co-Authored-By: Blumi <ankur.nairit@gmail.com>

CLI-Usage: /new-workspace + /clone-workspace commands Co-Authored-By: Blumi <ankur.nairit@gmail.com>

Document cost-aware routing, always-on discovery, white-box memory - Configuration: add `router` + `always_on` to the config reference (cross-refs). - CLI-Usage: new TUI commands /route + /discoveries. - Self-Management: full "Cost-aware routing" + "Always-on discovery" sections (config blocks, safety, how to drive them). - Memory-and-Knowledge: a "White-box memory (view/pin/edit/delete)" subsection + the /api/memory/* endpoints. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

Document GPU acceleration, self-healing & evolution, new TUI commands Refresh the help/wiki for the [Unreleased] features: - CLI-Usage: new slash commands /open-workspace, /heal, /accel (+ /grid and /autocontinue) and a `blumi accel` management row. - Memory-and-Knowledge: a GPU acceleration section (Apple CoreML default, CUDA opt-in, local-server/Ollama path, grid-embed offload) + acceleration/heal config; update embeddings.backend="grid" to the real strongest-peer transport. - Self-Management: a Self-healing & evolution section (reflex recovery, failure to fix learning, evolution autonomy, cross-step verify, /heal surfacing). - Grid: a GPU-aware embedding offload section (POST /api/grid/embed). - Installation: GPU/embeddings build options (BLUMI_CUDA, gpu-cuda, lean default). - Troubleshooting: GPU/accelerator + self-healing entries. - Configuration: acceleration/heal/embeddings/memory/knowledge cross-refs. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

Home: add a star-us call to action Co-Authored-By: Blumi <ankur.nairit@gmail.com>

Add Memory & Knowledge page (semantic memory, SEDM diffusion, code KB) Co-Authored-By: Blumi <ankur.nairit@gmail.com>

Grid: fix desk-photo alt text (MacBook Pro, not ultrawide) Co-Authored-By: Blumi <ankur.nairit@gmail.com>