One binary: the lint and the trainer are commands of portal

portal serve runs a site; portal lint is what iris was; portal plan,
build, report and the rest are what portal-trainer was. One source at
one version, so the three never disagree about what content means.
Both histories are merged in (subtree). The release attaches the bare
binary for a content repo's CI. The trainer's plans, intakes, engines
and reference prompt come along; its runs stay in the old repo.

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

docs/README.md

@@ -14,12 +14,15 @@ engine does with it.
 | [Storylines](storylines.md) | The same site told several ways: lists of texts, one storyline per visitor, counted per storyline. |
 | [Memberships](memberships.md) | Groups kept by portal itself: a membership as a case, a person as a phone number first, and the provider only saying who. |
 | [Operations](operations.md) | Releasing, deploying, adding a site, environment variables. |
+| [Training a site](training.md) | `portal plan` and `portal build`: a business in plain words becomes a content repo, held to the lint. |
+| [The lint](lint.md) | `portal lint`: what a content repo's CI runs before anything reaches a site. |
 | [Filesystem routes](design/filesystem-routes.md) | Why the `questions/` tree is the router. |
 
-Two repos in the same family carry their own docs:
+One repo in the same family carries its own docs:
 
-- [uhhm/iris](https://project.uhhm.no/uhhm/iris) — the lint. Versioned
-  as portal and released by portal's publish job; it is the thing a
-  content repo's CI runs before anything reaches a site.
 - [uhhm/gdo](https://project.uhhm.no/uhhm/gdo) — the mailer. Delivers
   what content asked to be sent, and carries replies back.
+
+The lint (once uhhm/iris) and the trainer (once uhhm/portal-trainer)
+are commands of the `portal` binary since 0.6; their chapters are
+above, and the trainer's runs stay in the old repo.