teknium1 a6bab19ab7 test(docker): a named profile's gateway start refuses without --force; --force still drives its slot ...

The container harness pinned the pre-multiplex-only contract (a named profile brings up its
own s6-supervised gateway). Under #118273 + this PR that start is refused: the slot stays
registered (DOWN) so `--force` has something to drive, and the refusal names `--force` and
`migrate --multiplex`. Split into the refusal invariant and the `--force` start/stop control.

2026-09-21 11:40:48 -07:00

..

__init__.py

…

conftest.py

…

test_config_migration.py

…

test_container_restart.py

…

test_dashboard.py

…

test_docker_exec_privilege_drop.py

…

test_dump_build_sha.py

…

test_gateway_bootstrap_state.py

…

test_gateway_run_supervised.py

…

test_home_override_scripts.py

…

test_immutable_install_permissions.py

…

test_immutable_install.py

…

test_license_file_present.py

…

test_log_dir_seed.py

…

test_main_invocation.py

…

test_profile_gateway.py

…

test_puid_pgid_remap.py

…

test_s6_profile_gateway_integration.py

…

test_smoke.py

…

test_sqlite_runtime.py

…

test_stage2_browser_discovery.py

…

test_tini_compat_shim.py

…

test_toplevel_chown.py

…

test_tui_passthrough.py

…

test_tui_prebuilt_bundle.py

…

test_user_flag_guard.py

…

test_zombie_reaping.py

…