Problem

The initial fix PR: #187 introduced a regression where running wizards generate-keys without any configuration would always panic with called Option::unwrap() on a None value.

The wizards generate-keys command was panicking with called Option::unwrap() on a None value when run without explicitly setting configuration files. This occurred because create_chain_spec() was calling load_spec("") with an empty string, which attempted to load custom chainspec configuration files that don't exist in a default setup.

Solution

Modified create_chain_spec() to respect the existing configuration system:

• Use the chain value from SubstrateCfg (configurable via CHAIN env var or config preset)
• Default to "dev" when no chain is specified

// Dev environment (default)
./midnight-node wizards generate-keys

// Or explicitly
CFG_PRESET=dev ./midnight-node wizards generate-keys

// QA network
CFG_PRESET=qanet ./midnight-node wizards generate-keys

// Preview network  
CFG_PRESET=preview ./midnight-node wizards generate-keys

// Using a named chain (dev, local)
CHAIN=local ./midnight-node wizards generate-keys

// Using a path to a chain-spec file
CHAIN=res/node-dev-01/chain-spec-raw.json ./midnight-node wizards generate-keys

Note: When deploying the midnight-node binary to a different location, the res directory must be copied alongside it. This directory contains required configuration files (cfg) and mock data (mock-bridge-data, genesis, dev) that the binary expects to find relative to its working directory.