feat: add community picker with address search and welcome dialog to map view

Redesign the map sidebar into a dual-mode panel: a simplified community
picker (normal mode) with address search via LocationSelector, and the
full layer controls (editing mode) for admins. Citizens can search their
address to find nearby collection points within 500m, shown as colored
pins on the map. A welcome dialog presents the regulation summary on
first load with navigation options.

Also: extract shared types (CurrentUser, GeoSetData, SEARCH_COLORS) to
types.ts, deduplicate geometry list item rendering in DetailPanel, add
GeometryCollection support to bounds calculation, improve map labels
(point addresses at zoom, polygon names that fade), and update docs.

Author: kouloumos

CLAUDE.md

@@ -2,6 +2,18 @@
 
 This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
 
+## Development Environment
+
+This project uses [Nix](https://nixos.org/) to manage development dependencies. All shell commands (`npm`, `npx`, `node`, etc.) must be run inside the Nix development shell.
+
+**Prefix all commands with `nix develop --command`**, for example:
+```bash
+nix develop --command npm run build
+nix develop --command npx tsc --noEmit
+```
+
+If you open an interactive shell session first (`nix develop`), subsequent commands in that session don't need the prefix.
+
 ## Build Commands
 
 ### Development

docs/guides/consultations.md

@@ -10,7 +10,7 @@ The consultation feature operates as a JSON-driven, dual-view interface:
 
 1. **Regulation JSON**: Each consultation points to a remote JSON file (`jsonUrl`) that defines the entire regulation structure — chapters, articles, geographic areas, cross-references, and definitions. The schema is defined in [`json-schemas/regulation.schema.json`](../../json-schemas/regulation.schema.json).
 2. **Database Layer**: Prisma stores consultation metadata (name, end date, active status), comments, and upvotes. Comments are entity-scoped — tied to a specific chapter, article, geoset, or geometry by `entityType` + `entityId`.
-3. **Frontend Layer**: A `ConsultationViewer` client component orchestrates two views — a Document View (chapters/articles with markdown content) and a Map View (Mapbox-powered geographic visualization). A floating action button toggles between them.
+3. **Frontend Layer**: A `ConsultationViewer` client component orchestrates two views — a Document View (chapters/articles with markdown content) and a Map View (Mapbox-powered geographic visualization). A floating action button toggles between them. The map view features a community picker with address search, allowing citizens to find nearby collection points by searching their address. A welcome dialog shows the regulation summary on first load.
 4. **Comment System**: Authenticated users can leave HTML-rich comments on any entity. Comments support upvoting and trigger email notifications to the municipality's contact address.
 5. **Admin Geo-Editor**: Administrators can draw missing geometries directly on the map when regulation text defines areas textually but lacks GeoJSON coordinates. Edits are stored in localStorage and exported as a complete updated regulation JSON.
 
@@ -121,15 +121,15 @@ sequenceDiagram
     * Layout: [`src/app/[locale]/(city)/[cityId]/consultation/[id]/layout.tsx`](../../src/app/%5Blocale%5D/(city)/%5BcityId%5D/consultation/%5Bid%5D/layout.tsx) (header, footer, feature-flag check)
 
 * **Frontend Components** (all under `src/components/consultations/`):
-    * `ConsultationViewer`: Master orchestrator — manages view state (document/map), URL hash navigation, chapter expansion, reference click handling
+    * `ConsultationViewer`: Master orchestrator — manages view state (document/map), URL hash navigation, chapter expansion, reference click handling, welcome dialog with regulation summary, and `defaultView` support
     * `ConsultationHeader`: Title, status badge (Active/Inactive), end date, comment count
     * `ConsultationDocument`: Renders chapters/articles with expand/collapse, AI summary cards, sources list
     * `ChapterView` / `ArticleView`: Individual chapter and article renderers with comment counts, permalinks, collapsible content
     * `MarkdownContent`: Renders markdown with `{REF:id}` and `{DEF:id}` pattern handling as interactive links
-    * `ConsultationMap`: Mapbox map with geoset rendering, layer controls, detail panel, derived geometry computation (buffer/difference)
-    * `LayerControlsPanel` / `LayerControlsButton`: Sidebar for toggling geoset/geometry visibility with checkbox tree UI
-    * `DetailPanel`: Side sheet showing selected geoset/geometry info with description, textual definition, and comments
-    * `GeoSetItem` / `GeometryItem`: Tree items in layer controls with checkboxes, color swatches, and comment counts
+    * `ConsultationMap`: Mapbox map with geoset rendering, layer controls, detail panel, derived geometry computation (buffer/difference), address search with search location pins, initial fit-to-bounds, and `GeometryCollection` zoom support
+    * `LayerControlsPanel` / `LayerControlsButton`: Dual-mode sidebar — in normal mode shows a simplified community picker with address search (via `LocationSelector`); in editing mode shows the full layer controls with checkbox tree UI for toggling geoset/geometry visibility
+    * `DetailPanel`: Side sheet showing selected geoset/geometry/search-location info. For search locations, shows nearby points within 500m sorted by distance (Haversine). For geosets, lists point geometries with comment counts. For geometries, shows description, textual definition, and comments
+    * `GeoSetItem` / `GeometryItem`: Tree items in layer controls (editing mode) with checkboxes, color swatches, clickable names, and inline comment counts
     * `CommentSection`: Rich text editor (ReactQuill), authentication check, comment display with upvotes and delete
     * `CommentsOverviewSheet`: Modal listing all comments with sort options (recent/likes), entity type badges, navigation
     * `AISummaryCard`: Collapsible card for AI-generated summaries on chapters/articles
@@ -144,7 +144,7 @@ sequenceDiagram
     * `CityConsultations`: [`src/components/cities/CityConsultations.tsx`](../../src/components/cities/CityConsultations.tsx) (card grid listing for city consultations tab)
 
 * **Types**:
-    * `RegulationData`, `Chapter`, `Article`, `GeoSet`, `Geometry`, etc.: [`src/components/consultations/types.ts`](../../src/components/consultations/types.ts)
+    * `RegulationData`, `Geometry`, `CurrentUser`, `GeoSetData`, `SEARCH_COLORS`, etc.: [`src/components/consultations/types.ts`](../../src/components/consultations/types.ts) (shared types used across all consultation components)
 
 * **Email**:
     * Template: [`src/lib/email/templates/consultation-comment.tsx`](../../src/lib/email/templates/consultation-comment.tsx) (React Email HTML template with entity permalink)
@@ -261,12 +261,16 @@ For local development, you can place regulation JSON files in the `public/` dire
 4. Geometries may have a `textualDefinition` but null `geojson` — the admin geo-editor addresses this gap
 
 ### Map & Geo-Editor
-1. The map uses Mapbox GL with custom styling for different geosets (each has a `color`)
+1. The map uses Mapbox GL with custom styling for different geosets (each has a `color`) and always-on street labels
 2. `defaultVisibleGeosets` in the regulation JSON controls initial map layer visibility
-3. Derived geometries are computed client-side using Turf.js operations
-4. The admin geo-editor stores drawn geometries in browser `localStorage` until exported
-5. Export produces a complete updated `regulation.json` merging local edits with original data
-6. Only super-administrators can access editing mode
+3. The map auto-fits to all visible features on initial load (unless a hash navigation targets a specific entity)
+4. Citizens can search addresses via the community picker; searched locations appear as colored pins and open a detail panel showing nearby points within 500m
+5. Clicking a community boundary polygon opens the parent geoset detail; clicking a point opens the geometry detail
+6. Point labels (addresses) appear at higher zoom levels; polygon labels (community names) fade out at street level to avoid noise
+7. Derived geometries are computed client-side using buffer/difference operations
+8. The admin geo-editor stores drawn geometries in browser `localStorage` until exported
+9. Export produces a complete updated `regulation.json` merging local edits with original data
+10. Only super-administrators can access editing mode (via a small edit icon in the community picker header)
 
 ### Navigation
 1. URL hash anchors (`#chapter-1`, `#article-3`, `#geoset-prohibited_areas`) enable deep linking to specific entities

jest.config.js

@@ -1,6 +1,8 @@
 module.exports = {
   preset: 'ts-jest',
   testEnvironment: 'jsdom',
+  maxWorkers: '50%',
+  workerIdleMemoryLimit: '512MB',
   moduleNameMapper: {
     '^@/(.*)$': '<rootDir>/src/$1',
   },

public/regulation-cooking-oil.json

@@ -14,6 +14,7 @@
       "description": "Η σελίδα της δημόσιας διαβούλευσης στον ιστότοπο του Δήμου Αθηναίων"
     }
   ],
