CI/CD release tracking

CiCdReleaseWorkflow.cs demonstrates a deployment pipeline that records each release in Okatana.

The workflow chooses a stable marker such as [release:v2.8.0], searches existing project tickets, creates a ticket only when needed, discovers the deployed board by slug, moves the ticket after deployment, and appends a deployment comment.

This is intentionally reconciliation-first. Because create operations have no idempotency key, a pipeline should be able to restart after a runner crash without blindly creating another release ticket.

Recommended operational metadata includes the release version, source revision, environment, deployment URL, CI run ID, and UTC deployment time. Keep secrets and access tokens out of the ticket body.

Scopes normally include tickets:read, tickets:write, boards:read, and comments:write.