Fixes from running 0.7.1 in production — 20 files, 5 PRs incoming

[jeremiaspf]

Fixes from running 0.7.1 in production — 20 files, 5 PRs incoming

We've been running OntoBricks 0.7.1 in production and found a set of bugs along the way, which we've now fixed and want to send back rather than sit on. Since it's a batch of independent, unrelated issues rather than one thing, we're not filing them as individual GitHub Issues — instead we're opening a small, focused PR per group, and using this thread as the single place with the full context up front.

Two recurring root causes account for most of it:

1. Stale class/property URIs after a domain's Base URI changes. If a class or property already exists when the domain gets re-based, several modules kept trusting the stored uri field as-is instead of rebuilding it from the local name against the current Base URI. Depending on the module, this showed up as: reasoning rules (Aggregate/Decision Table/SPARQL/SWRL) silently returning 0 results; R2RML-generated instances with an rdf:type disconnected from their real class; Digital Twin instances not attaching to their class; orphaned axioms in exported OWL; and Cohort Discovery rules showing 0 members/edges. Fixed consistently across all of them.
2. d3js.org blocked in restricted-network environments (common for Databricks Apps in corporate networks) — every D3-based visualization failed to load. Switched to jsDelivr everywhere D3 is loaded.

The rest are smaller, independent fixes: Lakebase/Postgres SQL-dialect support in the reasoning engines' numeric casting (TRY_CAST doesn't exist in Postgres), an Aggregate Rule preview showing 0 inferred triples without materializing, a Decision Table failing outright on an unmapped input column, the Designer's Constraints tab having no backend to persist to (so Transitive/Symmetric relationship reasoning silently never activated), a missing "Delete rule" button in Cohort Discovery, a couple of save-state bugs in Manual Mapping, and some UX papercuts in the SWRL rule editor.

Full write-up of all of it, organized by area with root cause and effect for each, is attached.

PRs (all against develop, will link here as each goes up):

1. fix(reasoning): Lakebase dialect + stale-URI fix across the four rule engines
2. fix(ontology): stale-URI fix in OWL/R2RML/Digital Twin generation + Constraints tab persistence
3. feat(ontology): Cohort Discovery delete button + stale-URI fix + SWRL editor fixes
4. fix(frontend): D3.js CDN swap (d3js.org → jsDelivr)
5. fix(mapping): Manual Mapping save-state fixes

One more file (src/back/objects/mapping/Mapping.py) has a couple of related fixes we're holding back for now — we found it's grown a substantial schema-drift feature on develop since 0.7.1, and want to make sure our change still makes sense against that before proposing it. Will follow up separately.

All tested against current develop, not just our 0.7.1 baseline. Happy to add automated tests to any of these if useful, or to split/reshape the PRs if you'd rather receive them differently — this is our first contribution here, so tell us if we've gotten the process wrong in some way.

[jeremiaspf]

Follow-up: the two files we held back (Mapping.py / mapping-design.js) are up now, reconciled against the schema-drift feature that landed on develop since our first batch:

• fix(mapping): preserve excluded_attributes on update, backfill relationship source/target class #152
• fix(mapping): stop discarding stale auto-load responses, always clear loading state, keep column-role menu open #153

Both verified to apply cleanly against current develop with no overlap with schema-drift.