+  "defaultView": "map",
   "defaultVisibleGeosets": [
     "dk_1",
     "dk_2",
@@ -4402,11 +4403,11 @@
           "id": "dk2_23_point",
           "textualDefinition": "ΠΛ. ΠΡΟΦ. ΗΛΙΑ, 2η Δημοτική Κοινότητα, Αθήνα",
           "geojson": {
-            "type": "Point",
             "coordinates": [
-              23.7535381,
-              38.0123173
-            ]
+              23.7465002258959,
+              37.965898200067805
+            ],
+            "type": "Point"
           }
         },
         {
@@ -11978,8 +11979,8 @@
           "geojson": {
             "type": "Point",
             "coordinates": [
-              23.751698,
-              37.9442429
+              23.7734905,
+              38.0003983
             ]
           }
         },

src/app/[locale]/(city)/[cityId]/consultation/[id]/page.tsx

@@ -1,34 +1,15 @@
 import { Metadata } from "next";
 import { getCityCached } from "@/lib/cache";
-import { getConsultationById, getConsultationComments } from "@/lib/db/consultations";
+import { getConsultationById, getConsultationComments, fetchRegulationData } from "@/lib/db/consultations";
 import { notFound } from "next/navigation";
 import { ConsultationViewer } from "@/components/consultations";
