Version 0.75.0

Each build now says which storage network it was made for, and the deploy checks that answer against what it was told before letting the build go out.

NMTS can be built for either of two networks: the live one, where storage is real and paid for, or the test one, where it is neither — and the choice is frozen into the build, so a wrong one would mean your browser talking to the wrong storage network entirely. Until today nothing checked it, and worse, the code was written to refuse a build that chose nothing while the deploy configuration quietly answered on its behalf with the test network, so the refusal could never happen. Nothing was ever served from the wrong network: the deploy has named the live one all along, and we checked. The deploy now reads the choice before building and stops if there is not one, every page carries a line naming the network it was built for, and after the deploy finishes it asks the running site to read that line back — if the two disagree, the deploy fails.