fix(types): skip ForwardRef resolution for unannotated attribute probes

[benedikt-bartscher]

[greptile-apps]

Greptile Summary

The PR avoids resolving unrelated forward references when probing unannotated attributes.

• Adds an annotation-name check across a class MRO before calling get_type_hints.
• Handles Python 3.14 lazy annotations through annotationlib.
• Adds regression coverage for unannotated probes, unresolved annotations, and PEP 649 behavior.
• Adds a bugfix news entry.

Confidence Score: 4/5

The PR is not yet safe to merge because the annotation-name snapshot remains stale when annotations change after the first probe.

The cached MRO annotation names have no invalidation path, while get_attribute_access_type now relies on that snapshot to decide whether an annotated attribute can be resolved.

Files Needing Attention: packages/reflex-base/src/reflex_base/utils/compat.py, packages/reflex-base/src/reflex_base/utils/types.py

Important Files Changed

Filename	Overview
packages/reflex-base/src/reflex_base/utils/compat.py	Adds MRO-wide annotation-name discovery with Python 3.14 lazy-annotation support.
packages/reflex-base/src/reflex_base/utils/types.py	Gates type-hint resolution on whether the requested attribute is declared in the class MRO.
tests/units/test_attribute_access_type.py	Adds regression tests for unannotated probes, unresolved forward references, and Python 3.14 lazy annotations.
packages/reflex-base/news/+annotation-probe-guard.bugfix.md	Documents the attribute-probe and lazy-annotation fix.

_{Reviews (4): Last reviewed commit: "Merge remote-tracking branch 'upstream/m..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 27 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing benedikt-bartscher:annotation-probe-guard (dc3bc6a) with main (f7c848f)²}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (45b8ed5) during the generation of this report, so f7c848f was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[cubic-dev-ai]

All reported issues were addressed across 5 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>