Problem
lib/python/base_cli/config.py treats LOG_DEBUG=1 as a way to activate Python CLI debug logging alongside the documented BASE_CLI_LOG_LEVEL=debug path.
LOG_DEBUG is used by Base wrapper/debug plumbing and mentioned in wrapper-level README text, but it is not clearly documented in the runtime environment table as an internal compatibility signal or public user knob. That makes the debug surface harder to reason about.
Verified from Claude finding: #67, with severity reduced.
Desired outcome
Decide whether LOG_DEBUG is an internal compatibility alias that should be documented as such, or remove the Python-layer alias in favor of the explicit BASE_CLI_LOG_LEVEL setting.
Scope
- Audit wrapper/setup uses of
LOG_DEBUG before removing anything.
- If kept, document its intended ownership and relationship to
BASE_CLI_LOG_LEVEL.
- If removed from Python config, preserve wrapper debug behavior through the explicit supported env var.
Acceptance criteria
- Runtime/debug documentation matches
base_cli.config behavior.
- Wrapper debug modes still work.
- No undocumented user-facing debug path remains unintentionally public.
Problem
lib/python/base_cli/config.pytreatsLOG_DEBUG=1as a way to activate Python CLI debug logging alongside the documentedBASE_CLI_LOG_LEVEL=debugpath.LOG_DEBUGis used by Base wrapper/debug plumbing and mentioned in wrapper-level README text, but it is not clearly documented in the runtime environment table as an internal compatibility signal or public user knob. That makes the debug surface harder to reason about.Verified from Claude finding: #67, with severity reduced.
Desired outcome
Decide whether
LOG_DEBUGis an internal compatibility alias that should be documented as such, or remove the Python-layer alias in favor of the explicitBASE_CLI_LOG_LEVELsetting.Scope
LOG_DEBUGbefore removing anything.BASE_CLI_LOG_LEVEL.Acceptance criteria
base_cli.configbehavior.