Tones and storylines: every word once per tone, kept through a lift, and a report of what each brought in

tones in the plan lists tones of voice, one storyline each. The words
pass writes each page once per tone and folds the tones into lists
where they differ; the render emits the lists portal reads as
storylines; the lift carries them back. needs.yaml names the tones.
portal-trainer report --site reads the site's counts per storyline
and scores each on what arrived and what ended well.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt

src/plan.rs

@@ -169,6 +169,12 @@ rest. Each is one line in the plan, and the builder does the wiring:
   behind sign-in, with name and address filled from the account: a
   seat on a committee for members, a discount for customers. The
   group is one a decision `grants`, so nobody has to be waved in.
+- **Tell it two ways and find out.** `tones` lists tones of voice, one
+  storyline each: every word on the site is written once per tone, a
+  visitor reads one storyline throughout, and the site counts what
+  each brought in. Two is plenty; name them as a person would ("plain,
+  like a good notice on the door"; "warm, as a neighbour would put
+  it"). Leave it out to tell one story.
 - **Keep the people in portal.** `people: memberships` keeps every
   group in portal itself: a desk invite is a place held until the
   person signs in, a person is their phone number first, and any