Support reflected timedelta addition for Time

[FanWu-ai]

Pull Request Check List

• Added tests for changed code.
• Updated documentation for changed code.

Fix

pendulum.time(12, 30) + timedelta(minutes=15) succeeds, but reversing the operands raises TypeError. Add Time.__radd__ delegating to self.__add__, as DateTime already does. This preserves subclass dispatch and the existing handling of zero, microseconds, midnight rollover, unsupported types and day-containing durations.

Eleven new cases cover native timedelta/Pendulum Duration, carry and rollover, rejected day components, exact result type and subclass overrides. Documentation shows both operand orders and the existing day restriction.

Validation

Linux/Python 3.12.14, unchanged project dependencies and pinned hooks:

• Fresh complete baseline: 1,871 passed / 3 existing skips in each pure-Python and native mode.
• Final source and installed-wheel complete suites: 1,882 passed / 3 existing skips in each mode.
• Exact final tests replayed on pristine source: 9 failures / 14 controls per backend.
• Strict mypy (228 files), all hooks including Rust formatting/Clippy, strict MkDocs, rebuilt release wheel/sdist and strict Twine pass.
• Artifact production-source bytes match; native imports verified. Independent complete reruns and 3,015 additional cases per backend pass.

The unchanged skips cover Windows-only behavior and upstream timezone-transition limits. Strict docs retain existing INFO-level anchor diagnostics; packaging retains an existing Cargo metadata warning. Other Python/OS combinations and hosted CI are not claimed passed.

Prepared and tested with AI assistance (OpenAI Codex); no human review is claimed.

[codspeed]

Merging this PR will not alter performance

⚠️ 1 benchmark spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

• test_parse_iso8601

ℹ️ 1 benchmark has no flame graph

The flamegraph could not be generated because we failed to resolve the symbols in the profiling trace. This happens when we fail to harvest information about language frames.

• test_parse_iso8601

✅ 1 untouched benchmark

---

_{Comparing FanWu-ai:fix-time-reflected-addition-20261012 (3a2b77a) with master (7840d47)}