A declarative workflow family has been hardened with version-bound catalog resolution, cross-handoff integrity rules, durable provider acknowledgements, bounded polling, and inherited approval gates. The implementation is committed on an isolated branch while another long-running plan is active elsewhere. The remaining question is how to integrate the branch, run a real provider-backed canary, synchronize the catalog, and activate exactly the proven version without disturbing concurrent work or allowing repository/database divergence.