fix: reclassify skill-only Technical Projects as Skills

[mergemaven11]

Closes #152

What changed

• Detect TECHNICAL PROJECTS sections that are clearly skill labels/values rather than actual project evidence.
• Reclassify only those conservative cases into Skills before normal skill compaction.
• Preserve real project sections when they contain project signals, dates, bullets, or descriptive prose.
• Reuse the existing skill-label vocabulary instead of inventing a second classification model.

Regression coverage

• Skill-only Technical Projects with Languages / Frameworks / Tools becomes Skills.
• Legitimate Incident Tracker + dashboard/API project remains Projects.
• Existing fragmented Technical Projects fixture remains covered.

Merge gate

Do not merge unless all applicable CI checks are green on the current head, there are no unresolved blocker findings, and the branch is based on current main.

[mergemaven11]

Tuesday/Friday engineering sweep triage: keep open for #152, but do not merge from this head. The branch is stale/non-mergeable and predates the CI fix that makes the globally required Frontend check report on non-frontend PRs; its old head only has Backend and Security successes. Refresh onto current main so all required checks, including Frontend CI, run on the exact current head before merge.

[mergemaven11]

Superseded by #204, which reapplies this fix on current protected main while preserving the newer resume-import parser improvements. Closing this stale/non-mergeable PR to keep one active remediation path for #152.