Add LVGMC warning map workflow

docs/DEVELOPMENT_AND_STAGING.md

@@ -4,9 +4,9 @@
 
 | Environment | Purpose | Address |
 |---|---|---|
-| Windows | Source editing and Git workflow only | Not applicable |
-| Rocky Linux | Docker development and production-like staging | `http://192.168.1.101:9190` |
-| Temporary VPS | Month-long user-acceptance staging behind Cloudflare, Nginx, and Authelia | Public UAT operational at `https://laikapstak.li` with temporary synthetic data |
+| Windows | Source editing, review, and Git operations only; no compile, build, runtime, dependency installation, or application testing | Not applicable |
+| Rocky Linux | Sole development runtime: compile, build, run, seed, test, and production-like staging | `http://192.168.1.101:9190` |
+| Ubuntu VPS | Deployment target and month-long user-acceptance environment; never a development or build host | Public UAT operational at `https://laikapstak.li` with temporary synthetic data |
 | Workplace production | Out of scope until reviewed and approved | Not documented here |
 
 Rocky checkout:
@@ -36,11 +36,14 @@ codex/staging-baseline
 - Do not change ownership or permissions of the container-managed `postgres/` directory as a deployment workaround.
 - Do not use the current staging procedure as an undocumented workplace-production procedure.
 
-## Windows development
+## Windows source workspace
 
-Use Windows to edit and review source files and to create Git commits. Docker builds,
-the running application, synthetic-data operations, and browser testing belong on
-Rocky. Docker Desktop is not part of the normal project workflow.
+Use Windows only to edit and review source files and perform Git operations. Do not
+run Node/npm dependency installation, TypeScript checks, Vite builds, SBT/Scala
+compilation, Docker/Podman commands, the application, synthetic-data operations,
+or browser application tests on Windows. All compile, build, development-runtime,
+and test work belongs on Rocky. The Ubuntu VPS only receives a release artifact
+that has already been built and verified on Rocky.
 
 ## Commit and transfer workflow
 

docs/PRODUCT_WORKFLOWS.md

@@ -108,6 +108,20 @@ The renderer uses canvas `TextMetrics` visible-glyph bounds (`actualBoundingBoxL
 
 Implementation status: both native exports are implemented and visually validated against the supplied production templates. Later newsroom feedback can still tune the per-template rectangles without changing the manual-entry workflow.
 
+## Brīdinājumi
+
+Purpose: prepare a newsroom map from the current LVĢMC open hydrometeorological-warning dataset without tracing warning areas manually.
+
+Operator flow:
+
+1. Open **Brīdinājumi**; warning metadata and ordered polygon coordinates load through the WeatherTool backend.
+2. Select the independent 1920×1080 or 3840×1440 production canvas.
+3. Optionally filter the current warning period by day and phenomenon.
+4. Enter the editorial title. Warning geometry, severity colors, legend, source data, and validity information remain data-driven.
+5. Preview and download the native-resolution PNG.
+
+The two exports use separate geographic-to-pixel calibration and layout values. Neither output is produced by resizing the other. Upstream times are interpreted in the `Europe/Riga` timezone. Empty warning data is a valid state and produces an uncolored base map.
+
 ## Apskats
 
 Purpose: aggregate selected fields across Latvia for a selected time range.

docs/README.md

@@ -4,7 +4,7 @@ This directory contains the working documentation for the WeatherTool modernizat
 
 ## Current status
 
-- Development source is edited and committed on Windows; Docker builds and runtime testing are performed on Rocky.
+- Windows is restricted to source editing, review, and Git operations. Rocky is the sole compile, build, development-runtime, and test environment. The Ubuntu VPS is a deployment target only.
 - A production-like staging copy runs through Docker Compose on Rocky Linux at `http://192.168.1.101:9190`.
 - Staging uses deterministic synthetic observations for the repository station set plus Valmiera, required by Faktiskā.
 - Scheduled external-provider jobs are disabled in development and staging.
@@ -26,7 +26,7 @@ This directory contains the working documentation for the WeatherTool modernizat
 ## Documents
 
 - [Architecture and data flow](ARCHITECTURE.md) — components, data sources, data flow, and repository layout.
-- [Development and staging](DEVELOPMENT_AND_STAGING.md) — Git workflow, local build, Rocky deployment, synthetic data, verification, and rollback.
+- [Development and staging](DEVELOPMENT_AND_STAGING.md) — Windows source/Git workflow, Rocky development and verification, VPS deployment, synthetic data, and rollback.
 - [Product workflows](PRODUCT_WORKFLOWS.md) — the intended purpose and current status of each visible workspace.
 - [Update roadmap](UPDATE_ROADMAP.md) — phased technical, security, dependency, testing, and UI work.
 - [Third-party notices](THIRD_PARTY_NOTICES.md) — licenses and attribution for adapted interface components.

docs/UPDATE_ROADMAP.md

@@ -4,10 +4,10 @@ This document tracks proposed WeatherTool improvements. Work should be delivered
 
 ## Environments and workflow
 
-- **Windows development:** source editing and Git workflow only; Docker runtime testing is performed on Rocky.
-- **Rocky staging:** production-like Docker deployment at `http://192.168.1.101:9190`.
+- **Windows source workspace:** source editing, review, and Git operations only; do not install dependencies, compile, build, run, or test here.
+- **Rocky development and staging:** the sole compile, build, development-runtime, and test environment, with production-like Docker staging at `http://192.168.1.101:9190`.
 - **Git over SSH:** Windows pushes reviewed commits to a private bare repository on Rocky; the Rocky staging checkout pulls those commits and rebuilds.
-- **Temporary VPS staging:** release `ef64895` is publicly operational behind Cloudflare strict TLS, Nginx, and Authelia with a limited 14-day synthetic dataset.
+- **Ubuntu VPS deployment:** release `ef64895` is publicly operational behind Cloudflare strict TLS, Nginx, and Authelia with a limited 14-day synthetic dataset; the VPS does not compile or build the project.
 - **Workplace production:** remains separate until changes are reviewed, tested, and explicitly approved for workplace use.
 
 Do not synchronize `.env`, database directories, generated dependencies, build output, or provider credentials between machines.