feat(ui): explain why controls are locked + keep Emergency usable during hot lock#3
Merged
Merged
Conversation
…ing hot lock - Lock badge now shows 'Locked: <reason>'; native tooltips on every disabled control + a visible hint strip below the heading explain the active lock (hot threshold, cooling band, sensor failure, agent offline, in-flight override) and what unlocks it - During a hot lock the policy still accepts 100%, but the UI was disabling the Emergency button too — it now stays clickable with its own tooltip - render passes the raw safety.reason (map keys are raw codes)
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.
Summary
Locked: <Reason>and every disabled control gets a tooltip + a visible hint strip explaining the active lock and what clears it (hot threshold, cooling band, sensor failure, agent offline, override in flight)request_overrideonly rejects <100), but the UI disabled the Emergency button along with everything else. Emergency now stays clickable with its own explanatory tooltip.Verification
node --checkon the JS