* refactor: place shared settings profiles and host contracts with owners * fix: retire stale cleanup validation contacts * refactor: consolidate imports from concrete owners * refactor: bind new card fixture to profile defaults owner * style: format rebased concrete host import * refactor: consolidate project header color owner imports * fix: load released phone readers after folder moves * fix: preserve released chat readers and current owner imports
OMP Source Control AI settings proof
Run ORCA_BACKGROUND_LAUNCH=1 node tests/tools/omp-source-control-ui/run.mjs.
The runner rebuilds the existing background-safe Electron fixture and the production
CommitMessageAiPane with its real styles. It uses disposable HOME/ZDOTDIR/userData,
never reveals a window, and closes its own app after recording evidence under
.bench-fixtures/omp-source-control-*/.
DOM assertions and screenshots cover:
- OMP appears in the commit-message agent menu and can be selected.
- Selecting OMP keeps CLI arguments empty so OMP uses its configured provider/model.
- An explicit
--model provider/exact-modelargument can be saved and remains in the input after the save completes.
The settings persistence adapter is in-memory. This is a rendered production
component check, not a full app IPC, restart-persistence, or generation test. No
generator is called or mocked. Current Source Control AI settings expose action
recipes with CLI arguments; they do not have a Discover Models button. The separate
omp-source-control-discovery.test.ts regression covers production generation
selection with cached models, including SSH host keys.