jif-oai a5e5faf216 Reject legacy [profiles] when using profile-v2 (#22647) ...

## Why

`profile-v2` layers the selected profile file on top of the base user
`config.toml`, but the legacy `[profiles]` table also stores named
profile overrides in that same base file. Allowing both paths during one
load makes it too easy to get a mixed profile where stale legacy
settings still influence a profile-v2 run.

## What Changed

- Detect a legacy `[profiles]` table in the base user config whenever
`--profile-v2` selects a profile file.
- Fail config loading with an `InvalidData` error that tells the user to
move those settings into the selected profile-v2 file or remove
`[profiles]`.
- Add a loader regression covering `--profile-v2` with legacy
`[profiles]` in `config.toml`.

## Testing

- `cargo test -p codex-config
profile_v2_rejects_legacy_profiles_in_base_user_config`

2026-05-15 11:35:42 +02:00

..

examples

Add remote thread config loader protos (#18892)

2026-04-23 10:06:05 -07:00

scripts

Add remote thread config loader protos (#18892)

2026-04-23 10:06:05 -07:00

src

Reject legacy [profiles] when using profile-v2 (#22647)

2026-05-15 11:35:42 +02:00

BUILD.bazel

Extract codex-config from codex-core (#11389)

2026-02-11 10:02:49 -08:00

Cargo.toml

config: add strict config parsing (#20559)

2026-05-13 16:08:05 +00:00