Spike: can a settings/env knob make daemon forks keep --dangerously-load-development-channels?

Find a surface that makes a daemon respawn inherit the channels flag, or blocks the fork. Candidates seen in CC 2.1.259 binary, UNVERIFIED: CLAUDE_CODE_DISABLE_BG_EXIT_HANDOFF, CLAUDE_CODE_DAEMON_COLD_START; dispatch schema source=shell|slash|fleet|spare|respawn with launch.flagArgs/respawnFlags. Test on a SCRATCH session (never a live agent): set the env in ~/.claude/settings.json env block on a throwaway cwd, trigger the same path (/usage then the 1M model switch), check ~/.claude/daemon/roster.json respawnFlags and the fork argv. Deliverable: either a settings/env line for cc-settings-drift-check to enforce, or a written negative result. Needs Elazar GO before touching ~/.claude/settings.json.