[coinmandeer]

Change

Follows the merged UI redesign (coinmandeer/map0S-codex#1): the AI puts every place it names on the map, the chrome is quieter, the renderer and iOS glitches found in the audit are fixed, and the e2e suite is back to describing the product that ships.

AI → map, whichever model answers

• Places an answer names (places field, a JSON block, GPS pairs, list items) are geocoded on the server and drawn automatically, with one camera fit for route + stops + places. No "Show on map" click (apps/api/src/services/ai/mentionedPlaces.ts, chatService.ts).
• A plain-text answer is no longer dropped; a tool call written into the text is recognised; submit_plan accepts stops by name/address; two or more places + a "route" question yields a computed route.
• Rejected mapData goes back to the model once instead of ending the turn; tool arguments wrapped in Markdown or with a trailing comma are repaired syntactically instead of silently discarded.
• Offline/memory profile gets a gazetteer and a straight-line router, so the assistant works in dev without keys.
• Answers render paragraphs, lists and bold (AnswerText.tsx); compact header with the last conversation's title and one ⋯ menu.

Search, layers, place detail

• Suggester: places first with a kind icon, name + hierarchy, at most 3 layers, one source credit in the footer, arrow keys with aria-activedescendant. The "Ask AI: …" row is replaced by a quiet "Enter asks the assistant" hint; anything not suggested goes to the AI. Orphaned GooglePlaceSearch.tsx removed.
• Layer and basemap panels: group icons, hairline list instead of boxes, no jumping "N on · M selected" summary.
• Place detail: section icons + chevron instead of the native triangle, bilingual field labels (district, updatedAt, dataScope…), locale-formatted dates, stat grid that no longer breaks words.

Renderer and map

• Emergency basemap no longer crashes on getStyle().name when the first style fails; one bad tile no longer swaps the whole basemap (8 errors / 15 s budget); glyphs for raster styles; the selected pin survives a basemap switch; the pulse stops after three cycles.
• Game: entering the game after a load often showed an empty board — a late detach of the replaced handle removed the new scene (shared layer id), and a handle detached inside a style.load dispatch re-attached itself. Fixed in worldLayer.ts; ?mode=game now starts the scene. With the scene running, the game panel opened from the HUD could stay a spinner for tens of seconds on a slow machine (a lazy component's Suspense retry never expires, and the board's redraws kept interrupting it); it now loads through ordinary state, commits as soon as its module is ready and is preloaded when game mode starts.
• Discover: area outlines waited for an unrelated state change because sync() bailed while any tile was loading — now retried on idle; the boundary manifest is fetched as soon as a local world is shown. The "What is here?" chip (component and styles existed) is mounted; on a phone it floats above the sheet and steps aside while the sheet is half or full height or a place detail covers the panel. The header shows the selected area's name even when the guide is unavailable.
• Map status: a failed layer's alert stays up while the layer retries instead of blinking out and back.

Plans and presets

• A shared plan link (/s?mode=planning#plan=…) kept losing mode on the first camera rewrite, so a reload or a copied address opened Discover without the plan.
• A preset with events (City) fell back to "Custom" immediately because the timeline's from/to window counted as drift; the time window is no longer part of preset identity.
• The empty planning panel opens half-height on a phone like the other panels.

iOS (PWA now, Capacitor in the roadmap)

• Inputs ≥ 16 px on touch (no focus zoom), no tap flash or rubber-band overscroll, PNG apple-touch-icon and manifest icons, apple-mobile-web-app-title; GPS is requested only after "My location" or when already granted; map controls no longer collide with the Layers/Settings column.

Data

• Golemio: v2 address objects, district slugs ("praha-1" → "Praha 1") and opening hours are kept; the memory server serves stateless live sources (was 404). GOLEMIO_API_KEY / EUROPEANA_API_KEY documented — keys only via env, none in the repo.

Audit

• docs/audits/2026-09-25-mapos-audit.md: findings by severity (renderer/perf, UI/UX, mobile/iOS, AI, tests), answers on GBFS, SpaceAPI, Ookla, Eurostat, BTC Map, Europeana, and a phased roadmap (F1 performance, F2 native-feeling mobile, F3 "wow", F4 Capacitor, F5 data).

E2E suite

• Specs rewritten for the redesigned chrome through one helper (e2e/fixtures/mapPanel.ts) instead of the removed basemap-btn/overflow ids; URL assertions replaced by application state (the URL deliberately keeps only the camera since v0.1); boundary tiles have a shared fixture (e2e/fixtures/boundaryTiles.ts).
• Three Discover tests exercised the legacy GeoJSON overlay that the default VITE_DISCOVER_BOUNDARIES flag hides; they now test the same user-visible behaviour on the vector-tile overlay.
• The area-hover performance check measured how fast the runner's software GL paints (a plain repaint of the unchanged map takes ~80 ms there). It now requires the handler to fit in one frame and the hover frame to cost no more than an ordinary repaint, keeping the absolute 50 ms on machines that paint that fast.
• The map memory benchmark (performanceMap.spec.ts) runs in its existing production profile (playwright.performance.config.ts, one worker) as a new CI step test:e2e:performance instead of beside the WebGL workers of the default profile, where it timed out on main too; the profile now points its base URL at its own preview port.
• The weather hover/tap test waits until the grid stops refetching before comparing the two readings (a late camera move replaced the grid between them on the CI runner).
• Security profile: the production bundle exposes no map handle, so the untrusted name is opened through Discover's accessible place list (the test had read window.__maposMap since it was written).
• No test was skipped, disabled or quarantined.

Evidence

• Relevant unit and contract tests pass — npm test (web 583 pass, API 848 pass, packages 111/84/4 pass; skips are the existing environment-gated ones: live model, PostgreSQL, rights inventories), test:contracts, test:privacy (218 pass), test:migrations (37), test:load, test:secrets, test:css-tokens. New unit tests: preset drift vs the event window, shared-plan link keeps its mode, ?mode=game starts the scene.
• Type, lint and formatting checks pass — npm run typecheck, npm run lint, npm run format:check.
• Integration/E2E, visual, accessibility or load evidence — local runs with the preinstalled Chromium: default suite 217/220 before the benchmark moved to its own profile (1 skipped MAPOS_LONG_PERF gate, unchanged; the 2 failures were that benchmark timing out beside other WebGL workers, 1.3/1.6 min alone with and without this branch's source changes). Profiles: offline 5/5, security 1/1, accessibility 8/8, visual 18/18, runtime-starter 2/2, performance 2/2 (production build, 1.1/1.3 min). After the first CI run: game panel under 4x CPU throttling opens in ~3–5 s (was never / >30 s), weather + game + Discover specs 23/23 on three loaded workers. Live check at 1440 px and iPhone 14 Pro size (Discover, layers, basemaps, "Brno" suggestions, a question sent with Enter, AI panel, place detail): no page errors.
• No test was presented as run when it was skipped — known sensitivity: game.spec.ts:68 fails only when several copies of itself run at once (--repeat-each), because they fight the same shared-world enemy.

Layer or provider integration (if applicable)

• Versioned manifest, query/100-feature budget and cancellation — no new layer; Golemio normalisation stays inside the existing source and its 500-row cap.
• Loading, empty, partial, error and provider-outage states — Golemio keeps its "not configured" / zoom notices; map status alert now stable during retries.
• Filters, legend, provider-neutral detail/actions and accessible non-map alternative — detail labels are provider-neutral and bilingual.
• Permissions, private-data boundary, AI exposure and entitlement policy — geocoding of places an answer names uses the existing resolve_location registry; no new data leaves the server.
• Fixture/contract tests, health/SLO owner and disable/rollback path — fixture test for Golemio normalisation; no new provider.
• No provider secret or untrusted extension JavaScript reaches the client — keys only via server env.

Release safety

• Migration: none.
• Feature flags: none added. Discover's existing VITE_DISCOVER_BOUNDARIES rollback path is unchanged.
• Security/privacy/dependency/bundle: no new dependency (the icon render script uses sharp, already installed with the API's glTF tooling). GPS permission is requested later than before.
• Traceability/docs: audit document, docs/data-sources.md, docs/environment.md, docs/plans/blockers.md updated.

🤖 Generated with Claude Code

https://claude.ai/code/session_01J3QFugXbaTxPuuP3q3rR16