chore(landing): orchestrate release notifications

[saurya]

Summary

• compose attribution, lifecycle updates, Linear comments, and delivery plans
• publish the versioned environment-release JSON schema
• document exact SaaS and Replicated emitter handoffs, including the stable-lane workflow gap

Stack

• Base: chore(landing): render actionable release notifications #260
• Final stack layer

Validation

• cd enterprise && poetry run pytest -q tests/unit/landing_notifications
• Enterprise and root Python pre-commit suites

This PR description was generated by an AI agent (OpenHands) on behalf of the user.

---

Enterprise server image for this PR:

ghcr.io/openhands/enterprise-server:sha-060e7f2

[github-actions]

Feature landing checklist

Before merge

• Documentation added for the feature on the website
• E2E test added covering regression / up-to-spec behavior
• Feature is gated by an ENABLE_<FEATURE> flag and exposed through the appropriate Helm / embedded-cluster configuration

Evidence

• ✅ Linear tracking ticket: chore(landing): define environment release foundation #91
• ✅ Feature flag name: provider execution defaults to dry-run
• ✅ Primary E2E test: enterprise/tests/unit/landing_notifications/test_orchestrator.py
• ✅ Delivery targets: saas-staging, saas-production, replicated-unstable, replicated-beta, replicated-stable

✅ Feature landing evidence is complete.

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
enterprise/server/services/landing_notifications
__init__.py
linear_updates.py					21-29, 51-53, 59-80, 83-84, 87, 90
orchestrator.py					39-61
Project Total

This report was generated by python-coverage-comment-action