ENG-10963 feat(log): deprecate the legacy console logging helpers (5/5)

[FarhanAliRaza]

With every call site migrated, console.debug/info/success/log/warn/error/timing now emit a runtime deprecation warning (removal in 1.0) and are marked with typing_extensions.deprecated for type-level warnings. Behavior is otherwise unchanged; the interactive Rich features (print/rule/status/ask/progress) remain first-class.

This must land last: the deprecation markers only pass CI once no in-repo call site uses the helpers.

Stack (ENG-10963)

#6863 → #6864 → #6865 → #6866 → this.
Merge in order; each PR is based on the previous branch.

[linear-code]

ENG-10963

[greptile-apps]

Greptile Summary

The PR deprecates the legacy console logging helpers while retaining their runtime rendering behavior.

• Adds runtime and type-level deprecation notices for the seven logging-shaped helpers.
• Separates the legacy debug implementation so timing avoids a duplicate warning.
• Adds release notes and regression coverage for output delegation and Rich keyword arguments.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
packages/reflex-base/src/reflex_base/utils/console.py	Adds runtime and static deprecation markers while preserving the helpers’ legacy rendering paths.
tests/units/reflex_base/utils/test_log.py	Adds coverage for shim output and preservation of Rich rendering arguments.
packages/reflex-base/news/+eng-10963-console-deprecate.deprecation.md	Documents the deprecated helpers, replacements, and unaffected interactive console APIs.

_{Reviews (8): Last reviewed commit: "feat(log): deprecate the legacy console ..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 27 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing farhan/eng-10963-log-5-deprecate-console (6b8e0a7) with farhan/eng-10963-log-4-hosting-cli (af9cfbe)²}

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 farhan/eng-10963-log-4-hosting-cli (ff238bf) during the generation of this report, so 291eee6 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a3b76f45c9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[cubic-dev-ai]

All reported issues were addressed across 3 files

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

Re-trigger cubic</sub>