Normalize Python trace agent types

[xTRam1]

Summary

• normalize narada-pyodide sub-agent trace events so SDK enum agents emit frontend-compatible string agent types such as operator instead of legacy numeric values like 2
• make narada-core trace parsing backward-compatible with already-persisted numeric agent_type values in Python sub-agent and Agent Studio agent traces
• add public TypedDict coverage for pythonAgentRun traces and keep Pyodide emission regression coverage in the existing Cloud Browser test file
• bump publish versions: narada-core 0.0.23, narada-pyodide 0.0.52, and narada 0.1.53a2

Why

Deep nested Python APA traces in Cloud Browser can return nested pythonAgentRun traces whose subAgentCall.agent_type is the SDK enum value 2. The trace parser expects the frontend trace contract (operator, generalist, coreAgent, or slash command strings), so parsing fails before the nested trace can complete.

Validation

• uv run pytest packages/narada-pyodide/tests packages/narada/tests -q
• uv run ruff check $(git ls-files '*.py')\n- uv run ruff format --check $(git ls-files '*.py')\n- python -m compileall -q packages/narada-core/src packages/narada-pyodide/src packages/narada-pyodide/tests\n\nNote: whole-repo uv run ruff check . currently walks the untracked .worktrees/ directory in this checkout, so I validated tracked Python files directly.

[sebzhao]

lgtm