build: stages in the plan's own words

`stages_text` on a need gives each stage plain words in the plan's
language. The fallback mails, the road line and the desk buttons use
them, and needs.yaml carries them as `stage_words` so the desk score
describes an outcome the way the site would. The vel's plan has them;
its desks score 26 of 26 where the id-based outcome scored 24.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

README.md

@@ -167,6 +167,12 @@ the business's own words and held-out personas.
   body (`aggregates.yaml` in the words map); the fallback says what
   happened and, where the submitter has a move from that stage, the
   link to make it.
+- `stages_text: { <stage>: <words> }` on a need: each stage in the
+  plan's language, where the ASCII id will not do (`ikke_lost` reads
+  as English). Used by the fallback mails, the "what happens next"
+  line, the desk buttons' fallback labels, and written into needs.yaml
+  as `stage_words` so the desk score describes an outcome in the
+  site's own words. With them, the vel's desks score 26 of 26.
 - `attended_by:` on a need: who moves cases that no desk button moves,
   an automation listening on the bucket's events, written into
   aggregates.yaml as portal's own annotation for the reader.