-import { RegulationData } from "@/components/consultations/types";
 import { auth } from "@/auth";
 import { env } from "@/env.mjs";
 
 interface PageProps {
     params: { cityId: string; id: string };
 }
 
-async function fetchRegulationData(jsonUrl: string): Promise<RegulationData | null> {
-    try {
-        // Resolve relative URLs (e.g. /regulation.json) against the app's base URL
-        const url = jsonUrl.startsWith('http') ? jsonUrl : `${env.NEXTAUTH_URL}${jsonUrl}`;
-        const response = await fetch(url, { cache: 'no-store' });
-
-        if (!response.ok) {
-            console.error(`Failed to fetch regulation data: ${response.status}`);
-            return null;
-        }
-
-        return await response.json();
-    } catch (error) {
-        console.error('Error fetching regulation data:', error);
-        return null;
-    }
-}
-
 export async function generateMetadata({ params }: PageProps): Promise<Metadata> {
     const [consultation, city] = await Promise.all([
         getConsultationById(params.cityId, params.id),
@@ -120,7 +101,7 @@ export default async function ConsultationPage({ params }: PageProps) {
     }
 
     // Check if consultations are enabled for this city
-    if (!(city as any).consultationsEnabled) {
+    if (!city.consultationsEnabled) {
         notFound();
     }
 
@@ -182,6 +163,8 @@ export default async function ConsultationPage({ params }: PageProps) {
                 currentUser={session?.user}
                 consultationId={params.id}
                 cityId={params.cityId}
+                cityName={city.name}
+                cityLogoUrl={city.logoImage || null}
             />
         </>
     );

src/components/consultations/ArticleView.tsx

@@ -4,15 +4,9 @@ import PermalinkButton from "./PermalinkButton";
 import AISummaryCard from "./AISummaryCard";
 import MarkdownContent from "./MarkdownContent";
 import CommentSection from "./CommentSection";
-import { Article, ReferenceFormat, RegulationData } from "./types";
+import { Article, ReferenceFormat, RegulationData, CurrentUser } from "./types";
 import { ConsultationCommentWithUpvotes } from "@/lib/db/consultations";
 
-interface CurrentUser {
-    id?: string;
-    name?: string | null;
-    email?: string | null;
-}
-
 interface ArticleViewProps {
     article: Article;
     baseUrl: string;

src/components/consultations/ChapterView.tsx

@@ -4,15 +4,9 @@ import PermalinkButton from "./PermalinkButton";
 import AISummaryCard from "./AISummaryCard";
 import MarkdownContent from "./MarkdownContent";
 import CommentSection from "./CommentSection";
-import { RegulationItem, ReferenceFormat, RegulationData } from "./types";
+import { RegulationItem, ReferenceFormat, RegulationData, CurrentUser } from "./types";
 import { ConsultationCommentWithUpvotes } from "@/lib/db/consultations";
 
-interface CurrentUser {
-    id?: string;
-    name?: string | null;
-    email?: string | null;
-}
-
 interface ChapterViewProps {
     chapter: RegulationItem;
     baseUrl: string;

src/components/consultations/ConsultationDocument.tsx

@@ -11,15 +11,9 @@ import ArticleView from "./ArticleView";
 import DocumentNavigation from "./DocumentNavigation";
 import SourcesList from "./SourcesList";
 import MarkdownContent from "./MarkdownContent";
-import { RegulationData, ReferenceFormat } from "./types";
+import { RegulationData, ReferenceFormat, CurrentUser } from "./types";
 import { ConsultationCommentWithUpvotes } from "@/lib/db/consultations";
 
-interface CurrentUser {
-    id?: string;
-    name?: string | null;
-    email?: string | null;
-}
-
 interface ConsultationDocumentProps {
     regulationData: RegulationData | null;
     baseUrl: string; // Base URL for permalinks