Refactor code structure for improved readability and maintainability

.env.example

@@ -12,10 +12,8 @@
 # frontend never speaks to Fayda directly.
 
 # Base URL of the emaapi backend, including the /api prefix.
-# 3001, not 3000: the portal itself takes 3000 in development, because that is
-# the port in the Fayda redirect URI registered for local testing. Set PORT=3001
-# in emaapi's .env to match.
-VITE_BASE_API_URL=http://localhost:3001/api
+# The portal runs on 4200 and the local API runs on 3000.
+VITE_BASE_API_URL=http://localhost:3000/api
 
 # Serve fixture data instead of calling the API. Any value other than "true"
 # uses the real backend.
@@ -25,7 +23,7 @@ VITE_USE_MOCKS=false
 # Host ports published by docker-compose.yml. It also expects per-app env files
 # at apps/portal/.env and apps/backoffice/.env, which can each be a copy of this
 # file. Ignored when running the Vite dev servers, which serve the portal on
-# 3000 and the backoffice on 4201.
+# 4200 and the backoffice on 4201.
 # EMA_PORTAL_PORT=8021
 # EMA_BACKOFFICE_PORT=8022
 
@@ -34,6 +32,5 @@ VITE_USE_MOCKS=false
 # page at /callback and /signup/fayda/callback, and whichever path is registered
 # with Fayda must match the API's FAYDA_REDIRECT_URI exactly.
 #
-# The value being registered first is http://localhost:3001/callback, so the
-# portal's dev server now listens on 3000 and emaapi moves to 3001. Nothing
+# Register http://localhost:4200/callback with Fayda. Nothing
 # extra to run — `nx serve portal` already binds the right port.