Atlas 0.4: deployment, runtime, and environment architecture views

[Shahinyanm]

What changed

• splits the former Operations area into Deployment, Runtime, Environments, and Configuration
• adds deterministic CI/CD and runtime architecture scenes with environment switching
• restores directional module dependencies and clearer aggregate links on the system map
• introduces a consistent visual grammar for sync, async, data, structure, deploy, config, network, and external links
• expands the legend and tooltips so colors, motion, and directions are understandable
• updates documentation and bumps the package version to 0.4.0

UX behavior

Deployment reads left to right: workflow -> CI/CD jobs -> build -> artifact -> deploy.

Runtime reads left to right: public entry -> routing -> workloads -> containers -> configuration.

Environment views keep development, staging, and production separate so their delivery and runtime topology is not mixed together.

Verification

• viewer interaction tests: 13/13 passed
• lint: passed
• typecheck: passed
• production build: passed
• npm pack dry run: passed for @dthreads/atlas@0.4.0

The full test command also reaches the server tests, but this restricted workspace does not permit binding to 127.0.0.1 (EPERM). Core viewer and project assertions pass before that environment-only failure.

Scope

The changes are generic to NestJS projects and contain no Playerok or pl-api-specific paths, names, or data.