• src/doors/syncduke/EVENTS

    From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Wed Jul 1 23:24:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/cf924b596761df48f1b9b4ef
    Added Files:
    src/doors/syncduke/EVENTS_DESIGN.md
    Log Message:
    syncduke: design doc for events.jsonl + shared game_lobby.js events layer

    Sub-project A of converging both lobbies on game_lobby.js: SyncDuke door emits events.jsonl (start/level/death) via -eventlog; game_lobby.js gains generic events read/prune/feed + time helpers; SyncDuke's lobby adds a recent-activity view using them. SyncDOOM untouched (its migration onto the shared layer is Sub-project B). Schema mirrors SyncDOOM so the shared reader parses both.

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

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Wed Jul 1 23:24:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/40083155d7a8775e46e4b2b7
    Added Files:
    src/doors/syncduke/EVENTS_PLAN.md
    Log Message:
    syncduke: implementation plan for events.jsonl + shared events layer

    Task-by-task plan (Sub-project A): door -eventlog + events.jsonl writer + start event + per-frame tick (T1), level + death detection (T2), game_lobby.js generic
    read/prune/feed/ago/mmss with a headless jsexec test (T3), SyncDuke lobby wiring
    + recent-activity view (T4), and full build/test/runtime validation incl. a guard that SyncDOOM stays untouched (T5).

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

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sat Nov 14 17:21:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/2d7a6e1724220b2696972ca7
    Modified Files:
    src/doors/syncduke/EVENTS_DESIGN.md SYNCDOOM_VS_SYNCDUKE.md
    Log Message:
    syncduke: document the death cause, frag and end event records

    EVENTS_DESIGN.md's schema listed only start/level/death, with the death record's original fields. Add the cause and by fields, the frag and end records, how the cause is determined and how the lobby feed words each
    record. The original scope notes are annotated, not rewritten.

    SYNCDOOM_VS_SYNCDUKE.md no longer lists the events log as a difference
    beyond the one that remains: SyncDuke's end record is per door session, SyncDOOM's per game.

    Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net