Skip to content

fix(startup): suppress drained invalid-secondmate-home diagnostic per fingerprint - #162

Merged
prajwal-395 merged 1 commit into
mainfrom
fm/fm-invalid-secondmate-home-rewakes
Sep 22, 2026
Merged

prajwal-395 merged 1 commit into
mainfrom
fm/fm-invalid-secondmate-home-rewakes

Conversation

@prajwal-395

Copy link
Copy Markdown
Owner

The invalid marker diagnostic used publish_actionable alone, so a persistent marker re-woke on every startup scan after its drain. Queue it through a per-fingerprint diagnostic record with queue_notice_once instead, and retire the record on a healthy scan, so a changed marker or a repaired-then-invalid home wakes again. Proved by test_invalid_secondmate_marker_wake_does_not_rewake_after_drain, which fails on the base code.

… fingerprint

The invalid marker diagnostic used publish_actionable alone, so a
persistent marker re-woke on every startup scan after its drain.
Queue it through a per-fingerprint diagnostic record with
queue_notice_once instead, and retire the record on a healthy scan,
so a changed marker or a repaired-then-invalid home wakes again.
@prajwal-395
prajwal-395 merged commit 2b7f835 into main Sep 22, 2026
27 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant