Conflicted link-repair journal re-alerts on every launch #33

New issue

Open

opened 2026-09-16 00:32:09 +00:00 by kayg · 0 comments

kayg commented

2026-09-16 00:32:09 +00:00

Owner

Overnight (Main), found while running VM checks: a stale pending link-repair journal (Indexes/LinkRepairs/v1-6fb1e0c3-…-1000013-82341.json, move of notes/plain-first-lrenamed-…32900000.md → notes/editor-performance-10k-no-image-32900000.md from an earlier perf run) whose destination had since changed produced the modal 'Some links could not follow a renamed file…' on EVERY launch, forever, and blocked the ⌘/ search recipe in checkers (root cause of several 'checker never reached fixture' results tonight). Product question for the morning: a conflicted journal should surface once (or offer discard/keep) rather than re-alert on every launch. Cleared on the VM by nulling pending (backup at /tmp/stale-repair-journal.json on the VM).

Overnight (Main), found while running VM checks: a stale pending link-repair journal (`Indexes/LinkRepairs/v1-6fb1e0c3-…-1000013-82341.json`, move of `notes/plain-first-lrenamed-…32900000.md` → `notes/editor-performance-10k-no-image-32900000.md` from an earlier perf run) whose destination had since changed produced the modal 'Some links could not follow a renamed file…' on EVERY launch, forever, and blocked the ⌘/ search recipe in checkers (root cause of several 'checker never reached fixture' results tonight). Product question for the morning: a conflicted journal should surface once (or offer discard/keep) rather than re-alert on every launch. Cleared on the VM by nulling `pending` (backup at /tmp/stale-repair-journal.json on the VM).

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

kayg/calternal-macos#33

No description provided.

Rows
Columns