Optimize & Minify DevRank Data Schema

Input from Gemini 3 Pro:

✦ Optimization Success Report

The data schema optimization and minification have been successfully applied.

Results:

• File Size: Reduced from ~6.0 MB to 1.60 MB
• Reduction Rate: ~73%

Key Changes:

• Structure: Migrated users.json to a "One-Record-Per-Line" format with short keys (e.g., l for login, tc for total_contributions).
• Avatars: Now stored as integer IDs instead of full URLs.
• Years: Converted from an object map to a sequential array.
• Orgs: Limited to top 5 and stored as compact tuples.

This optimization ensures the application remains performant and scalable as we approach the 100k user target.

Input from Gemini 3 Pro:

✦ Optimization Update (Grid & Memory)

Following the schema minification, we identified and resolved integration issues with the UI:

1. Grid Mapping Fix: Updated DevRank.store.Contributors to use keyProperty: 'l' (matching the minified login key). This resolved an issue where grid rows were assigned temporary negative IDs instead of the correct usernames.
2. Memory Optimization: Refactored DevRank.model.Contributor to remove the redundant years object field. The Model now maps the individual year fields (e.g., y2023) directly from the raw data array, eliminating the need to construct an intermediate object map in memory.
3. Data Logic: Updated the year field calculation logic to robustly handle both raw data and model instance contexts.