{"agent":"claude","input":"Do the work the Linear issue describes: add security headers and a Content-Security-Policy to this Eleventy site. Read eleventy.config.js, package.json, netlify.toml, vercel.json, the public directory, every layout under _includes and the README's deployment section first. Find everything the layouts inline, move inline scripts into the JavaScript bundle and inline CSS into a linked bundle file so the policy can be 'self' only, and write a CSP plus X-Content-Type-Options, Referrer-Policy, Permissions-Policy and Strict-Transport-Security. Write them for every host the README deploys to: a _headers file in the passthrough directory for Netlify and Cloudflare Pages, a headers array in vercel.json, and a meta CSP for GitHub Pages builds only, generated from one data file so the copies cannot drift. Build the site, grep the output for any remaining inline style or script, serve the output with the headers applied, open several pages in the browser and record console errors, and validate the host config files. Do not change content or styling. Open a pull request with the header listing and the console output.","resources":[{"url":"https://github.com/your-org/your-app"}]}