fix: avoid penalizing backend projects for missing live demos (#271)

[thvvamshi]

Fixes #271

Summary

This update improves the fairness of resume evaluation by ensuring candidates are not penalized for missing live demos when their projects do not typically require one.

The evaluation prompt now requires projects to be classified before scoring. Live demo expectations are applied only to frontend/web applications, while backend, infrastructure, distributed systems, CLI tools, libraries, and machine learning projects are evaluated using repository evidence, implementation quality, architecture, and documentation instead.

Before

• Backend and system-focused projects could lose points simply because they did not include a public live demo.
• This unfairly affected projects such as REST APIs, distributed systems, cloud infrastructure, and CLI tools where public demos are generally not expected.

After

• Live demo verification is applied only to Frontend/Web applications.
• Backend APIs, Infrastructure, Distributed Systems, CLI tools, Libraries, and Machine Learning projects are no longer penalized solely for missing public demos.
• Projects are classified before evaluation so the appropriate scoring rules are applied consistently.

Validation

Tested locally using:

• Ollama (gemma3:4b)
• Gemini 2.5 Flash

Validated across multiple resume types, including:

• Backend-heavy profiles
• Frontend and full-stack projects
• Internship-based resumes
• Cases with missing or invalid project links

The updated evaluation consistently avoids penalizing backend-focused projects for missing live demos while preserving the existing verification behavior for frontend applications.