fix(doctor): use configured localnet port instead of hardcoded 3040

[teyrebaz33]

Closes #40

Problem

doctor hardcodes 127.0.0.1:3040 for the sequencer port check, ignoring the localnet.port value in scaffold.toml. This means projects using a non-default port always see the sequencer reported as unreachable in doctor output.

Fix

Use project.config.localnet.port to build the address and label dynamically — consistent with how localnet start, localnet status, and localnet stop already behave.

Changes

• src/commands/doctor.rs: derive localnet_addr and sequencer_port_label from project config
• tests/cli.rs: new test verifying doctor uses configured port, not hardcoded 3040

Testing

cargo test doctor_uses_configured_localnet_port

[fryorcraken]

json parameter seems to be from another change/PR?

[teyrebaz33]

You're right, thanks for catching that! The json field on Logs is part of PR #39 (feat: add --json flag to localnet logs). This PR (#41) only changes src/commands/doctor.rs to use project.config.localnet.port instead of the hardcoded 3040. The extra commit appeared here because this branch was created from the same base. I can rebase to isolate just the doctor fix if that would help.

[weboko]

seems the unrelated change is still here

[teyrebaz33]

I've rebased this PR onto master so it now contains only the doctor fix commit — the json field on Logs is no longer included here (that belongs to #39). The branch has been updated to fix/doctor-uses-configured-port-v2.

[teyrebaz33]

Branch has been force-pushed and now contains exactly 1 commit with 2 files changed: src/commands/doctor.rs (the port fix) and tests/cli.rs (the test). No unrelated changes remain.

[fryorcraken]

Thanks @teyrebaz33. Holding off on a detailed review — what review is finding points at process gaps worth closing first. Please revise against the points below, then ping me for another pass. The repo's CONTRIBUTING.md is the contract these come from, in particular the "What Makes a High-Quality PR" section.

• Read your own diff and run the local checks before pushing
• Keep the PR to a single concern
• Make sure the PR description and commits match what the diff actually does
• Walk the repo's validation flow before asking for review