[P2][UI-03] Adaptive layouts and reviewable revisions

Programme: #1
Epic: #19

## Objective
Let the interface adapt to explicit preferences and approved learned patterns without silently moving controls, rewriting content or making the application feel unstable.

## Scope
- User preferences for density, typography, ordering, visible fields, panel sizes and default views.
- Pin/lock regions and components against automatic structural changes.
- Live data bindings independent of layout structure.
- Proposed structural revisions with diff/preview/apply/reject.
- Version history and restore for layouts/compositions.
- Adaptation explanations and provenance (explicit preference vs inferred pattern).
- Rules for refreshing articles, feeds and tables while preserving active reading/interaction state.

## Product rules
- Data refresh is not permission to regenerate structure.
- Active controls/reading position should not move unexpectedly.
- User corrections override learned patterns and can lock behavior.

## Acceptance criteria
- [ ] No silent layout revision moves an active control or rewrites text being read.
- [ ] Users can lock regions/layouts and restore prior versions.
- [ ] Structural changes are previewable/reviewable with a meaningful diff.
- [ ] Source-data refresh updates bindings without requiring layout regeneration.
- [ ] Adaptation origin is inspectable and reversible.
- [ ] Failed proposed revision leaves the last approved layout intact.

## Dependencies
- UI-01
- UI-02
- DATA-03

**First phase:** P2
**Maturity target:** P5
**Owner:** workspace-ui-data

## Task issues
- [ ] #417 `UI-03.T01` — Model explicit layout preferences and locks
- [ ] #418 `UI-03.T02` — Implement structural diffs and revision history
- [ ] #419 `UI-03.T03` — Build preview, apply and reject workflows
- [ ] #420 `UI-03.T04` — Implement stable live data updates
- [ ] #421 `UI-03.T05` — Connect explainable adaptation proposals
- [ ] #422 `UI-03.T06` — Implement restore and migration behavior
- [ ] #423 `UI-03.T07` — Qualify layout stability and accessibility

Start by reading dependencies UI-01, UI-02, and DATA-03, then review task issues #417–#423 to identify the first bounded implementation area. Done means the relevant task's acceptance criteria are met without violating the stability, reviewability, reversibility, and data-refresh rules listed here.

Written by the indexing model from the issue text.