Support persistent default listen-addr for spacetime start

[0monish]

Description of Changes

This change allows spacetime start to use a project-configured default listen address from spacetime.json.

Behavior precedence is now:

1. Explicit CLI flag, such as spacetime start --listen-addr 127.0.0.1:5000
2. listen-addr from spacetime.json
3. Built-in default 0.0.0.0:3000

Example:

{
  "listen-addr": "0.0.0.0:4000"
}

With that config in place, spacetime start will start on 0.0.0.0:4000 unless --listen-addr is passed explicitly.

Implementation details:

• spacetime start now checks project config before forwarding to the standalone binary.
• Config lookup uses the existing spacetime.json discovery behavior, including parent-directory search and spacetime.local.json layering.
• The forwarded argument path preserves CLI precedence over config.
• Added unit tests covering detection of explicit --listen-addr and -l forms so config is only injected when the user did not already provide a listen address.
• Updated standalone config documentation to describe the new listen-addr behavior and precedence.

This is backward compatible:

• users without config still get 0.0.0.0:3000
• existing scripts that pass --listen-addr continue to behave the same
• the feature is project-local and works with the existing config-driven workflow

API and ABI breaking changes

None.

This change does not modify any public API or ABI. It only adds an additional configuration source for an existing CLI option while preserving current defaults and CLI override behavior.

Expected complexity level and risk

Complexity: 2/5

This is a small, localized CLI behavior change.

The main interaction point is config precedence between forwarded CLI arguments and project configuration. The implementation is low risk because it:

• preserves the existing standalone default when config is absent
• preserves explicit CLI --listen-addr and -l precedence
• reuses the existing spacetime.json discovery and layering behavior rather than introducing a new config system

The main thing reviewers may want to sanity-check is that the new config-backed behavior only applies when the user did not explicitly pass a listen address.

Testing

Completed:

• cargo fmt
• cargo check -p spacetimedb-cli
• cargo test -p spacetimedb-cli subcommands::start::tests
• cargo clippy -p spacetimedb-cli --all-targets

Reviewer checks:

• Run spacetime start without spacetime.json and confirm it still binds to 0.0.0.0:3000
• Add "listen-addr": "0.0.0.0:4000" to spacetime.json, run spacetime start, and confirm it binds to 0.0.0.0:4000
• Run spacetime start --listen-addr 127.0.0.1:5000 with config present and confirm the CLI flag still wins

[CLAassistant]

All committers have signed the CLA.

[0monish]

When I can get this feature merged this helps a lot as I am using the spacetimedb and Learning along with that.
If it's there, anything that I missed or anything wrong? Please let me know.

[cloutiertyler]

This does not belong here, it should be in this document:

https://github.com/clockworklabs/SpacetimeDB/blob/master/docs/docs/00300-resources/00200-reference/00100-cli-reference/00300-spacetime-json.md

[cloutiertyler]

Actually come to think of it, this configuration doesn't belong in spacetime.json at all. That is meant to be checked in to your project repo. This configuration should be in the cli.toml file.

SpacetimeDB/crates/paths/src/lib.rs

Line 63 in 7143ed9

//! └── cli.toml # CLI configuration

[cloutiertyler]

@0monish spacetime.json is not where this configuration belongs. Instead it should be stored in the cli.toml file. The cli.toml configuration is for configuring options for the spacetime command and other configuration required to run SpacetimeDB Standalone. spacetime.json is project specific configuration instead. So configuration related to your own project, not the CLI or Standalone. I'm going to close this PR, but feel free to open another one with the configuration in the appropriate file.

SpacetimeDB/crates/paths/src/lib.rs

Line 63 in 7143ed9

//! └── cli.toml # CLI configuration