[testing] is opentitan.org open to running unit-testing?

Description

I'm working to get opentitan running in current release of Siemens tools. There are differences of opinion between EDA vendors as to how to interpret the LRMs, as well as projects having various levels of code quality (don't run lint, run all & fix all, and everything in between).
Siemens tools are reporting LRM violations in certain areas. I'd like to propose the following:
a) I can submit code changes which make Siemens tools happy.
b) I can include unit-tests with svunit using edaplayground, where I can verify (to the best of my ability) that the changes generate identical results with VCS and Questa. Note that edaplayground has restrictions on line-counts, so there may be places where edaplayground can't be run.

It would be a shame if opentitan.org simply threw away the svunit unit-tests; one company reported a 97% drop in 12 months in bugs reported to the field, once they switched to unit-testing.

So would opentitan.org prefer that just code-changes be submitted, or code-changes plus unit-tests verifying the change (when behavior is expected to remain identical)?

No repository file, test, or entry point is named. Review the proposed Siemens-tool compatibility changes and the suggested svunit tests in EDA Playground, including comparison across VCS and Questa. The issue is done only when the project’s policy on accepting these code changes and tests is decided.