fix: execution order for logStreams

[kushalshit27]

🔧 Changes

Fix handler execution order to ensure clientGrants processes before logStreams

Solution:

• Added @order('70') decorator to logStreams to ensure it executes after clientGrants (priority 60)

📚 References

• Resolves: #1172

🔬 Testing

• Unit Tests: ✅

📝 Checklist

• All new/changed/fixed functionality is covered by tests (or N/A)
• I have added documentation for all new/changed functionality (or N/A)

[kushalshit27]

@claude

[codecov-commenter]

Codecov Report

❌ Patch coverage is 42.85714% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.17%. Comparing base (d3231b5) to head (8247248).
⚠️ Report is 85 commits behind head on master.

Files with missing lines	Patch %	Lines
src/tools/auth0/handlers/default.ts	50.00%	1 Missing and 1 partial ⚠️
src/tools/auth0/index.ts	0.00%	0 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1175      +/-   ##
==========================================
- Coverage   80.23%   80.17%   -0.07%     
==========================================
  Files         134      134              
  Lines        5096     5100       +4     
  Branches     1013     1014       +1     
==========================================
  Hits         4089     4089              
- Misses        578      579       +1     
- Partials      429      432       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kushalshit27]

@claude

[kushalshit27]

@claude

[github-actions]

Claude finished @kushalshit27's task —— View job

---

Review Progress

• Read project documentation
• Review diff and changed files
• Analyze code quality
• Analyze security concerns
• Analyze performance implications
• Provide inline feedback
• Provide overall assessment

---

Overall Assessment

❌ The PR has several issues that should be addressed before merging. While the order decorator validation is solid, the execution order choice creates ambiguity, the sorting function has a minor inefficiency, lacks defensive NaN handling, and there's no test coverage for the critical sorting logic.

Key Concerns:

1. Order Priority Conflict: Using @order('70') for logStreams creates ambiguity with 4 other handlers at the same priority level. Consider using @order('65') for explicit positioning between clientGrants (60) and other handlers.
2. Missing Test Coverage: The refactored sortByOrder function has no tests despite being critical for handler execution order.
3. Minor Code Quality Issues: Unnecessary array copy and potential NaN edge case in sorting logic.

Strengths:

• Order decorator validation is well-implemented and prevents invalid values
• Documentation in sortByOrder is clear and helpful
• The overall approach to fixing the execution order issue is sound

---

Job Run | Branch: DXCDT-1266-set-order-of-execution-for-tenant