Documentation that points where the documentation is

The working notes, the roadmap and the eight topic notes now live on the wiki,
so the twelve places in the source that said "see CLAUDE.md" were pointing at
a file this repository no longer has. They say "see the working notes" now,
and the README opens onto the wiki rather than onto two files beside it.

Four references are deliberately untouched -- prompts.py, settings_store.py,
admin/agents.html and the whole of agent/instructions.py. Those name AGENTS.md
and CLAUDE.md as the file an agent chat looks for in *somebody else's* project
directory. Rewriting them would have broken the feature while looking tidy.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/lembas/api/admin_images.py

@@ -3,7 +3,7 @@
 Two shapes on one nav entry, because they are two different kinds of thing. The
 connection, the checkpoints and the switches are instance settings and get a
 settings page. A workflow is an authored document with a name, a description and
-a body, so the workflows are list-plus-detail -- the shape `CLAUDE.md` requires
+a body, so the workflows are list-plus-detail -- the shape the working notes require
 of any admin list, and for the reason it gives: a page that renders a ten-line
 JSON textarea per row is unusable at three rows.
 

src/lembas/api/agents.py

@@ -238,7 +238,7 @@ async def browse_profile(
     it holds for the same reason -- somebody who owns the credential could list
     the directory with an ssh client -- but it does mean Manual mode's promise
     that everything is shown to you first now has a second exception. Both are
-    written down in CLAUDE.md.
+    written down in the working notes.
     """
     profile = _profile(db, user, profile_id)
     entries: list = []

src/lembas/api/chats.py

@@ -985,7 +985,7 @@ def _too_many_replies(db: DBSession, chat: Chat, user: User) -> str:
     """Why this account may not start another reply right now, or "".
 
     In-process, and that is exact rather than approximate only because this
-    application runs one worker -- see the first known limit in PLAN.md. With
+    application runs one worker -- see the first known limit in the roadmap. With
     several, this becomes a guess, and a quota that is a guess should be a
     number in the database instead. Stated here rather than discovered.
     """