Branch analysis and consolidation recommendations

[Copilot]

Analysis of 5 active branches (main, docs, poc, poc-2, poc-and) to identify unique features, redundancies, and provide merge/delete recommendations.

Analysis Deliverables

Four documents totaling 823 lines:

• BRANCH_ANALYSIS_README.md - Navigation and quick summary
• BRANCH_VISUAL_SUMMARY.md - Charts, comparison tables, decision matrix
• BRANCH_RECOMMENDATIONS.md - Action items with timeline and risk assessment
• BRANCH_COMPARISON_ANALYSIS.md - Detailed technical analysis of each branch

Key Findings

poc-2 (merge to main - high priority)

• Complete vanilla JS implementation: map, POIs, admin, multi-layer support
• 6 Vitest test files with coverage
• 7 documentation files (architecture, tooling, JSDoc guide)
• Production-ready: ESLint, Prettier, modular structure
• ~1,000 LOC, no framework dependencies

poc-and (keep for evaluation)

• SvelteKit + TypeScript alternative
• Similar features, component-based architecture
• E2E tests with Playwright
• ~2,000 LOC with full framework stack

docs & poc (delete)

• docs: no unique content (already in main/devDocs)
• poc: basic implementation fully superseded by poc-2

Comparison Matrix

Branch	Tests	Docs	Framework	Status
poc-2	✅ 6 files	✅ Extensive	None	Production-ready
poc-and	⚠️ Basic E2E	⚠️ Basic	SvelteKit	Alternative approach
poc	❌	❌	None	Obsolete
docs	❌	✅	N/A	Redundant

Recommendations

1. Merge poc-2 → main (establishes tested, documented vanilla JS baseline)
2. Delete docs and poc branches (no unique value)
3. Keep poc-and for framework evaluation (strategic decision in 1-2 months)

Estimated implementation: 5-7 hours

Original prompt

Compare all open branches of the mapping-project to one another, note which unique features each has, which can be safely deleted, and what functionality should be merged into main from each

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.