Enable Discussions with a Compliance & classification category

[eaitbrahim]

Discussions is currently disabled. Questions will otherwise arrive as issues, where they are noise, or nowhere, which is worse — a question nobody could ask is a contributor lost silently.

For this project the highest-value category is not technical: it is a place to discuss classification and rulings without it becoming a pull request against a default.

Acceptance

• Enable Discussions
• Categories: Q&A, Ideas, Show and tell, and Compliance & classification — the last one explicitly for "should X be treated this way", kept separate from bug triage
• Seed with 3–4 real posts so it is not an empty room: the honest measured result and what it means, the "not a fatwa engine" boundary, and an open call for the scholarly review path
• Link it from README and issue templates

[eaitbrahim]

Status — everything done except one UI-only step:

• Discussions enabled (has_discussions: true, verified via API)
• Q&A, Ideas, Show and tell categories present (verified via GraphQL — they are Discussions' defaults)
• Compliance & classification — blocked: GitHub exposes no API for creating a category (no GraphQL mutation — introspection shows none — and no REST endpoint; tried both). It needs one authenticated click in the web UI from a repo admin. Exact step below.
• Seeded with 4 real posts:
  • #304 The honest measured result (Announcements) — links the experiment record, states the posture
  • #305 keel is not a fatwa engine — the governance boundary (Announcements)
  • #306 Open call: a scholarly review path (General — move to the new category when it exists)
  • #307 Start here: what goes where (General)
• Linked from the README (merged in docs(readme): rewrite for the newcomer, led by the compliance engine #300's "Asking questions, and contributing") and from the issue templates (merged in docs(templates): issue forms with a distinct compliance-question route, and a PR template that asks the right questions #303's config.yml contact links)

The remaining click (any repo admin, ~30 seconds): repo → Discussions → in the Categories sidebar, click the pencil ("edit categories") → New category, with:

• Name: Compliance & classification
• Description: Should X be treated this way? Rulings, attestations, and how different operators classify assets and mechanisms — a question, not a bug, and not a pull request against a default.
• Format: Discussion (not Q&A/announcement)

Then move #306 into it. This issue stays open until the category exists.

[eaitbrahim]

Category created and verified — Compliance & classification now shows in the category list (GraphQL), and discussion #306 (the scholarly-review open call) has been moved into it.

All acceptance now met: Discussions enabled; Q&A, Ideas, Show and tell, and Compliance & classification present; four seed posts (#304–#307); linked from the README and the issue templates' config.yml. Closing.