Selected plugin fails registration but preflight still reports ready

[gtdebz]

I was testing a third-party module whose driver has one missing Python dependency. Core printed a registration warning at startup and kept the built-in commands available. I continued with the module path. Validate completed and preflight reported ready, but apply failed because the selected driver was unavailable.

Keeping unrelated commands available is useful. For the selected module, I expected preflight to stop before apply. HYOPS_STRICT_PLUGINS=1 catches the registration failure earlier, but it also changes the behaviour of the whole command rather than only the selected module path.

[jeleel-muibi]

Can you confirm that the execution profile selects the same driver named in the registration warning? Please also compare the exit status from validate, preflight, and apply with normal startup, then run validate once with HYOPS_STRICT_PLUGINS=1.

[gtdebz]

Yes. The profile selects the same entry-point name shown in the warning.

This is Core v0.1.3 on Ubuntu 24.04. With normal startup, validate and preflight both returned 0. Apply returned 1 when Core tried to resolve the driver.

With HYOPS_STRICT_PLUGINS=1, validate returned 1 during startup before the
module was checked.

[jeleel-muibi]

Does the normal preflight output mention the failed registration, or does it report the selected module as ready without a warning?

[gtdebz]

It reports the module as ready. The output names the module and execution profile, but it does not mention that the selected driver failed registration. The warning only appears during startup.

[jeleel-muibi]

The selected-driver readiness check is the gap. Tolerant startup should keep unrelated built-in commands available, but preflight should not report ready when the selected execution profile depends on a driver that did not register. The change can stay limited to selected-driver readiness. Strict plugin mode does not need to change.

[gtdebz]

Agreed. I opened #277 focused improvement with that scope. Validate can continue checking the module contract, but preflight should stop before apply when its selected driver is unavailable.