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

portal-portal/questions/received.yaml

@@ -0,0 +1,15 @@
+followup: true
+name: What happens with what you sent?
+description: >
+  Bendik reads every intake. Within two working days you get a link to
+  a working draft built from your answers.
+alternatives:
+  - name: You try the draft as each of your roles
+    description: >
+      Click through it as a customer, then as the colleague who handles
+      that customer. Tell us what reads wrong and the draft comes back
+      revised.
+  - name: Back to the start
+    description: ""
+    action: /
+    consequence: [Back]