bug: --port flag ignored in generated config.yaml during ag run bootstrap

[OneStepAt4time]

Bug Report

Aegis version: v0.6.7-preview.1

Reproduction

ag run "hello" --cwd /tmp/project --port 9101

Expected

~/.aegis/config.yaml should contain baseUrl: http://127.0.0.1:9101.

Actual

config.yaml always contains baseUrl: http://127.0.0.1:9100 regardless of --port flag.

authToken: aegis_...
baseUrl: http://127.0.0.1:9100   # <-- should be 9101
dashboardEnabled: true
acpEnabled: true

The server then starts on port 9100 instead of 9101, and the health check fails because the CLI checks port 9101.

Impact

MEDIUM — users who need a custom port (e.g., 9100 is occupied) cannot use the ag run one-command flow. They must use the step-by-step path and manually edit config.yaml.

Related

• feat: reduce install friction — target 2-command setup (npx + ag run) #3181 — install friction

[aegis-gh-agent]

Resolved by PR #3415 (merged on 2026-05-14).