Manage iodef core no_del tweak_iodef

[mo-marqh]

PR Summary

Sci/Tech Reviewer: Harry Shepherd (@harry-shepherd) - -->
Code Reviewer: Benjamin Went (@MetBenjaminWent)

This PR removes the lfric_core dependency on tweak_iodef
The script is left in the source until a following PR can remove lfric_apps dependency on this, at which point it can be deleted.

Instead, XML component fragments are addressed directly, through source symlinks, and through rose / cylc configurations

This then enables static analysis of XML files that are used as iodef.xml files by XIOS, introducing testing of XML in the source tree and the opportunity for XML rules encoded in the depths of the lfric xios interface to be tested directly, improving management of XML configurations

Code Quality Checklist

• I have performed a self-review of my own code
• My code follows the project's style guidelines
• Comments have been included that aid understanding and enhance the readability of the code
• My changes generate no new warnings
• All automated checks in the CI pipeline have completed successfully

Testing

• I have tested this change locally, using the LFRic Core rose-stem suite
• If required (e.g. API changes) I have also run the LFRic Apps test suite using this branch
• If any tests fail (rose-stem or CI) the reason is understood and acceptable (e.g. kgo changes)
• I have added tests to cover new functionality as appropriate (e.g. system tests, unit tests, etc.)
• Any new tests have been assigned an appropriate amount of compute resource and have been allocated to an appropriate testing group (i.e. the developer tests are for jobs which use a small amount of compute resource and complete in a matter of minutes)

trac.log

Test Suite Results - lfric_core - manage_iodef_core/run4

Suite Information

Item	Value
Suite Name	manage_iodef_core/run4
Suite User	mark.hedley
Workflow Start	2026-08-19T15:27:36
Groups Run	all

Dependency	Reference	Main Like
lfric_core	mo-marqh/lfric_core@manage_iodef_core	False
SimSys_Scripts	MetOffice/SimSys_Scripts@cab3315	True

Task Information

✅ succeeded tasks - 434

Security Considerations

• I have reviewed my changes for potential security issues
• Sensitive data is properly handled (if applicable)
• Authentication and authorisation are properly implemented (if applicable)

Performance Impact

• Performance of the code has been considered and, if applicable, suitable performance measurements have been conducted

AI Assistance and Attribution

• Some of the content of this change has been produced with the assistance of Generative AI tool name (e.g., Met Office Github Copilot Enterprise, Github Copilot Personal, ChatGPT GPT-4, etc) and I have followed the Simulation Systems AI policy (including attribution labels)

Documentation

• Where appropriate I have updated documentation related to this change and confirmed that it builds correctly

PSyclone Approval

• If you have edited any PSyclone-related code (e.g. PSyKAl-lite, Kernel interface, optimisation scripts, LFRic data structure code) then please contact the TCD Team

Sci/Tech Review

• I understand this area of code and the changes being added
• The proposed changes correspond to the pull request description
• Documentation is sufficient (do documentation papers need updating)
• Sufficient testing has been completed

(Please alert the code reviewer via a tag when you have approved the SR)

Code Review

• All dependencies have been resolved
• Related Issues have been properly linked and addressed
• CLA compliance has been confirmed
• Code quality standards have been met
• Tests are adequate and have passed
• Documentation is complete and accurate
• Security considerations have been addressed
• Performance impact is acceptable

[Harry Shepherd (harry-shepherd)]

Could you double check this regex and it's comment please?

I don't think it matches strings starting with ../metadata.

I also think it will match some non-alphabetic following characters, for example I think:
$SOURCE_ROOT/bob/bruce matches
etc/bob33 matches
etc/33bob doesn't match

[mo-marqh]

tests rerun and updated trac.log output placed in PR description

[mo-marqh]

hopefully ready for re-review Harry Shepherd (@harry-shepherd)