Coral 2 → Coral 3 Dialog Upgrade

In-place upgrade of _cq_dialog/.content.xml where nodes use granite/ui/components/foundation/ (without coral/). Only for action: upgrade-coral2. Inputs from .migration/lui-dialog-context.yml.

---

Prerequisites

1. _cq_dialog/.content.xml classified coral2.
2. No _cq_dialog.coral2/ backup (or user confirmed re-upgrade).

---

Resource Type Replacement Table

Pattern rule: granite/ui/components/foundation/ (without coral/) → granite/ui/components/coral/foundation/. Exceptions (pathbrowser → pathfield, fileupload, tagfield) are listed explicitly above — apply each row's exact Coral 3 value, do not derive by prefix substitution. Do NOT replace cq/gui/components/authoring/dialog on the root — correct for both versions.

---

Additional Property Fixes

---

Conversion Steps (per component)

1. Backup: copy _cq_dialog/ → _cq_dialog.coral2/.
2. Read _cq_dialog/.content.xml. Apply resource type replacements. Apply property fixes. Sanitize path property values (rootPath and any property whose value starts with /): strip a leading /libs/ prefix and collapse any // double-slash sequences to /.
3. Write updated file in place.
4. Design dialog (skip if skipReason: editable-templates-in-use): If _cq_design_dialog/ exists and contains Coral 2 resource types, apply the same resource type replacements: backup _cq_design_dialog/ → _cq_design_dialog.coral2/, apply replacements, write in place, and add <exclude pattern=".*/_cq_design_dialog\.coral2(/.*)?"/> to filter.xml.
5. Update filter.xml: add <exclude pattern=".*/_cq_dialog\.coral2(/.*)?"/>.
6. Report: types replaced (N), fixes applied, backup location, whether design dialog was upgraded.

---

Critical Rules

• Always backup before modifying.
• Only replace known Coral 2 types — do not touch unrecognised types.
• pathbrowser → pathfield (different name, not prefix-only).
• fileupload → cq/gui/components/authoring/dialog/fileupload (different path family).