Split from #32.\n\nUse persisted customization records during update/reload flows and report the outcome clearly.\n\n## Scope\n- load active customization records during update/install flows\n- surface record metadata to the agent/update logic\n- report per-customization outcome: applied cleanly, repaired automatically, needs review, disabled\n- run associated validation or smoke checks when available\n\n## Success criteria\n- update flow loads active customization records\n- agent/update path can inspect metadata for repair decisions\n- result summary clearly reports per-customization status\n- validation hooks run when configured and failures are surfaced\n- tests cover success and incompatible-customization cases\n\nBlocked by: #35, #36\nParent: #32
Split from #32.\n\nUse persisted customization records during update/reload flows and report the outcome clearly.\n\n## Scope\n- load active customization records during update/install flows\n- surface record metadata to the agent/update logic\n- report per-customization outcome: applied cleanly, repaired automatically, needs review, disabled\n- run associated validation or smoke checks when available\n\n## Success criteria\n- update flow loads active customization records\n- agent/update path can inspect metadata for repair decisions\n- result summary clearly reports per-customization status\n- validation hooks run when configured and failures are surfaced\n- tests cover success and incompatible-customization cases\n\nBlocked by: #35, #36\nParent: #32