[Feature]: Improve ambient telemetry realism and modeling assumptions

[nikkogibler]

Area

API or backend

What problem are you trying to solve?

The ambient telemetry layer is part of the product’s atmosphere and worldbuilding, but it should become more internally consistent and better grounded in explicit modeling assumptions.

Proposed solution

Improve one or more telemetry domains and document the assumptions clearly enough that future contributors can extend them intentionally.

Acceptance criteria:

• at least one telemetry domain becomes more realistic or clearly modeled
• implementation notes or comments explain the assumptions used
• API responses remain stable or are updated intentionally with documentation changes

Alternatives considered

• Keep the current atmospheric outputs mostly cinematic. This is simpler, but it limits credibility and makes the simulation layer harder to grow.
• Attempt a highly detailed scientific model across every telemetry surface at once. That would be more rigorous, but it is too broad for a focused contributor issue.

Scope and impact

• improve realism for Mars-time, light-delay, and environmental telemetry outputs
• document or clarify the assumptions behind the current model
• make the data feel more believable without overcomplicating the first iteration

Relevant code:

• artifacts/api-server/src/routes/ambient.ts
• artifacts/api-server/src/lib/marsTime.ts
• artifacts/api-server/src/lib/missionTelemetry.ts

Notes:

This issue is better for someone comfortable with modeling, systems thinking, or space-domain research.

Pre-flight checks

• I searched existing issues and did not find a duplicate.
• I explained the problem, not just the desired feature.