Fix sidebar crash with OpenCode 2.0.10 themes - #26
Merged
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
1 participant
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.
Opening the runtime sidebar on OpenCode 2.0.10 crashed because the host removed
text.statusand renamed semantic color tokens. This also affected folders without initialized automation.Resolve both 2.0.6 and 2.0.10 tokens, retaining normal unavailable-owner status in unconfigured folders. The native renderer now runs against resolved themes from both SDK versions and covers startup, missing owners, running tasks, stale readings, session selection and narrow layouts. Its exit guard also prevents an OpenTUI early shutdown from passing the test silently.
Documentation: updated runtime and installation references and Unreleased notes. Workflow phases, polling, ownership and recovery are unchanged; the eight workflow diagrams remain accurate and need no edits.
Validation:
npm run check; local documentation link targets andgit diff --check. Running the new regression fixture against the original sidebar reproduces the reported error and exits unsuccessfully.