v1.3.0 — KEYWORD Convention + Verification Refresh

🔑 v1.3.0 — KEYWORD Convention + Verification Refresh

This release makes AI OSINT safer to publish and easier to use responsibly, and refreshes verification status as of June 2026.

The KEYWORD Convention

All ~400 dorks and queries now use a KEYWORD placeholder instead of hard-coded secret-seeking strings. Replace KEYWORD with a term you're authorized to search for — your brand, an owned domain, an internal project, or an engagement scope. Service fingerprints (titles, paths, ports, env-var names, key prefixes) are kept, because they identify the service, not a victim's secret.

Why: documenting common AI misconfigurations and how to audit your own exposure is legitimate. Shipping turnkey strings that maximize the yield of other people's live secrets is not. This convention keeps every technique useful for authorized testing without being a harvesting kit.

Verification Refresh (June 2026)

• 🟢 Grok shared conversations — still broadly indexed
• 🟡 ChatGPT shares — degraded (de-indexing ongoing since Aug 2025) but cached/archived remnants persist
• 🟢 HuggingFace Spaces — active
• ✅ GitHub web search confirmed on path: syntax
• ✅ ChromaDB confirmed /api/v2, port 8000, no auth by default
• ✅ Default ports & provider key prefixes re-verified

Unchanged

Threat intelligence, tools, Sigma rules and CVE coverage carry forward from v1.2.0. This is a parameterization + verification release, not a content expansion.

Full changelog: CHANGELOG.md

---