pub fn claude_legacy_launch() -> boolExpand description
Resolve D-11’s legacy-launch opt-out (31-04) from
DEVFLOW_CLAUDE_LEGACY_LAUNCH.
Environment only, deliberately: D-11 specifies one flag and one environment
variable, and nothing else. There is no devflow.toml key, so this takes no
project_root — a standing per-project default for an escape hatch is
exactly the “used routinely, erodes what it protects” shape D-11 warns
about. --legacy-claude-launch supplies the other half, OR-ed in
commands::start / pipeline_launch::resume.
The value is PARSED as a bool, not merely tested for presence (W4). A
naive env::var(..).is_ok() would make DEVFLOW_CLAUDE_LEGACY_LAUNCH=false
enable the legacy path — an accidental-reach path D-11 forbids. Garbage
warns and is ignored rather than enabling; the escape hatch fails CLOSED.
Read through [env_value] with the variable name as a literal, matching
yes_ship and external_verify_enabled. A const-mediated read compiles
and works identically but is INVISIBLE to
doc_check::source_read_env_vars, which would then pass green while the
variable went undocumented — the “by blindness” failure 31-02 recorded.