Skip to content

fix(setup): Honor active profile when saving configuration - #85

Merged
4ndreello merged 1 commit into
mainfrom
fix/honor-active-profile-in-setup
Sep 15, 2026
Merged

4ndreello merged 1 commit into
mainfrom
fix/honor-active-profile-in-setup

Conversation

@4ndreello

Copy link
Copy Markdown
Owner

Make codedeck setup target the profile that runtime actually resolves.

When activeProfile was set, setup without --profile still wrote top-level agents, leaving those edits ineffective and allowing stale duplicate role bindings. Interactive and batch setup now share target resolution, explicit --profile still works, and no active profile preserves base-config behavior.

A missing active profile now fails before model discovery or config writes. doctor reports the selected profile and surfaces resolution errors so role bindings can be attributed to the configuration that actually runs.

Focused profile, setup wizard, and doctor tests pass, along with the TypeScript build.

Make interactive and batch setup target the active profile by default so the configuration setup matches runtime resolution. Fail clearly when the active profile is missing and expose the selected profile in doctor output.
@sonarqubecloud

Copy link
Copy Markdown

@4ndreello
4ndreello marked this pull request as ready for review September 15, 2026 17:14
@4ndreello
4ndreello merged commit 1fc4ec8 into main Sep 15, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant