Move AI orchestration runtime out of phases

[luisorofino]

What does this PR do?

Moves AI flow runtime concerns out of the phases package and into a dedicated runtime layer:

• Moves PhaseOrchestrator to ddev.ai.runtime.orchestrator.
• Moves checkpoint handling to ddev.ai.runtime.checkpoints.
• Extracts concrete run-scoped resources into ddev.ai.runtime.resources.RunResources.
• Extracts phase registration and discovery into ddev.ai.phases.registry.
• Adds a PhaseResources protocol in ddev.ai.phases.resources so phase implementations depend on a small resource contract instead of the concrete orchestrator module.
• Updates imports and tests to match the new package boundaries.

Motivation

The AI framework now has clearer responsibility boundaries: phases define executable phase behavior, while runtime owns orchestration, checkpoints, and run-scoped resource wiring. This also improves dependency direction: the runtime layer depends on phases, and phases depend only on the PhaseResources protocol rather than the orchestrator implementation.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[luisorofino]

• Add max_timeout to PhaseOrchestrator's arguments #24010
• Add context flags to TaskConfig #23992
• Centralize agent logging behind scoped callbacks and remove artifact_root tramp data #23935
• Improve readability of run_tasks in AgenticPhase #23919
• Move AI orchestration runtime out of phases #23916 👈 (View in Graphite)
• Decouple AI agent runtime construction #23912
• Replace extra_init_kwargs with polymorphic Phase.build() factory and ResourceProvider #23889
• loa/openmetrics-ai-gen

This stack of pull requests is managed by Graphite. Learn more about stacking.

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run