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>
This commit is contained in:
@@ -7,7 +7,7 @@ are separate because they fail differently:
|
||||
shows;
|
||||
- **flavour text** — the Middle-earth lines, which live in the artwork, the
|
||||
empty states, the loading lines and the error pages and nowhere else (see the
|
||||
flavour rule in CLAUDE.md), and which somebody rebranding needs to be able to
|
||||
flavour rule in the working notes), and which somebody rebranding needs to be able to
|
||||
replace without editing templates;
|
||||
- **themes**, which are token sets rather than stylesheets, because the
|
||||
invariant that no component hard-codes a colour is what makes a third one
|
||||
@@ -36,7 +36,7 @@ page and by nothing else.
|
||||
The cost of being a cache is stated rather than discovered: with several
|
||||
workers, a save in one is not seen by the others until each next reads. That is
|
||||
already true of this application for other reasons -- see the "one worker" note
|
||||
in PLAN.md -- and this does not make it worse.
|
||||
in the roadmap -- and this does not make it worse.
|
||||
"""
|
||||
|
||||
from __future__ import annotations
|
||||
|
||||
Reference in New Issue
Block a user