• Revert automatic server-list.json fallback in classic frontend
• Restore original standalone vs multi-server initialization logic
• Bump version to v6.0.1

Version bump to v6.0.1

• Update version string from v6.0.0pre1 to v6.0.1

speedtest.js

Restore original server initialization logic

• Remove automatic server-list.json fallback for standalone installations
• Restore original logic: standalone mode skips server selection entirely
• Multi-server mode handles explicit URL strings or hardcoded arrays
• Simplify initServers function by removing intermediate loading state

index-classic.html

Description

speedtest.js now logs version v6.0.1 at runtime, but package.json still declares version 6.0.0,
which can confuse users and tooling relying on package metadata.

Code

speedtest.js[R51-53]

  console.log(
-    "LibreSpeed by Federico Dossena v6.0.0pre1 - https://github.com/librespeed/speedtest"
+    "LibreSpeed by Federico Dossena v6.0.1 - https://github.com/librespeed/speedtest"
  );

Evidence

The PR changes the logged version string to v6.0.1, while the package manifest still reports 6.0.0
in the checked-out PR branch code, leaving inconsistent version reporting.

speedtest.js[46-54]
package.json[1-6]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`speedtest.js` prints `v6.0.1` at runtime, but `package.json` still reports version `6.0.0`, creating inconsistent version reporting.

### Issue Context
This PR updates only the runtime banner string; the repo’s package metadata remains unchanged.

### Fix Focus Areas
- package.json[1-6]
- speedtest.js[46-54]

### Suggested fix
Either:
1) Bump `package.json.version` to `6.0.1`, or
2) Revert/adjust the `console.log` banner to match the intended package version.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools