Chore/2505 standardize user context

[settler-av]

🔗 Related Issue

Closes #2505

---

📝 Summary

Standardizes user context dependency naming across endpoints by renaming _user to current_user_ctx for consistency and clarity.

🏷️ Type of Change

• Bug fix
• Feature / Enhancement
• Documentation
• Refactor
• Chore (deps, CI, tooling)
• Other (describe below)

---

🧪 Verification

Check	Command	Status
Lint suite	make lint	✅
Unit tests	make test	✅
Coverage ≥ 80%	make coverage	✅

---

✅ Checklist

• Code formatted (make black isort pre-commit)
• Tests added/updated for changes
• Documentation updated (if applicable)
• No secrets or credentials committed

---

[crivetimihai]

Thanks for tackling the naming standardization, @settler-av! The intent is good — consistent naming makes the codebase more readable. However, I have a concern about the current scope:

The PR renames _user → current_user_ctx in 4 files, but misses 3 files that still use _user (cancellation_router.py, llmchat_router.py, tokens.py), and doesn't touch the ~240 places that use user=Depends(...). The net effect is going from 2 naming patterns to 3, which makes things less consistent rather than more.

Additionally, the _ = current_user_ctx lines added in ~18 functions to suppress unused-variable warnings add boilerplate — the original _user prefix already conveyed "intentionally unused" by Python convention, more concisely.

Could you either:

1. Expand the scope to cover all user dependency injection points (including the user=Depends(...) pattern), or
2. If this is intended as a phased rollout, document the plan and create follow-up issues for the remaining files?

[settler-av]

Thanks for the review.

I’ve updated only the files listed under #2505 (Phase 1). I’ll incorporate changes in the remaining three files mentioned here, along with the required dependency injection points.

I’ll push new commits to this PR once those updates are done.