forge:apply

To apply approved code changes after gate approval, use an automated apply pipeline that reads the handoff, creates a run, coordinates tasks, and performs lifecycle cleanup. This ensures transparent and auditable propagation into the repository.

The apply pipeline for code deployment worktrees automates run creation, reads the approved handoff, coordinates implementer and documenter tasks, and executes post-apply lifecycle actions to ensure transparent and traceable code deployment.

Yes, you can integrate git branch creation, committing, and PRs into an automated code deployment workflow. The pipeline supports optional git integration with robust error handling to avoid blocking the deployment pipeline.

Yes, you need prior Gate #2 approval before automating source file updates. The apply process enforces safety checks and reads the approved handoff to ensure only authorized changes are applied to the repository.

An automated apply workflow stops after creating a run if safety checks fail or gates are not cleared. The pipeline enforces safety checks, logs outcomes, and returns control to the user when gates require manual intervention.