🚀 elevata v0.5.2 — Metadata stability & History foundation

This release significantly improves the robustness, determinism, and safety of
history metadata generation in the RAWCORE schema.

---

🔁 RAWCORE → HIST Synchronization

✔ Deterministic generation of *_hist datasets

• Based on lineage_key instead of dataset name
• Automatically created/updated when RAWCORE metadata changes
• Fully system-managed (is_system_managed=True)

✔ Idempotent schema sync

• Drop orphaned components and columns before rebuild
• Recreate history columns in a canonical order
• No more UNIQUE or foreign key conflicts

✔ History surrogate key improvements

• <rawcore_name>_hist_key automatically generated
• Expression built from rawcore SK + version_started_at

✔ Business key propagation

• RAWCORE SK also marked as BK in _hist
• Lineage via TargetColumnInput for every non-tech col

---

✨ UI & Signals

✔ Inline rename now updates both RAWCORE & HIST instantly

• Signals ensure sync of dataset name + columns
• HTMX out-of-band swap updates _hist grid row as well
• _hist objects are fully read-only in the UI

---

🛡️ SQL Preview Behavior

• build_sql_preview_for_target returns a clear comment for _hist
  instead of misleading SELECT queries
• New tests guard this behavior against regressions

---

🔬 Test Coverage

• New tests for SQL preview routing
• Stability fixes for history generation test suite
• All HIST-related tests now stable and passing

---

🧭 What’s next (v0.6.0 Roadmap)

• Dialect capabilities & health checks
• Incremental load path (Merge + Update/Insert fallback)
• History-based delete detection
• Load-run observability & debug plan output

---

This release stabilizes the complete foundation for historization metadata.
Incremental loads and delete detection will build on this in v0.6.0.

Full Changelog: v0.5.1...v0.5.2