Bug Description\n\nSite: Jigidi (jigidi.com)\nCheck type: status_code — expects 2XX = claimed\nProblem: The site is behind Cloudflare protection that returns HTTP 200 for ALL requests, including non-existent users. Both adam (claimed test username) and noonewouldeverusethis7 (unclaimed test username) return HTTP 200 with identical Cloudflare challenge page content.\n\n## Investigation\n\nTested both URLs:\n- https://www.jigidi.com/user/adam → HTTP 200 (supposedly "claimed")\n- https://www.jigidi.com/user/noonewouldeverusethis7 → HTTP 200 (should be "unclaimed")\n\nBoth return the same Cloudflare JavaScript challenge page:\n\n\n\nThis is a Cloudflare "I'm under attack" mode page that blocks all automated access. Since checkType: "status_code" only checks the HTTP status (not content), any username gets a false "Claimed" result.\n\n## Proposed Fix\n\nDisable the Jigidi site entry in data.json since it cannot be reliably checked without solving Cloudflare challenges.\n\n\n\n## Context\n\nThis matches the pattern used for other Cloudflare-protected sites in the database (e.g., MicrosoftTechNet, AppleDiscussions are disabled). See development.rst "How to fix false-positives" section for the standard process.