Tell On timer how late its frame is, so time minus late is exact (#224)

A timer can only fire on a frame. It fires on the first frame past each
due time, so Time.time at that moment is the due time plus up to one
frame. On a display that is not exactly 60 Hz this delay creeps up by
a millisecond every few seconds and falls back to zero once it reaches
a whole frame. The issue saw 82.009 after 82 ticks. The timer itself
does not drift, it keeps the remainder when it fires.

- On timer gets a number output late. It is what is left of the
  timer's clock after taking one interval, so time - late is exactly
  the due time.
- When one long frame catches up several ticks, each gets its own
  late. The first one was due longest ago and is the latest.

Tests:
- New unit test in behavior-events: late 0.125 after a frame past
  1.0 s, 0 on the dot, 1.5 and 0.5 for two ticks caught up in one
  frame.
- Counter-check: late taken before the interval is subtracted fails
  exactly that test. Original restored with cmp.
- ./check.sh: 156 files, 2300 tests, CHECK EXIT 0 (was 2299).
- No e2e change. The e2e modules only wire the exec of On timer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/core/graph/nodes/events/OnTimer.ts

@@ -1,12 +1,13 @@
 import type { NodeDef } from '../../NodeRegistry';
-import { exec } from '../shared';
+import { exec, num } from '../shared';
 
 export const OnTimer: NodeDef = {
   type: 'OnTimer',
   label: 'On timer',
   category: 'event',
-  description: 'Runs every N seconds.',
+  description:
+    'Runs every N seconds. It can only run on a frame, so late says how far this frame is past the due time.',
   inputs: [],
-  outputs: [exec()],
+  outputs: [exec(), num('late')],
   params: [{ key: 'interval', label: 'Interval (s)', kind: 'number', default: 1, min: 0.01, step: 0.1 }],
 };