Fix naming conventions: Replace single-letter variables and generic constants with descriptive names

[Copilot]

Overview

This PR addresses naming convention issues throughout the codebase to follow TypeScript/JavaScript best practices and improve code readability. All single-letter variables, cryptic constants, and unclear function names have been replaced with descriptive, self-documenting names.

Changes Made

Constants (src/constants.ts)

Replaced generic single-letter constant names with descriptive alternatives:

• C → RD_INCREASE_CONSTANT - Clearly indicates its use in RD increase calculations over time
• TAU → VOLATILITY_CONSTRAINT - Better describes its role as a constraint on volatility changes
• EPSILON → CONVERGENCE_TOLERANCE - More accurately reflects its purpose in iterative convergence

Function Names (src/glickoHelper.ts)

• g() → calculateGValue() - Single-letter function replaced with meaningful name describing the g-function calculation in Glicko-2
• f() → volatilityFunction() - Helper function now has a descriptive name indicating its role in volatility updates

Variables in glickoHelper.ts

Improved clarity throughout the algorithm implementation:

• t → timeInMonths - Time calculation variable now self-explanatory
• A, B, C → iterationA, iterationB, iterationC - Iteration variables in Illinois algorithm
• fA, fB, fC → functionValueA, functionValueB, functionValueC - Function evaluation results
• i, j → firstTerm, secondTerm - Mathematical terms in volatility function
• k → multiplier - Multiplicative factor in boundary search
• a → initialA - Initial value for iteration

Variables in Glicko2.ts

Replaced abbreviated variables with full descriptive names:

• E → expectedScoreValue - Expected score calculation result
• v → varianceValue - Variance of performance
• del → deltaValue - Delta value in rating update
• Removed unused gFunction variable

Benefits

✅ Improved Readability: Code is now self-documenting with clear variable and function names
✅ Better Maintainability: Future developers can understand the code without needing extensive comments
✅ Follows Best Practices: Adheres to TypeScript/JavaScript naming conventions
✅ No Breaking Changes: All changes are internal; the public API remains unchanged
✅ Verified Functionality: Build passes and functionality testing confirms correct behavior

Testing

• TypeScript compilation: ✅ Successful
• Functionality test: ✅ Rating calculations produce correct results
• No regression in existing behavior

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Nomenclature fixes - naming conventions</issue_title>
<issue_description></issue_description>

<agent_instructions>Look for naming convention issues in the repo, and correct all to make sure they follow proper coding standards and best practices.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Fixes #3

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.