David Feltell

Added https://github.com/pybind/pybind11/issues/5359 to see if this can be solved upstream.

Just encountered an issue where I wanted to `@ref resolve` from within `ManagerInterface`/`Manager`, expecting it to link to the member function, when it actually links to the Glossary. I notice...

Some of this was done as part of #1037 by adding a `glossary_` prefix to disambiguate. Looking at the `@section`s in `Glossary.dox`, there are still some ambiguous reference names. I.e....

We have precedent for this with the `EntityReferencePagerInterface`, which has a `close()` method that is called by the middleware on destruction. Similarly the `UIDelegateInterface` also has a `close()` method, called...

We're building up a library of example repos and docs, which should cover this by example.

On reading through the `apiComplianceSuite` I think the number of changes to strip it down would be quite small - most of the tests do seem valuable.

Add a CI job that pip installs OpenAssetIO and uses simpleResolver to resolve from SimpleCppManager. This will test linkage etc.

Note that building as multiple shared libraries is insufficient to provide the ideal plugin loading environment. For example when split into multiple shared libraries, Python will transitively load `libopenassetio` but...

Updated description to focus specifically on the Python package, since that's the end goal. We should still consider warning users that static library builds are unsupported.

Relevant Windows documentation for Python library loading: https://docs.python.org/3/whatsnew/3.8.html#bpo-36085-whatsnew >the system paths, the directory containing the DLL or PYD file, and directories added with [add_dll_directory()](https://docs.python.org/3/library/os.html#os.add_dll_directory) are searched for load-time dependencies >...