TNT needs a small release that keeps the core Unix surface minimal while making third-party modules safer and easier to deploy.\n\nScope:\n- Add a module checker for manifests, entrypoints, handshakes, permissions, events, and minimum TNT version compatibility.\n- Add a non-mutating install wizard that lets deployers choose core-only, all compatible modules, selected modules, or explicit module paths.\n- Harden module runtime isolation for invalid names, response floods, and repeated invalid responses.\n- Add maintainer coverage tooling so core, module interface, packaging, tests, and docs have explicit ownership patterns.\n- Prepare the TNT 1.1.0 release metadata and changelog.\n\nValidation plan:\n- Local release preflight and integration tests.\n- Temporary Linux checkout tests.\n- Manual production-like smoke tests on the private test server without committing any test-server details or automation.
TNT needs a small release that keeps the core Unix surface minimal while making third-party modules safer and easier to deploy.\n\nScope:\n- Add a module checker for manifests, entrypoints, handshakes, permissions, events, and minimum TNT version compatibility.\n- Add a non-mutating install wizard that lets deployers choose core-only, all compatible modules, selected modules, or explicit module paths.\n- Harden module runtime isolation for invalid names, response floods, and repeated invalid responses.\n- Add maintainer coverage tooling so core, module interface, packaging, tests, and docs have explicit ownership patterns.\n- Prepare the TNT 1.1.0 release metadata and changelog.\n\nValidation plan:\n- Local release preflight and integration tests.\n- Temporary Linux checkout tests.\n- Manual production-like smoke tests on the private test server without committing any test-server details or automation.