feat: Add .tool-versions file, remove unused Docker documentation, and create repository summary and story files; enhance analysis.py and add fetch_trikk_coords.py script

2026-06-10 13:03:08 +02:00
parent eb95b98111
commit 793dd2c3a9
9 changed files with 82 additions and 575 deletions
@@ -0,0 +1,26 @@
+# The Story of finn-eiendom-mcp
+
+## The Chronicles: A Year in Numbers
+The repository's history shows a highly focused and rapid development cycle.
+- **Total Commits**: 11
+- **Recent Activity**: Intense development burst observed in late May 2026.
+- **Core Focus**: Transitioning from a simple scraper to a robust, architecture-tested service layer.
+
+## Cast of Characters
+While the repository is primarily a solo endeavor, the commit history reveals a singular vision: building a high-integrity, decision-support tool. The development pattern suggests a "single-driver" model where architectural integrity (enforced by `tests/test_architecture.py`) is prioritized alongside feature delivery.
+
+## Seasonal Patterns
+Development is characterized by concentrated "sprints." Rather than steady, low-level activity, the project shows evidence of intense functional implementation blocks, likely corresponding to specific feature realizations (e.g., the move to Pydantic v2 and the establishment of the Service Layer).
+
+## The Great Themes
+Three major themes dominate the project's evolution:
+1. **Architectural Rigor**: The move toward a "Single-Home Rule" where all business logic is pushed down into a dedicated service layer, accessible by multiple interfaces (CLI, MCP, and Library).
+2. **Data Enrichment**: A shift from simple web scraping to sophisticated data orchestration, combining FINN real estate listings with deep market context from Eiendom.no.
+3. **Reliability and Observability**: The implementation of hash-aware caching, extensive testing (unit, integration, and architecture tests), and structured logging/formatting.
+
+## Plot Twists and Turning Points
+- **The Great Refactor (Phase 2)**: A pivotal moment in the project's history was the decision to move away from a simple script toward a professional-grade Python package. This involved implementing a clear separation between the transport layers (CLI/MCP) and the core logic (Service/Domain).
+- **The Introduction of MCP**: The pivot to include a Model Context Protocol (MCP) server marked a change in the project's purpose, moving from a purely manual CLI tool to an AI-agent-ready intelligence engine.
+
+## The Current Chapter
+The repository currently stands at the conclusion of its "Phase 2" implementation. The architecture is solidified, the service layer is the single source of truth, and the system is ready to be used by LLM agents to provide high-value, real-time real estate insights. The next chapter focuses on scaling the analysis complexity and further refining the scoring models.