Under the hood
Useful2 Signal0
Background session attaches now write a small journal file so crashed attaches still report what happened later.
What's wrong with this entry?
Anonymous. No account, no email.
What
Every background attach writes a journal file so an attach that dies with its process still reports an outcome on a later run.
Details
- JSON journal under an
attach-journaldirectory, created with mode 0700 and files 0600, deleted on completion. - Updated as milestones land: marksExpected, daemonBooted, interactiveReached, attachMs, msgsLoaded, msgsInJsonl, msgsRenderedAtFirstPaint.
- On a later run, orphaned journals whose owning process is gone, or older than 24h (15 min for live pids), are claimed and replayed as synthetic tengu_bg_attach_outcome events carrying
journal_recovered. - Windows rename and unlink contention gets 4 retries; files that still cannot be unlinked are renamed with a
.clearedsuffix.
Evidence
journal_recovered
Strings lifted out of the shipped bundle, so the claim above can be checked against them.