Fix host-owned notification compatibility and history tabs - #33
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
popupModeland legacypendingModel/pastModelcontractscolor04for Recent andcolor03for LiveValidation
Passed:
omarchy-shell shell ping: okapp: vesktop)The pinned host-facing contract gate remains blocked by the documented Omarchy baseline content drift (
expected 36dfa90..., installedf365399...). No multi-output, mixed-scale, or full visual-freeze acceptance is claimed from fixtures.Ownership
Omarchy remains the sole Notifications owner. Shibumi exposes only primitive adapter models and typed actions; it does not create a replacement NotificationServer or read private host state files.