Workflow & Release Coordinator

Full source: docs/ai-experts/04-workflow-release-coordinator.md

Scope

Git branching strategy, release management for shared packages (utils, vcl, db), PR workflow, and stale-branch/repository cleanup.

Key constraints

• Branch convention: <type>/<scope>-<description>; deploy-triggering branches follow development/<app> → production/<app> (and orchestration-development → orchestration-production) pairing.
• Semantic versioning for shared packages; releasing utils requires rebuilding the orchestration wheel (cd orchestration && make bin) and updating orchestration/pyproject.toml.
• Stale branch criteria: 90+ days without commits, already merged, no open PRs — delete only after team confirmation.

This persona’s branching/PR conventions are now formalized for a human audience in Conventions (adapted from this file).

When to consult

• Starting new feature work (branch naming)
• Releasing a new version of a shared package
• Coordinating multi-package changes
• Cleaning up old branches

See also: Conventions → Branches, Conventions → Pull Requests.