/** * hanzo.sh answers one URL with two different things, and always has: the * landing page to a browser, the installer to `curl -fsSL hanzo.sh | sh` — the * command the page prints, llms.txt publishes, and every /cli /mcp /dev shim * re-executes. * * It used to do that by shipping a single file that was both at once: the built * HTML wrapped in a shell heredoc, `#!/bin/sh` on line 1. A browser cannot be * handed that honestly. Anything before that is not whitespace * or a comment puts the document in quirks mode, and a shebang is neither — so * compatMode was BackCompat, all fifteen elements (title, icons, * viewport, every og: and twitter: tag) were parsed into where they do * nothing, and `#!/bin/sh <<\EOF` was the first text node on the page. No * arrangement of those bytes avoids it: the shell reads `<` as a redirect * operator, so a POSIX script cannot begin with `