jif-oai 932f72c225 fix: reject legacy profile selectors (#24059) ...

## Why

`--profile` now selects `<name>.config.toml`, so the legacy `profile`
selector should not be reintroduced through config write or MCP tool
paths. A matching legacy selector in base user config also needs the
same migration guard as a matching legacy `[profiles.<name>]` table so
profile loading fails with one clear migration error instead of mixing
the old and new profile models.

## What

- reject non-null app-server config writes to the top-level legacy
`profile` selector
- make `--profile <name>` reject base user config that still selects the
same legacy `profile = "<name>"` value, alongside the existing matching
legacy profile-table guard
- reject removed MCP `codex` tool fields such as `profile` by denying
unknown tool-call parameters and exposing that restriction in the
generated schema
- add regression coverage for the app-server write paths, config loader
guard, and MCP tool input/schema behavior

## Verification

- targeted regression tests cover the new app-server, config loader, and
MCP rejection paths

2026-05-22 13:19:47 +02:00

..

src

fix: reject legacy profile selectors (#24059)

2026-05-22 13:19:47 +02:00

tests

Support multi-environment apply_patch selection (#21617)

2026-05-11 16:33:44 -07:00

BUILD.bazel

[bazel] Bump rules_rs and llvm (#13366)

2026-03-04 01:59:32 +00:00

Cargo.toml

extension: wire extension registries into sessions (#21737)

2026-05-11 11:38:18 +02:00