Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Dockerfile`:
- Around line 6-11: The Dockerfile omits server.mjs from the build context so
the later production stage copy of /app/server.mjs into appbase/staticbuilder
fails; update the initial COPY steps to include server.mjs (the file named
server.mjs) into the image root (alongside the existing COPY of ./server and
./src) so that the downstream stage can successfully COPY /app/server.mjs —
ensure the same ownership flag (--chown=default:root) is used and that any
build-stage directory referenced by the production stage (appbase/staticbuilder)
will contain server.mjs.

In `@docs/ViteSSRMigrationPlan.md`:
- Around line 15-51: The fenced code blocks in docs/ViteSSRMigrationPlan.md are
missing language identifiers (e.g., the ASCII-art blocks and other snippets),
which triggers markdown lint MD040; update each triple-backtick fence used for
non-syntax blocks to include a language tag such as text (or bash where
appropriate). Locate the fenced blocks that contain the ASCII diagrams and
phase/service lists (the blocks shown in the diff) and change ``` to ```text (or
```bash for shell examples) so the renderer/linter recognizes them; ensure all
similar fenced blocks in the file (the ones showing diagrams and lists) are
updated consistently.

In `@scripts/update-runtime-env.js`:
- Line 23: The script always writes runtime overrides to the hardcoded outputDir
('public') so production (which serves dist/client) never gets the updated
env-config.js; change the outputDir assignment in scripts/update-runtime-env.js
(the outputDir constant) to resolve to 'dist/client' when running in production
(e.g. process.env.NODE_ENV === 'production') or, more robustly, detect and
prefer an existing 'dist/client' directory over 'public' before writing; ensure
the rest of the script still writes the env-config.js into the chosen outputDir.

In `@server.mjs`:
- Around line 203-210: The async route handlers that call await getEntry()
(e.g., the sitemap handler registered via app.use('/sitemap.xml', ...), the
robots handler app.get('/robots.txt', ...), and the other async app.get/app.use
handlers that also call getEntry()) must be wrapped so promise rejections are
forwarded to Express error middleware; wrap each async handler with the existing
asyncHandler helper (or implement a small wrapper that catches errors and calls
next(err)) so any rejection from getEntry() is passed to next rather than
causing an unhandled promise rejection.

In `@src/entry-client.jsx`:
- Around line 60-63: The current code replaces server-provided settings by
assigning preloadedState.settings = settings; instead of merging; change it so
localStorage settings overlay the server-preloaded settings by merging objects
(preserve existing preloadedState.settings keys and only overwrite with values
from SettingsUtility.getSettingsFromLocalStorage()), updating the assignment
that references SettingsUtility.getSettingsFromLocalStorage() and
preloadedState.settings accordingly.
- Around line 38-40: The tracePropagationTargets fallback produces [''] when
unset, causing Sentry to match all URLs; fix by normalizing and filtering the
value before passing it to Sentry: read config.sentryTracePropagationTargets,
split on ',', trim each entry, remove empty strings, and pass that filtered
array to the tracePropagationTargets option (the code around
tracePropagationTargets in src/entry-client.jsx). Ensure the transformation is
applied where tracePropagationTargets is constructed so untrimmed or empty
values are excluded.

In `@src/views/MapView/utils/mapActions.js`:
- Around line 9-11: panViewToBounds currently uses globalThis.L (and thus
depends on Leaflet being global) even though mapActions.js already loads Leaflet
into the module-scoped L; update panViewToBounds to use the module-scoped L
(e.g., replace globalThis.L.latLng / globalThis.L.latLngBounds uses with
L.latLng / L.latLngBounds) and add a guard to ensure L is non-null before
calling its methods so it works consistently without relying on globalThis.L or
side effects from MapView.js (which only sets globalThis.rL).

In `@vite.config.js`:
- Around line 9-42: The Vite config is using the wrong parameter name: change
the defineConfig callback parameter from ssrBuild to isSsrBuild and update the
conditional spread that currently uses !ssrBuild to use !isSsrBuild so
sentryVitePlugin is only added for non-SSR builds; update references inside the
defineConfig callback (e.g., the ternary that adds sentryVitePlugin) and ensure
the symbol names defineConfig and sentryVitePlugin remain unchanged.

---

Outside diff comments:
In `@src/views/MapView/MapView.js`:
- Around line 9-10: MapView currently statically imports react-leaflet
(useMapEvents and the ReactLeaflet namespace) and related components like
UserMarker, causing SSR to evaluate Leaflet code and crash; change this by
removing those top-level imports and instead load the entire map subtree on the
client only — either dynamically import the MapView map subtree (and components
such as UserMarker) with SSR disabled (e.g., next/dynamic({ ssr: false })) or
render the map subtree only after a client mount check (useEffect/setState) so
useMapEvents and ReactLeaflet are only imported/executed in the browser; ensure
all references to useMapEvents, ReactLeaflet, and UserMarker are moved into the
client-only module or the dynamically imported component.

---

Nitpick comments:
In `@package.json`:
- Line 72: The lint:fix npm script is missing the .mjs extension so autofixes
can miss files; update the "lint:fix" script in package.json (the lint:fix
entry) to include --ext .js,.jsx,.mjs for eslint and ensure prettier invocation
also targets .mjs (make the extensions consistent with the "lint" script) so
.mjs files are linted and auto-fixed.