feat: framework-level route & reference extraction

[yohi]

What changed

All framework resolvers now expose FrameworkResolver.extract() returning route/endpoint nodes + reference edges. The orchestrator passes detected-framework names to each extractFromSource call so framework-specific regex extractors only run on relevant files.

Commits

• 1d6d8c9 feat(resolution): replace extractNodes with extract() returning nodes and references
• dca86f6 feat(resolution): add getApplicableFrameworks helper for per-language dispatch
• 571beab feat(django): emit route nodes and route->view references in extract()
• 1a09053 fix(django): restore include(), ORM dispatch, and DRF router extraction
• 16eb713 feat(flask,fastapi): emit route nodes and route->handler references
• a483c28 feat(express): emit route nodes and route->handler references
• 8ed2c30 fix(express): restore balanced-paren and arrow-handler extraction

Test evidence

• npm run build passes (tsc + copy-assets)
• npm test passes: 2,530 pass / 175 skip (160 test files)
• __tests__/frameworks.test.ts pass (113 tests)
• __tests__/frameworks-integration.test.ts pass (23 tests)
• No dangling extractNodes references remain in src/ or __tests__/

Checklist

• Step 1: FrameworkResolver.extract interface with ProjectNode + GraphReference
• Step 2: detectFrameworks wired into extraction orchestrator
• Step 3: Batch any per-file regex extraction
• Step 4: Remove dead / superseded regex code
• Step 5: Verify against existing integration tests
• README: Framework-aware Routes table updated with new frameworks

[yohi]

miss