fix(workflow-executor): accept LOG_LEVEL case-insensitively

[PMerlet]

Problem

When the executor runs alongside other services sharing an environment/secret, LOG_LEVEL is often set in lowercase (e.g. info). The CLI validated it against a strict Debug | Info | Warn | Error enum, so info threw ConfigurationError at startup → the process exits → the container never serves (deploy goes unhealthy, 100% 5xx).

Hit in real life deploying the executor as a Beanstalk service: the shared staging/env-vars secret sets LOG_LEVEL=info, crashing the executor on boot.

Fix

parseLoggerLevelEnv now normalizes the raw value to canonical case (raw[0].toUpperCase() + rest.toLowerCase()) before validating. So info, INFO, debug, WARN, … are accepted and mapped to Info/Debug/Warn; genuinely unknown levels (trace, verbose, …) still throw the same ConfigurationError.

Tests

• New: info/INFO/debug/WARN/error parse to the canonical level.
• Updated: the "throws on invalid" cases no longer include debug/info (now valid); trace/fatal/verbose/xxx still throw.
• Full cli.test.ts green (68 tests).

🤖 Generated with Claude Code

Note

Accept LOG_LEVEL env var case-insensitively in workflow-executor

Normalizes the LOG_LEVEL value in parseLoggerLevelEnv by capitalizing the first character and lowercasing the rest before validating against the schema, so values like info, INFO, or Warn are all accepted. Tests are updated to cover the new case-insensitive behavior and remove previously invalid cases that are now valid.

^{Macroscope summarized 9c9c5c6.}

[qltysh]

Coverage Impact

This PR will not change total coverage.

Modified Files with Diff Coverage (1)

Rating	File	% Diff	Uncovered Line #s
	packages/workflow-executor/src/cli-core.ts	100.0%
	Total	100.0%

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.