seo: serve context7.json so the llms.txt corpus can be claimed

Context7 already indexes imqueue.org's llms.txt as a corpus. Claiming it —
which is what puts the site's own name on the listing instead of leaving it
an anonymous mirror — requires serving the ownership proof verbatim from the
domain root, so this is a passthrough copy rather than a template.

org only: the claim is over imqueue.org's corpus, and imqueue.com has no
llms.txt listing there to claim.

Author: Mikhus

eleventy.config.js

@@ -789,6 +789,13 @@ module.exports = function (eleventyConfig) {
   // paths to imqueue.org; imqueue.org 301s retired versioned API URLs to /latest/.
   eleventyConfig.addPassthroughCopy({ [`src/${EDITION}/_redirects`]: "_redirects" });
 
+  // Context7 ownership proof. Context7 already indexes imqueue.org's llms.txt as a
+  // corpus; claiming it means serving this file verbatim from the domain root so the
+  // public key can be matched. org only — the claim is over imqueue.org's corpus.
+  if (!isCom) {
+    eleventyConfig.addPassthroughCopy({ "src/org/context7.json": "context7.json" });
+  }
+
   // API reference (current + kept archives) is now generated as native Eleventy
   // pages under src/org/api/**; the old standalone TypeDoc HTML passthrough is
   // gone. Regenerate with `npm run build-docs` (latest) / `gen-api-archive` (old).

src/org/context7.json

@@ -0,0 +1,4 @@
+{
+  "url": "https://context7.com/llmstxt/imqueue_llms_txt",
+  "public_key": "pk_fjNtG1ue4XLAYwKYgyOMq"
+}