`remote doctor` calls repo.status(progress_cb=progress_cb) unconditionally (core/tasks/remote.py:504). LexisRepository.status grew the parameter; BaseRepository, FileBasedRepository and AggregateRepository did not. Every non-LEXIS backend therefore raises on a routine call: owi-up: {"error": "TypeError: FileBasedRepository.status() got an unexpected keyword argument 'progress_cb'"} Reproduced on both OpenWebSearch.eu clusters against 5.6.0 via POST /remote/doctor/status, where LEXIS reports fully -- per-access ok, dataset counts, zones -- and the s3a mirror reports only this error. Worth more than a signature slip: file-based covers every non-LEXIS repository, which is exactly the class OWILIX is valuable for holding. The case for OWILIX being authoritative for contents rests on it holding repositories LEXIS cannot; a doctor that cannot report on them undercuts that. Accepted and ignored on the base and file-based implementations, forwarded by the aggregate. Ignoring is right for a backend whose status is a local existence check with no progress to report. Recorded as F7 in docs/review/remote_pull_and_mirror_operability_2026-08-04.md.