{"agent":"claude","input":"Add giscus comments to this Starlight site. Read package.json, astro.config.mjs, src/content.config.ts, the three pages under src/content/docs and README.md first, and read Starlight's overriding-components guide and the Footer entry of its overrides reference. Add src/components/Footer.astro that renders the default Footer from @astrojs/starlight/components/Footer.astro followed by a new src/components/Comments.astro, and register it under components.Footer in astro.config.mjs. In Comments.astro render the giscus script tag with data-mapping pathname, crossorigin anonymous and async, reading data-repo, data-repo-id, data-category and data-category-id from PUBLIC_GISCUS_REPO, PUBLIC_GISCUS_REPO_ID, PUBLIC_GISCUS_CATEGORY and PUBLIC_GISCUS_CATEGORY_ID via import.meta.env, rendering nothing when any is missing, and add a .env.example naming them. Set the script's data-theme from the html element's data-theme attribute and add a client script with a MutationObserver on that attribute that posts { giscus: { setConfig: { theme } } } to iframe.giscus-frame with target origin https://giscus.app. Extend docsSchema with an optional boolean comments field, skip rendering when it is false or when the page template is splash, and document both in README.md along with the three GitHub prerequisites. Run npm install, npx astro check and npm run build with placeholder values, show that dist/guides/example/index.html contains the giscus script and dist/index.html does not, build again with the variables unset to show nothing renders, then open a pull request that pastes those checks.","resources":[{"url":"https://github.com/your-org/your-app"}]}