## Bootstrap and Shell Service Bring-Up

- Roots: `app_bootstrap_main` at `0x00484440`, `bootstrap_init_shell_window_services` at
  `0x004840e0`, and `shell_install_global_controller` at `0x0051ff90`.
- Trigger/Cadence: one-time bootstrap handoff immediately after CRT completion.
- Key Dispatchers: `app_bootstrap_main`, `bootstrap_init_shell_window_services`,
  `shell_install_global_controller`, `shell_service_pump_iteration`, graphics config load or
  default-init helpers, runtime capability probes, and early shell service initializers under the
  `0x004610..0x0053f0..` branch.
- State Anchors: global shell controller pointer `0x006d4024`, sibling display/runtime globals under
  `0x006d402c` and `0x006d4030`, and host capability flags gathered by
  `bootstrap_probe_system_profile`.
- Subsystem Handoffs: after the global shell controller has been installed the bootstrap path enters
  the repeating `shell_service_pump_iteration` loop, which services shell-state work and hands each
  iteration down into the controller frame path; when the shell lifetime ends this same bootstrap
  path tears the shell bundle down and returns to `app_bootstrap_main`.
- Evidence: `startup-call-chain.md`, function-map rows for `app_bootstrap_main`,
  `bootstrap_init_shell_window_services`, `shell_install_global_controller`,
  `shell_service_pump_iteration`, `shell_load_graphics_config_or_init_defaults`,
  `shell_reset_display_runtime_defaults`, and related graphics setup helpers.
- Current Boundary: current local evidence still carries gameplay entry and later in-engine world
  stepping through the same shell-owned outer coordinator family before the shell bundle is
  destroyed; no detached gameplay-owned outer loop has surfaced in the local static pass.