Part of #873. FORGE_CREW_CONCURRENCY, FORGE_CHECKS_CONCURRENCY, FORGE_CHECK_SHARDS (which childEnv() does not even pass to checks and crew shells today) and FORGE_CELLS_EGRESS are read once at boot. A number should change from Settings (admin) and MCP, take effect on the next pick without a restart, be audited, and the env value stay as the boot default. Done means: the admin lowers check concurrency on the settings page and the next check honours it, with a test; the check command and crew shells receive the shard count from the setting, not from the pod env.
Part of #873. FORGE_CREW_CONCURRENCY, FORGE_CHECKS_CONCURRENCY, FORGE_CHECK_SHARDS (which childEnv() does not even pass to checks and crew shells today) and FORGE_CELLS_EGRESS are read once at boot. A number should change from Settings (admin) and MCP, take effect on the next pick without a restart, be audited, and the env value stay as the boot default. Done means: the admin lowers check concurrency on the settings page and the next check honours it, with a test; the check command and crew shells receive the shard count from the setting, not from the pod env.