MOCIlib documentation

[Pierre Siddall (Pierre-siddall)]

PR Summary

Code Reviewer: Erica Neininger (@ericaneininger)

This PR intends to begin the process of documenting the newly added MOCIlib so that developers have better information on how to use the functions which MOCIlib implements.

closes #52

Code Quality Checklist

(Some checks are automatically carried out via the CI pipeline)

• I have performed a self-review of my own code
• My code follows the project's style guidelines
• Comments have been included that aid undertanding and enhance the
  readability of the code
• My changes generate no new warnings

Testing

• I have tested this change locally, using the Moci rose-stem suite
• If any tests fail (rose-stem or CI) the reason is understood and
  acceptable (eg. kgo changes)
• I have added tests to cover new functionality as appropriate (eg. system
  tests, unit tests, etc.)

Test Suite Results - moci - test_new_docs_addition/run1

Suite Information

Item	Value
Suite Name	test_new_docs_addition/run1
Suite User	pierre.siddall
Workflow Start	2026-05-07T09:50:47
Groups Run	all

Dependency	Reference	Main Like
moci	Pierre-siddall/moci@add-mocilib-docs	False
SimSys_Scripts	MetOffice/SimSys_Scripts@main	True

Task Information

✅ succeeded tasks - 115

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

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

[Erica Neininger (ericaneininger)]

Can we please use "MOCI" (capitalised) since it is an acromym (Met Office Coupling Infrastructure)

Otherwise this is a sensible start.

[Erica Neininger (ericaneininger)]

Thanks for the update.