The local end-to-end environment runs jobs on a Kimi coding-plan key while the rig is down. Three things kept that from working by configuration alone; each is now a configuration value that folknet leaves unset, so folknet and the development box run one code path: - jobs/src/inventory.rs used_providers() counted every pi-backed model as the self-hosted `gateway`. It now takes a named model's provider from its alias's `provider` in bench/folknet.json (alias_provider(), default `gateway`), so a Kimi job is checked and recorded under its own provider. The `gateway` service is needed only when a `gateway` model is named. - bench/folknet.json declares `kimi-for-coding` (provider `kimi`) and the `kimi` provider, billed by subscription because the key is a coding-plan key. - Kimi refuses pi's `developer` role. jobs/scripts/pi-session.sh passes NEV_MODEL_COMPAT, a JSON object from the environment or .env, to pi as the model's `compat`; the box's ~/.lane-model-env sets it. The test comparing allowed providers with manifest PROVIDERS leaves out providers only an alias names. clear_agent_env() removes NEV_MODEL_COMPAT so a lane that exports it does not change what the jobs tests see. Verified through the development box's lane: cargo test -p jobs, and the harness folknet and wording tests. The fixture Dagu job passed on kimi-for-coding.