process-lifecycle

Automating DDEV lifecycle for Drupal worktrees involves starting the environment, enforcing readiness checks, and executing orderly shutdown procedures. This requires resolving the project root from configuration files and using worktree-relative paths to manage container instances.

Readiness gating for DDEV environments requires checking container status, PHP version, database access, Chrome webdriver availability, and vendor dependencies. These checks prevent mid-task failures and ensure the environment is fully operational before development or test execution begins.

Enforcing completion criteria before DDEV shutdown requires running coding standards checks, static analysis, and tests as quality gates. The lifecycle process supports error recovery and stuck detection patterns to handle failures and ensure resources are cleaned up properly after work completes.

DDEV environments can get stuck during worktree bootstrapping due to unresolved project root paths, missing dependency installation, or container instance slot conflicts. The lifecycle process includes stuck detection patterns and phase-based execution recovery to resolve these issues and ensure proper environment initialization.

Managing multiple Drupal worktrees simultaneously requires guarding DDEV instance slots and using worktree-relative paths to isolate environments. The lifecycle process coordinates phase-based execution across separate worktrees, ensuring each environment is independently bootstrapped, validated, and released.

Automating DDEV container shutdown requires resolving the project root from configuration files and enforcing completion criteria. Limitations include dependency on environment readiness checks and the need for error recovery mechanisms to handle stuck detection patterns during phase-based execution and resource cleanup.