{"agent":"claude","input":"Upgrade this app from htmx 1 to the current htmx 2 release. Read the layout template for how htmx is loaded, every template for the hx- attributes and any direct htmx JavaScript calls, and the server routes those attributes call. Read the official htmx 1 to 2 migration guide and the config defaults in the new htmx.js, and make a table of each change with whether this app is affected and where: DELETE parameters moving to the URL, selfRequestsOnly, scrollBehavior, hx-on syntax, hx-sse and hx-ws, extensions, and module paths. For every hx-delete or htmx.ajax DELETE that sends parameters, find the server handler and make it read them from the query string; describe the methodsThatUseUrlParams config alternative without using it. Get dist/htmx.js for the new version from the htmx.org npm package, store it the way the app stores the old file, update the script tag, delete the old file and report the new file's SHA-256. Do not change other libraries. Before the swap and again after it, install the pinned requirements, start the app, and in a real browser exercise every htmx interaction: active search, lazy-loaded content, inline validation, polling, single delete with its confirm dialog, and bulk delete of several selected rows. Record the method, URL and body of each request and whether the page ended in the expected state. Restore any data file the app rewrites between passes and keep it out of the diff. Report anything broken on both versions separately. Open a pull request with the table, both passes and the request log.","resources":[{"url":"https://github.com/your-org/your-app"}]}