No prod deploy pipeline for the IDS-hosted DataSpace (dataspace.open-contracting.in)

deploy-IDS-Dataspace.yml triggers on dev only. The IDS-hosted DataSpace production instance (dataspace.open-contracting.in) has no automated deployment path.

Why this one has history

That host served HTTP 502 for five weeks before anyone noticed (DataSpaceFrontend#449). A stale build sat there with nothing to detect it. Coverage now exists for the symptom — IDS-DRR-QA-Automation#17 added availability smoke checks against both dev and prod — but there is still no pipeline to deploy a fix through when it next breaks.

Scope

Same shape as deploy-Dataspace.yml, which already handles dev and prod in one workflow via a branch-conditional environment:

• trigger on main with environment: production
• digest-pinned deployment
• health gate before promoting
• smoke gate — the DataSpace availability tests from IDS-DRR-QA-Automation#17 are the obvious candidate, since they assert exactly the failure that went unnoticed
• automatic rollback that still reports the run red