ref(config): Remove the setup profile system

[4ndreello]

Why

Profiles overlaid a named snapshot on top of the base config, and the result drifted: doctor reported one setup while launches resolved another. Rather than patch the overlay, this removes it. There is one setup again, the top-level config, so what doctor prints is what run and open use.

What changes

• Drop the codedeck profile command (src/cli/commands/profile.ts).
• Drop --profile from run, open and setup.
• Remove the overlay from src/config/config.ts (resolveEffectiveConfig, ProfileSnapshot, name parsing, listing) and the profile branch of resolveSetupTarget/buildSetupPlan in src/config/setup.ts.
• doctor prints plain Roles with no Profile section, and doctor --json no longer carries activeProfile/activeProfileError.
• The web setup page has only the global target.
• README and CLAUDE.md no longer document profiles.

Existing profiles/activeProfile keys in a user config are left alone: nothing reads them, and every setup path (CLI, wizard, web) preserves them on save. No config data is deleted.

Spec and validation: .specs/features/remove-profiles/.

Verification

• npx tsc --noEmit -p . passes.
• npx vitest run tests/doctor-roles.test.ts tests/open-action.test.ts tests/run-role.test.ts tests/setup-cli-contract.test.ts tests/setup-plan.test.ts tests/setup-web.test.ts tests/setup-wizard.test.ts: 7 files, 197 tests passed.
• Mutation probe: reintroducing the active-profile overlay in run.ts and doctor.ts fails the two new tests (2/2 killed). Reverted, they pass again.
• Built CLI: codedeck profile list exits with unknown command 'profile', run --profile x with unknown option '--profile', and doctor shows Roles from the top-level bindings.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud