Rocketship — more detail: panel seams, cockpit windows, delta wing structure, dorsal/tail fins, dual engine bells, nozzle glow, nav lights.
Earth grid — strict 3×3 only: 2 latitude parallels (60°N / 60°S) + equator, 3 meridians (45°W / prime / 45°E). No extra lines.
Poles — verified: North at top (720, 230), South at bottom (720, 890) on the sphere; small pole markers added.
Continents — replaced ovals with angular coastline-style paths (Americas partial, Greenland, Eurasia, Europe, Africa, Arabia, India, SE Asia).
Exhaust — volumetric tapered ribbon (filled paths + inner/outer gradients + nozzle bloom), aligned to rocket nozzle at ~(868, 582).
Sky / cosmic area — static SVG, not generated at runtime. Stars/nebulae are hand-placed vector elements (gradients + circles + blink paths). Nothing is computed in JS or canvas. If you want variation, we can add a separate review pass (denser star field, different nebula shapes) by editing hub-logo-fragment-space.svg only.


i need orchestration for the whole project and project parts. if you need to write some configs or scripts - do it in ./orchestration folder. the tasks there are:
- global - to make able to run the whole backend (and connected frontend parts) locally on my laptop without having external server and DNS. you may use light DNS stubs via /etc/hosts* if needed but generally the minor intervention on the host is the goal
- sub-global: run all infra inside docker containers, separatedly and specifically: landing (hub, 1 docker frontend (FE for the future)) ->>> gitea (1 separated docker FE) ->>> the rest (1 separated docker FE for crashes/tasks web interface)
- sub-global: use shared code base whenever possible, reachable using decentralized version control system like git or DVFS (distributed virtual file system). changes on one end should reflect changes on another in easy way.
- sub-global: minimalistic infra, but the docker base images should commonly follow already proven solutions like nginx as a FE, php as the primary BE language, mariadb as DB
- "1 click deploy" - if docker is installed, would like to see the only one script than is:
1) either create docker infra on the laptop
2) update the existing infra from previous run
anyway, finally it should run, ideally on any devices

orchestration lives on next in ./orchestration/ (feature/20260527_orchestration merged and removed 2026-06-04). SVG landing changes continue on next / feature branches.
