Add module lifecycle governance for TNT 1.1.0#56
Merged
Conversation
Add module validation, install profile generation, maintainer coverage tooling, and runtime isolation for invalid or flooding modules. Refs #55
Owner
Author
|
Self-review complete. Local release preflight, local full integration tests, whitespace checks, private-string scan, and the GitHub Ubuntu/macOS PR gates all passed. |
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
1 participant
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.
Summary\n\nThis prepares TNT 1.1.0 by adding the core-side lifecycle and safety pieces needed for third-party modules while keeping TNT itself minimal and Unix-friendly.\n\nChanges include:\n- Add module manifest and handshake validation via scripts/module_check.sh.\n- Add a non-mutating install wizard that generates reviewable env files for core-only, all-compatible, selected, and manual module deployments.\n- Harden module runtime isolation for invalid module names, response floods, and repeated invalid responses.\n- Add MAINTAINERS-style ownership mapping and coverage checks.\n- Update release metadata and changelog for 1.1.0.\n\n## Validation\n\n- make release-check\n- make test\n- git diff --check HEAD~1..HEAD\n- repository scan confirmed no private test-server strings are present\n\nCloses #55