test: enforce late-slope restart and shutdown deadlines

scripts/validation/opcua-lifecycle-memory/LATE_SLOPE.md

@@ -36,8 +36,9 @@ observed quiescent RSS and final values. Predeclare these elapsed-time windows:
 | Final late phase | 6600–7200 |
 
 Proposed fixed bounds are startup 120s, each complete cycle including its restart
-30s, cycle deadline 7230s, independent shutdown owners 20s each and container
-deadline 7440s. The final cycle may finish after 7200s, but cannot extend
+30s, cycle deadline 7230s, shutdown ceiling 60s and container deadline 7440s.
+The active restart helper has a separate 25s linked deadline; its elapsed time
+is recorded before post-restart configuration. The final cycle may finish after 7200s, but cannot extend
 its 30s bound. Validate these bounds with reviewed short controls before committing
 the protocol; hitting one makes the diagnostic incomplete, not grounds to relax it.
 
@@ -75,6 +76,10 @@ the generic profile mode currently throws earlier and must keep its old behavior
 Cleanup must attempt both independent owners under their separate deadlines even
 when one fails or the operation token is canceled. Preserve the first rejection
 alongside any later cleanup failure; neither error may erase the other.
+The shutdown ceiling covers 5s to capture manager references, 20s for each
+owner, 5s to delete the private client directory and 10s to verify shutdown.
+Any local deadline or overall elapsed miss is fatal and makes the diagnostic
+incomplete; the container deadline is unchanged.
 
 Before execution, implement and review the proposed setup/last-cycle/cleanup and
 outer deadlines in the actual harness and launcher; no extension or retry-to-green.