iris: the lint over a portal site, as its own repo

question_lint becomes `iris check`, needs_replay becomes `iris
replay`, and the needs module and local-checkout loaders come with
them. Portal is a library dependency pinned to the release iris
matches (v0.3.36), so every type iris reads is the site's own and the
two never disagree about what a page is. `iris --path questions`
still works, so a content repo's one-line CI needs only a new path.

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

CHANGELOG.md

@@ -0,0 +1,12 @@
+# Changelog
+
+One line per change, grouped by the release that shipped it. Newest
+first. Each release names the portal tag it is built against.
+
+## 0.1.0 (2026-09-22) - portal v0.3.36
+
+- First release: the lint moved out of portal (`question_lint` becomes
+  `iris check`, `needs_replay` becomes `iris replay`), with the
+  business-needs pass, the wording task export and scoring, and the
+  simulation model export. Portal is a library dependency pinned to
+  the release iris matches.