D1.3 Freeze weekend: DTC on Relay in production

Plan issue D1.3, phase 1 of the community-base unification plan.

Spec: docs/plan/phase-1.md, section D1.3, in DataTalksClub/community-base. Status is tracked in docs/plan/STATUS.md there, which stays the source of truth.

Depends on: D1.1, D1.2cb. Do not start until every one of them is done in STATUS.md.

Freeze issue. Playbook P13 applies: this moves data during a scheduled weekend freeze of the site. Do not start it outside a planned freeze window.

Process

This repository's AGENTS.md and _docs/PROCESS.md govern this work, with _docs/specs/ as the product authority. The plan says what to build and how to verify it; the site process says how work is done here.

Spec

Repository: DataTalksClub/website. Depends on: D1.1, D1.2cb. Freeze required: yes. Playbook P13.

Production checks after deploy:

• jobs_ingress_selftest in the production container -> OK.
• One scheduled job fires and succeeds within its cron interval.
• One real transactional send to an owner mailbox reaches delivered.
• Relay status contract green; DTC Studio jobs page shows no dead intents.

Done when

• the checks above are pasted into the issue and the freeze label is removed

First read docs/plan/phase-1.md section D1.3, docs/plan/STATUS.md, AGENTS.md, _docs/PROCESS.md, and _docs/specs/; confirm D1.1 and D1.2cb are done before scheduling Playbook P13. During the planned freeze, run jobs_ingress_selftest in the production container and verify a scheduled job, transactional send, relay status contract, and DTC Studio jobs page. Done means the checks are pasted into the issue and the freeze label is removed.