"""Side-effect imports — populates the ``@isolation_check`` registry.

Importing this package triggers every per-category submodule import,
which in turn registers every check via the ``@isolation_check``
decorator at module-load time.

Wave 1 (pure core) ports every check category, including the network
checks (``checks.network``): their only adapter coupling was the
``QUARANTINE_NETWORK_NAME`` constant, now sourced from the pure
:mod:`mgf.vm.core.security.isolation.context`.
"""

from __future__ import annotations

# Order is alphabetical (matches ruff/isort default). Findings end up
# in alphabetical-by-id order in IsolationReport, which is fine —
# consumers re-group by category / severity at render time, so
# registration order doesn't affect user-facing output.
from mgf.vm.core.security.isolation.checks import cpu_firmware as _cpu_firmware  # noqa: F401
from mgf.vm.core.security.isolation.checks import devices as _devices  # noqa: F401
from mgf.vm.core.security.isolation.checks import disk as _disk  # noqa: F401
from mgf.vm.core.security.isolation.checks import display as _display  # noqa: F401
from mgf.vm.core.security.isolation.checks import host as _host  # noqa: F401
from mgf.vm.core.security.isolation.checks import hostdev as _hostdev  # noqa: F401
from mgf.vm.core.security.isolation.checks import memory as _memory  # noqa: F401
from mgf.vm.core.security.isolation.checks import network as _network  # noqa: F401
from mgf.vm.core.security.isolation.checks import runtime as _runtime  # noqa: F401
from mgf.vm.core.security.isolation.checks import shares as _shares  # noqa: F401
