From 57e254470e11ab40b6bae31b2cbf62aebca27ce4 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Mon, 16 Nov 2026 23:24:29 -0300 Subject: Record every run's frames to a sessions database in xitdb Live play was recorded only after someone typed record N, into 16 fixed slots. Now every run is a session in one xitdb database per sketch, beside its state file (.xitdb): an append-only log of the frames live update was fed, one commit a second of session time, and keyframes of the State at start, every minute, on jumps, before and after reloads and at exit. A kill -9 loses at most the uncommitted second (test-kill). Whether a build records travels in the sketch: App.Options.record, null meaning Debug, reaching the host as Info.record. Scripted runs from fresh state record in memory, exports not at all. Each stretch of a session keeps its build, layout and Info.source: the repository revision (one jj or git call per build, build_info), zig version, backend and mode. Sessions.zig takes plain data (bytes, events, strings, a path, an Io), so a second host can drive it. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_016Y9MNBECMWcJD5pdS4SR6T --- test/kill.script | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 test/kill.script (limited to 'test/kill.script') diff --git a/test/kill.script b/test/kill.script new file mode 100644 index 0000000..824b741 --- /dev/null +++ b/test/kill.script @@ -0,0 +1,5 @@ +# A run without --fresh records to a file; it dies by SIGKILL after 255 +# frames, the last 15 of them not yet committed (test/killed.script). +move 100 80 +frames 254 +kill -- cgit v1.3