Borders: country / voivodeship / powiat (admin 0–2), JSON settings.
Pixel editing, cache, styles, tile proxy.
Poland, voivodeships, “Show heights”, elevation bug fixed.
T3DTerrain component page with screenshot and live HTML demo; chapter 13 updated (MD5 OK, live DEM URL).
Downloaded and MD5-verified; served from https://mapa.imetroll.com/terrain/planet.pmtiles.
Account + API client verified (4000 queries/day), credentials in /etc/tflight/opensky.env.
Data core, 98 tests.
Temperature / humidity / cloud gradients, legends, area lookup via TMapAreas.
planet.pmtiles verified; DEM live at mapa.imetroll.com/terrain/planet.pmtiles.
planet.pmtiles live (CORS/Range); T3DTerrain help page + live HTML demo; default SourceURL = pmtiles://https://mapa.imetroll.com/terrain/planet.pmtiles.
Icons, hourly animation, sun elevation.
Clouds over 3D terrain.
Both VCL/FMX installers with TStatistics + TWeather — ONLY on the owner's explicit order, not before all components are done.
Requirements in TSKY_REQUIREMENTS.md: 5 modes, 4 animations, tile cache. Build after TWeather + TFlight.
Requirements in TFLIGHT_REQUIREMENTS.md: live aircraft via OpenSky, flight tracking, ICAO types, customizable icons. Build after TWeather.
Only on the owner's explicit order.
Which subdomain should TSky use?
Proxy through our server or serve directly?