needs input: The unchanged npm run build succeeds and writes a Next.js server build to .next/, not a static export. The site requires dynamic /api/* routes and /.well-known/farcaster.json, and emits root-relative /_next/ asset URLs. Static dist/IPFS hosting cannot host this site as it stands; changing source or configuration is forbidden. — Should this unchanged site use hosting with a Next.js server, or may its source and configuration be changed to support static dist/IPFS hosting?

needs input: Two things block hosting clrhc/quadConnect as it is. (1) License: the repository is under the Business Source License 1.1 with 'Additional Use Grant: None' (LICENSE, README 'License', and the latest commit a305e86): anyone may run it for non-production use, but nobody but the licensor (Celerity, github.com/clrhc) may deploy it or a derivative in production before 2030-10-30. Publishing it on IPFS under our name is a production deployment, and all 322 commits are by Celerity, not the requester. (2) Technical: unchanged, npm ci && npm run build (npm, package-lock.json) produces a Next.js 16 server build in .next/, not a static export. next.config.ts sets no output: 'export' and reads no environment variable for it, Next 16 has no CLI flag or next export for it, and the page loads all its data from the site's own /api/* routes (app/api/state and 20 others) and serves /.well-known/farcaster.json dynamically. A dist/ copied from it would be a shell with root-relative /_next/ URLs and