docs: add references to mdr and fix commit msg instructions for warp #94
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.
This pull request primarily updates documentation to improve clarity, accuracy, and traceability for both developers and regulatory compliance. The most significant changes include correcting naming conventions for projects and libraries, updating architecture and communication pattern descriptions, adding references to canonical documentation for commit messages and scopes, and introducing a comprehensive index to the MDR documentation folder.
Documentation improvements and corrections:
WARP.mdto use consistent, uppercase naming conventions (e.g.,GenORDER,GenSOLVER,GenUNITS,GenFORM) and corrected references throughout architecture and library descriptions. [1] [2] [3]WARP.mdto reflect updated source directory structure for server, client, and shared components, and clarified the location of API contracts. [1] [2]WARP.mdto canonical documentation for commit message instructions and supported scopes, improving traceability and consistency for contributors. [1] [2]docs/mdr/README.mdto organize MDR compliance documentation, making it easier to navigate design history, requirements, risk analysis, usability, post-market surveillance, validation, interfaces, and regulations overview.