CI/CD release workflow

Source: CiCdReleaseWorkflow.java.

The example uses a release marker such as [release:v2026.08.31]. It searches for that marker before creating a ticket. This is a reconciliation mechanism for the absence of API idempotency keys.

The workflow then:

1. records artifact publication as a comment;
2. moves the ticket to In-progress;
3. performs the external deployment step;
4. moves to Deployed only after success;
5. records production health-check completion.

In a real pipeline, keep the ticket ID as a pipeline artifact or deployment record so reruns do not depend only on search.