[RFC] SUAVE dependency isolation (suave_compat shim + dedicated venv + CI job)

[aligatoralex]

Tracking issue for RFC 0003

How YAADO should depend on SUAVE 2.5.2, given it needs --no-build-isolation + three runtime shims and cannot go in the uv-locked env. Full proposal in PR #40 → docs/rfc/0003-suave-dependency-isolation.md; evidence in PR #33 (docs/SUAVE_INTEGRATION_NOTES.md).

Recommendation

• Add a tested suave_compat shim module (turning PR docs: SUAVE 2.5.2 install/integration notes (feasibility + API validation) #33's monkeypatches into maintained code: collections.MutableMapping alias, cumtrapz→cumulative_trapezoid, a scipy.misc.derivative replacement) imported before import SUAVE.
• Keep SUAVE in a dedicated venv, never uv add'd; move to a baked container later.
• Separate CI job for the [FEATURE] Update VehicleFactory to support vehicle-agnostic ComponentStore architecture #29 gated test (submodule checkout + shimmed venv); SKIPPED in the shared env stays the default until then.

Decisions needed

• suave_compat location (YAADO_Core/modules/ vs a tools//integrations/ home — it is glue, not physics).
• Container now or later.
• Owner + method for validating the scipy.misc.derivative replacement's numerics.

Discuss on PR #40.

[aligatoralex]

Update: RFC content moved from PR #40 (closed, superseded) to docs/rfcs/0003-suave-dependency-isolation.md in PR #47 (single consolidated docs PR, see #47 for why). No content change — same RFC. Discussion continues here.

---

Generated by Claude Code