Record the closing-card deployment and pending live smoke

[aryanorastar]

Verified release state

#43 was approved and explicitly authorized to ship independently before held #42. It merged as two-parent dad2505, passed merged-main CI and deployed once as a6c7c577, with 4a8e93d5 as rollback. Health is HTTP 200/status ok; settings and variables are unchanged. New login → old SIGTERM is a 5.100-second proxy and old drain completed for both support and Telegram.

Remaining verification

The requested Spanish/Chinese closing-card and Spanish reopening smoke is still pending user-created synthetic posts. The documents explicitly do not claim a smoke PASS or invent either card text. Raw logs and future card evidence remain private outside Git.

#42 stays held. Its existing-output per-case comparison contains seven changed cases, both runs for each and 28 replies verified verbatim with original judge problems. Escalating signals were not retained by the original runner and are marked unavailable. No new evaluation was run.

#28 remains stopped until explicit confirmation that the channel permissions are fixed. Only the read-only preflight is then authorized; no preparation push before private_staff_destination. No permission changes or #29/#30 work.

Scope and checks

Documentation only: roadmap, architecture, runbook and implementation checklist. No runtime change, credential change or additional deployment. npm test: 668 pass before push. Keep this report draft until the requested live smoke evidence arrives.