Skip to content

fix(doctor): classify standing warnings as advisory - #152

Merged
pitimon merged 1 commit into
mainfrom
fix/137-doctor-standing-warnings
Aug 5, 2026
Merged

fix(doctor): classify standing warnings as advisory#152
pitimon merged 1 commit into
mainfrom
fix/137-doctor-standing-warnings

Conversation

@pitimon

@pitimon pitimon commented Aug 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • classify the headless browser.opener warning as advisory while keeping it visible
  • keep a missing opener on a non-headless host actionable and degrading
  • classify the optional unconfigured notification integration as an advisory preference
  • document the full per-warning audit and preserve fail-closed behavior for failures and malformed IDs

Test plan

  • strict RED/GREEN tests for headless and actionable opener paths
  • strict RED/GREEN test for unconfigured notification preference
  • doctor test suite
  • npm run ci:local

Closes #137

@pitimon
pitimon force-pushed the fix/137-doctor-standing-warnings branch from b1dfda4 to 013f86d Compare August 5, 2026 10:12
@pitimon
pitimon merged commit dbecf80 into main Aug 5, 2026
1 check passed
@pitimon
pitimon deleted the fix/137-doctor-standing-warnings branch August 5, 2026 10:13
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.

doctor: audit all checks for standing warns — browser.opener still pins degraded on a headless host

1 participant