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/aggregates.yaml

@@ -0,0 +1,17 @@
+# One onboarding per business. `open` is the intake as submitted; the
+# generator (portal-trainer generate) turns it into a draft content
+# repo; the business reviews the draft and either it goes live or it
+# comes back for another pass.
+aggregates:
+  - bucket: onboardings
+    initial: open
+    states:
+      open: { event: intake_received }
+      drafted: { event: draft_generated }
+      revising: { event: revision_requested }
+      live: { event: went_live }
+      declined: { event: declined }
+    transitions:
+      open: [drafted, declined]
+      drafted: [live, revising, declined]
+      revising: [drafted, declined]