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

intakes/contractor.yaml

@@ -0,0 +1,44 @@
+# An intake as the owner of a small building contractor would fill it
+# in: plain words, no portal vocabulary. These are the fields the
+# onboarding site asks for.
+business: Nordvik Bygg
+contact: { name: Ingrid Nordvik, email: ingrid@nordvikbygg.example }
+language: en
+
+what_we_do: >
+  We are twelve people. We survey old buildings, draw up rehabilitation
+  plans, handle the permit application, and do the building work with
+  our own carpenters plus subcontractors for electrical, plumbing and
+  scaffolding.
+
+who_comes_to_us: >
+  Housing boards and private owners who have a problem with a building
+  and want someone to look at it. Owners who already know what they
+  want built and need drawings, a permit and a price. Trade firms who
+  want to be on our list of subcontractors. Carpenters and apprentices
+  asking if we are hiring.
+
+what_we_keep_track_of: >
+  Enquiries: they come in, we go and look at the building, we send a
+  quote, and then we either win it or lose it. Sometimes it is simply
+  not for us and we say so straight away.
+  Subcontractors: they apply, we check their company registration,
+  trade approval and insurance. Often papers are missing and we have to
+  ask again. Then they are approved or turned down.
+  Job applications: we read them, invite some to an interview, and hire
+  or decline.
+  Things that go wrong on site: a hazard, a near miss, wrong materials
+  delivered. Someone reports it, the safety officer decides what is
+  done about it, and closes it when it is fixed.
+
+who_is_involved: >
+  Two project managers handle enquiries, subcontractors and hiring.
+  One safety officer handles everything reported from site.
+  The crew, ours and the subcontractors' people, are the ones on site
+  who report things. They are on their phones, with gloves on, and
+  will not fill in a long form.
+
+what_slows_us_down: >
+  Enquiries arrive by phone, email and text and get lost. We never know
+  which subcontractors have valid papers. Site problems get mentioned
+  at lunch and forgotten.