Repository navigation
docs(plugins): explain module contracts and verify plugin examples - #69
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explain the responsibilities of modules and plugins, service lookup, configuration and lifecycle ownership in four bilingual guides. Provide a complete external plugin example covering its public headers, CMake target, exported entries, application manifest and actual load/update/unload flow.
The branch incorporates accepted main
6b773269b6c761d18e87bd96665780d24e2447ca. Only the original four guide documents differ; their text and twelve bilingual code blocks are unchanged from the reviewed implementation. The newly accepted source layout and architecture archive are preserved.Validation at
2e3db816cb9af6ea40ff198ccb96bf371d02b201, tree2244a4c94c27516215f3d815249eced239d72ca5:Windows/Linux execution of this particular external example was not performed locally. The guides describe current lifecycle limits and do not introduce hot replacement, a general callback-drain guarantee or a shutdown-policy change. Published-head checks and the actual protected merge-queue candidate remain required before squash acceptance.