deploy: node 1.0.1

Upstream released v1.0.0-gm and v1.0.1 on mainnet day; the fleet has run
0.11.1 from the published mainnet.json since the hand cutover. The node-side
delta from 0.11.1 is small: the mainnet spec is embedded (`--chain mainnet`),
command.rs adjusts four lines, and the miner server and consensus client are
untouched. The release notes state any node from v0.11.1 on is valid, so this
is a binary swap on the same chain id, spec file and credentials.

This is also the first push-triggered node deploy since the cutover, which
is the point: prove the CI path upgrades bob without hand intervention.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YJp25VomsWVZDPM9Fwmhnq

.gitea/workflows/deploy.yaml

@@ -64,7 +64,7 @@ env:
   CHAIN: mainnet
   # Pinned; bump deliberately to upgrade. An unattended upgrade of a validator
   # is how you find out at 3am that a release changed a consensus rule.
-  NODE_VERSION: "0.11.1"
+  NODE_VERSION: "1.0.1"
   # Mainnet launch (2026-09-10 09:09 UTC): the chain spec is published as a
   # file before a binary embeds it, so the node can run from a JSON at
   # /etc/quantus-node/chainspec.json instead of a built-in name. When set, the