Cross-repository consistency
Git repositories do not provide a distributed transaction. A release manifest supplies the missing association: it identifies exactly which code and documentation were validated together. Publishing versioned documentation before runtime activation avoids shipping an undocumented behavior, while the current-version pointer changes only after verification.
Concurrency and retries
GitHub concurrency is repository-scoped, so every host mutation passes through one coordinator. Retries must be idempotent and may safely resume after a transient tunnel disconnect. Changes to the connector itself run last because a broken connector can strand the deployment job.
Rollback limits
Switching a symlink can roll back application code, but does not undo arbitrary data migrations. This release introduces no production application schema migration. Baseline service files and sensitive settings require explicit backups and carefully scoped restoration.