Repository Scanner: languages, frameworks, dependencies, structure, git (v0.1.0)

[s1rry]

What

First milestone (v0.1.0): DevPilot analyzes a repository end to end. No AI.

Repository Scanner — scan a project folder and get a full report:

• New devpilot-scan crate: pure manifest detectors (npm, Cargo, PyPI, Go) split from a filesystem adapter (FsProjectScanner) behind a new ProjectScanner core port. Detectors are pure functions over manifest text.
• Detects: languages (file tree), frameworks + dependencies (manifests), folder structure (top-level + notable dirs), git info (branch, commit count, last commit, top contributors aggregated from history).
• Core: ScanReport/Framework/Dependency/FolderSummary/GitSummary entities, ScanRepository use case.
• Wiring: scan_folder Tauri command via DI; typed lib/ipc/scan.ts.
• UI: Analysis view with overview cards, language bars, framework chips, dependency list, structure and git panels.

Verification

• cargo fmt --check, clippy -D warnings, full cargo test --workspace: clean.
  • Detectors: 7 unit tests over manifest strings. Scanner: 3 integration tests on real temp manifests. Use case: 3 tests over mocks. Plus existing suite.
• pnpm build (tsc strict + vite): clean.
• Rendered live in the Vite preview: seeded a report showing all panels (languages, frameworks, dependencies, structure, git contributors) — no console errors.

Real scanning runs against the backend in pnpm tauri dev.

Architecture holds: devpilot-scan depends only on devpilot-core; the scanner reads the working copy directly, so it does not depend on devpilot-git (use case orchestrates both).

🤖 Generated with Claude Code