🚀 feat: Advanced Analytics & Insights Platform

[adrianwedd]

Summary

• Implemented comprehensive career intelligence system with predictive modeling
• Added executive-grade analytics dashboard with 5 specialized views
• Integrated market intelligence and career trajectory visualization

Features

• 📊 Overview Dashboard: Executive summary with key metrics and insights
• 📈 Career Trajectory: Progression analysis with growth projections
• 🌍 Market Analysis: Industry trends and competitive positioning
• 🔮 Predictions: AI-powered forecasting with scenario planning
• 💡 Recommendations: Strategic guidance with prioritized actions

Technical Details

• Professional UI with responsive design and accessibility support
• Keyboard shortcuts (Ctrl/Cmd + Shift + A)
• Test page available at /test-analytics.html
• Integrates seamlessly with existing CV infrastructure

Testing

• ✅ Local testing completed
• ✅ Staging deployment successful
• ✅ All quality gates passed

Completes GitHub issue #122

To fix the problem, we should ensure that all LaTeX special characters, including backslash, are escaped in a way that prevents injection and rendering issues. The best way is to use a well-tested library such as latex-escape, but if we must implement it ourselves, we should escape backslashes first, then all other special characters, using a single regular expression and mapping. The escaping should be done in a way that does not introduce new unescaped backslashes. In the file assets/cv-template-engine.js, in the escapeLaTeX method (lines 690-697), we should replace the current implementation with one that escapes all LaTeX special characters, including backslash, using a mapping and a single .replace call with a global regular expression. We do not need to add any new imports, as this can be done inline.

To fix the problem, we should use a well-tested LaTeX escaping library if possible. If not, we must ensure that all LaTeX special characters, including the backslash, are escaped in a way that is safe for LaTeX documents. The best way to do this is to replace each special character with its LaTeX-escaped equivalent, and to ensure that the backslash is escaped first, before any other replacements, to avoid double-escaping. The fix should be applied to the escapeLaTeX method in assets/cv-template-engine.js, lines 690-697. If we cannot use an external library, we should use a single .replace() with a callback or a sequence of replacements that covers all special characters, with backslash first.

---

To fix the problem, we should parse the project.github URL and check that its host is exactly github.com (or, if desired, a whitelist of allowed GitHub hosts such as github.com and www.github.com). This prevents malicious URLs that merely contain "github.com" elsewhere from passing the check. The best way to do this in modern JavaScript is to use the built-in URL class to parse the URL and compare the host or hostname property. The change should be made in the fetchGitHubStatistics method, specifically in the filter function at line 92. No new dependencies are required, as the URL class is available in all modern browsers and Node.js.

---