Follow the systemd journal into timelines; name journald imports by their cursor
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
Closes #151. server/journald-receiver.mjs runs journalctl --follow --output=json, on this machine or another over SSH, and adds each entry as a moment, routed like the log importer's (by unit, identifier, host, severity or any field). It reads entries exactly as `och-import-logs --format journald` does, so a live stream and an import of the same entries make the same moments. It keeps the cursor of the last entry sent and resumes after it on restart, missing nothing written meanwhile and sending nothing twice; journalctl is restarted after the last entry read when it stops. Journald moment IDs now come from each entry's __CURSOR: journalctl prints an entry's fields in a different order on each run, so the line's text, which named it before, changed from one import to the next and re-importing an overlapping range duplicated it. The syslog receiver's queues move to server/moment-ingest.mjs, shared by both. Debian and RPM packages install openchronology-journald.service (in the systemd-journal group, with its cursor in a state directory) and journald.env. docs/journald.md compares the journal with syslog forwarded from it. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/349e283919522765d4ff8e816a06301834774d2f