Manual network.json editor opens with invalid placeholder topology on first-run

[thebracket]

During fresh-install verification, the first-run page that says LibreQoS must be configured offers a manual editing path. Clicking Edit network.json immediately opens the Network Layout editor with placeholder-looking nodes named 0, 1, 2, etc. Each row shows Download: undefined Mbps and Upload: undefined Mbps.

If the operator clicks Save Changes right away, the editor reports an error. This is confusing for new users because the UI presents the editor as the next setup step, but the starting state is already invalid.

Expected behavior:

• The manual network.json editor should open with a valid starter topology, an empty-state flow, or a clear required-action prompt.
• Save should be disabled until the topology is valid, or the editor should explain what must be entered before saving.
• New users should not land on a screen full of numeric placeholder nodes with undefined rates.

Observed behavior:

• From the first-run/manual editing prompt, Edit network.json opens an invalid topology immediately.
• Nodes appear as 0, 1, 2, etc.
• Rate badges show Download: undefined Mbps and Upload: undefined Mbps.
• Saving immediately produces an error.

Impact:

• Fresh installs using manual topology setup hit a confusing invalid state before they have made any edits.
• This makes the first-run setup path feel broken even though the broader install may have succeeded.

Notes:

• Found while testing a fresh install from the SSL/Caddy package build.
• This is unrelated to the Caddy/SSL scope and should be tracked separately.