No error message on missing acquistion

[thusser]

If the ImagingScript has no settings for acquisition/guiding and no acquisition is given, it fails silently.

[thusser]

Root cause for this is the same one documented in specs/plans/2026-08-15-pydantic-extra-validation.md — the missing error message is a symptom, not the bug.

acquisition_config / guiding_config were placed inside instrument_configs in the task YAML, but they belong on ImagingScript.Configuration, not InstrumentConfig. pydantic v2 defaults to extra="ignore", so both keys were silently dropped, the Configuration-level defaults (enabled=True) applied, and can_run then waited on an acquisition module and autoguider that were never configured. The task was scheduled but never executed, with no error pointing at the config.

The plan fixes it by setting extra="forbid" on the pydantic base model, so a misplaced or misspelled key fails loudly at load time instead of silently producing a task that never runs: https://github.com/pyobs/pyobs-core/blob/main/specs/plans/2026-08-15-pydantic-extra-validation.md

[thusser]

Fixed by #762: setting extra="forbid" on the pydantic config models means a misplaced key like guiding_config/acquisition_config now raises ValidationError at load instead of being silently dropped and applying the wrong defaults with no error.