OtlpLogger emits title-cased severityText in Effect 4

[schickling-assistant]

Problem

In effect@4.0.0-beta.102, the OTLP logger emits title-cased severityText values such as "Info". Effect 3 emitted the conventional uppercase value "INFO".

The numeric semantic remains correct: the same record emits severityNumber: 9.

Cause

OtlpLogger maps the number explicitly but forwards the new LogLevel string directly:

severityNumber: logLevelToSeverityNumber(options.logLevel),
severityText: options.logLevel,

Because Effect 4 changed LogLevel to title-cased string literals, the OTLP text changed as a side effect even though the severity number mapping did not.

Expected

Normalize OTLP severityText to the conventional uppercase short name (TRACE, DEBUG, INFO, WARN, ERROR, FATAL) while preserving the existing numeric mapping.

This matters for consumers that filter logs by severity_text; consumers using severityNumber are unaffected.

Posted on behalf of @schickling

field	value
agent_name	co1-spur
agent_session_id	2897548b-ef37-4215-b892-fcf0b69651bb
agent_tool	Codex CLI
agent_tool_version	0.145.0
agent_runtime	Codex CLI 0.145.0
agent_model	unknown
runtime_profile	/nix/store/mnx8agbdq3wiyb6vz63lhgscgazkrn98-coding-agent-runtime-profile/share/coding-agents/profile.json
skills_manifest	/nix/store/5r69m9k2llmri3na81518zx0a7y0d3cn-agent-skills-corpus/share/agent-skills/manifest.json
worktree	effect-utils/schickling-assistant/2026-07-29-effect4-w11-utilsdev
machine	dev3
tooling_profile	dotfiles@0fb7e03

[tim-smart]

Severity text is "This is the original string representation of the severity as it is known at the source.", so we shouldn't apply transformations to the effect literals.