Restore context7.json parsing config after claim

Ownership is verified and parsing is managed via context7.json, so restore the
config fields removed for the minimal claim: projectTitle, description, folders
(polished), excludeFiles, rules, and $schema. The url + public_key claim fields
stay in place, so ownership remains verified.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: franco-zalamena-iterable

context7.json

@@ -1,4 +1,19 @@
 {
+  "$schema": "https://context7.com/schema/context7.json",
+  "projectTitle": "Iterable Mobile SDKs",
+  "description": "Agent-facing reference for Iterable's mobile SDKs. Polished from Iterable's canonical docs with version-pinned snippets, decision tiers, and Kotlin-preferred Android examples. Covers push notifications, in-app messages, mobile inbox, embedded messaging, deep linking, JWT authentication, event tracking, user profiles, and unknown user activation.",
   "url": "https://context7.com/iterable/iterable-sdk-skill",
-  "public_key": "pk_JMMoVfKCtHoC5E3alGPcX"
+  "public_key": "pk_JMMoVfKCtHoC5E3alGPcX",
+  "folders": [
+    "polished"
+  ],
+  "excludeFiles": [
+    "*.layer-a.md"
+  ],
+  "rules": [
+    "Treat divergence from Iterable's published behavior as a critical issue — never invent SDK APIs, version numbers, or dashboard paths. If the user is on a different SDK version than the snippet's frontmatter `sdk_min_version`, surface the mismatch.",
+    "Several Iterable integrations fail silently with no error logs (JWT-required keys with no auth handler, `setEmail` inside the init callback, stale email captured in the auth handler lambda, runtime `POST_NOTIFICATIONS` permission missing on Android 13+, custom URL schemes without `setAllowedProtocols`, in-app handler import path drift). Always surface the relevant trap explicitly when the user touches these areas, even if they didn't ask.",
+    "For Android, prefer Kotlin snippets over Java. The polish layer drops Java duplicates when a Kotlin equivalent exists.",
+    "Frontmatter `sdk_min_version` pins the SDK release each snippet was validated against — surface it when the user asks about version compatibility, or when generating code that depends on an SDK feature introduced after a known older version."
+  ]
 }