LexLint: compliance lint for AI, scraping, and privacy law

Added value: +{
+  "description": "The match `why` was written from: the declared activities this instrument answers to, and the flags (engine axis) or behaviour categories (legacy axis) that matched. Present on every instrument finding.",
+  "properties": {
+    "activities": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "categories": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "flags": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "activities",
+    "flags",
+    "categories"
+  ],
+  "type": "object"
+}

Added value: +{
+  "description": "Why this instrument was pulled in, in basic language: which declared activity reached it and what the corpus tags it for. Show it ABOVE the finding's sentence wherever the finding appears, so the reader knows why before the law. Present on every instrument finding; absent on coverage and posture findings.",
+  "type": "string"
+}

Added value: +{
+  "description": "The full research summary the one sentence in `summary` was cut from. Present on instrument findings that have one; absent on coverage and posture findings.",
+  "type": "string"
+}

Added value: +{
+  "description": "How the jurisdiction reads to a person: \"Ireland\", \"European Union\", \"California (US)\". Show THIS in every table and sentence; the slug belongs in lexlint.yml. Absent when the corpus did not name the slug, in which case show the slug.",
+  "type": "string"
+}

Previous value: -"What the finding says, in one sentence."New value: +"What the finding says. On an instrument finding: the instrument's name, then one sentence, with the whole research summary in `detail`; read that before acting on a warn, and show it behind the sentence, never instead of it. A coverage or posture finding says what it must in the engine's own words."