Update resource limits and return value

Matistjati · niemela · commit b03c6a2f0162 · 2025-12-31T05:58:21.000-06:00
diff --git a/spec/2025-09.md b/spec/2025-09.md
@@ -1431,11 +1431,10 @@ If a system does not support displaying multiple image files, then it should dis
 or alternatively the last image file according to lexicographical order.
 
 Compile or run-time errors in the visualizer are not judge errors.
-The return value and any data written by the visualizer to standard error or standard output are ignored.
-Judge systems may impose limits on the output visualizer's usage of resources, including runtime, memory or the amount of output written to stdout.
+The return value and any data written by the visualizer to standard error do not carry special meaning and may be ignored.
+Judge systems may impose limits on the output visualizer's usage of resources, as described in [Resource guarantees](#resource-guarantees).
 Exceeding any of these limits is not a judge error.
-It is recommended that the judge system allows the output visualizer at least 5 seconds of runtime.
-To avoid timeouts, it is advisable to limit the output size, as the input to the visualizer is typically user-controlled.
+To avoid exceeding any of the resource limits, it is advisable to limit the output size, as the input to the visualizer is typically somewhat user-controlled.
 
 When writing an output visualizer, one should take care to ensure that it is portable.
 In particular:
