Raúl MarínandClaude Opus 4.8 e6ccc02b4b Fix client-side compatibility by not transmitting compatibility-derived settings ...

The earlier server-side approach could not distinguish a compatibility-synthesized
setting from a genuine explicit override (both arrive as identical changes), so it
broke when the client's `compatibility` matched the profile's pinned version (the
reverted value was then the only setting transmitted, with no `compatibility` in the
batch to explain it) and it silently dropped genuine HTTP/SQL overrides.

Fix it on the client instead: the native client resets settings whose value was set
only by `compatibility` before transmitting them, so the server re-derives them from
`compatibility` itself and honors its own constraints (for example a profile pinning a
setting read-only). Server-to-server settings propagation is left unchanged. The
server-side `SettingsConstraints` heuristic is reverted.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

2026-07-20 21:10:35 +02:00

..

configs

…

__init__.py

…

test.py

…