Repository navigation
Make the Home view a clear status summary - #894
Merged
Merged
Conversation
enaboapps
force-pushed
the
883-rows-headers-sidebar
branch
from
September 25, 2026 10:56
29dd84b to
b9c822c
Compare
enaboapps
force-pushed
the
884-home-status
branch
from
September 25, 2026 10:56
2167160 to
e9247b4
Compare
enaboapps
marked this pull request as ready for review
September 25, 2026 11:49
The Home band becomes a status hero whose title names the state (Ready, Finish setting up, Paused, Paused for mobile, or needs attention), with a matching leading-edge tone and one action that is primary only while something is left to do. Input access, switches, scanning and the optional mobile connection share one readiness checklist. Status tiles show done or needs-attention with both colour and a corner badge, and are hidden from assistive tech since the row text already says it. Closes #884 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The title was computed separately from the message and could contradict it: unavailable input access said "Finish setting up", Remote in control or a mobile connection without a local Select said "Finish setting up", and every launch flashed amber while switches loaded. homeStatus now returns all three from one ordered list of cases, amber only for things a person can fix here, with a test for each case. The mobile row reads "Mobile connection (optional)", and the Mobile page band stays neutral for Bluetooth that is starting, unsupported or failed. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
enaboapps
force-pushed
the
883-rows-headers-sidebar
branch
from
September 25, 2026 11:50
b9c822c to
ff5c0f1
Compare
enaboapps
force-pushed
the
884-home-status
branch
from
September 25, 2026 11:50
0f25257 to
fc784dd
Compare
enaboapps
marked this pull request as draft
September 25, 2026 11:50
enaboapps
marked this pull request as ready for review
September 25, 2026 13:32
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
2 participants
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.
Closes #884. Stacked on #893, tracked in #891.
What changed
aria-hiddenbecause the row text already states the status.Validation
On this head:
npm run lintpassednpm testpassed: 238 Vitest tests and 5 Node testsnpm run buildpassedcargo fmt --check,cargo clippy --all-targets -D warningsandcargo testpassed (566 tests, 1 ignored). No Rust changes in this stack.Review follow-up
An independent review of this layer's head raised these points, now addressed:
src/homeStatus.ts, so they can't contradict each other. Unavailable input access, Remote in control and a mobile connection without a local Select no longer say "Finish setting up". Launch no longer flashes amber while switches load. 13 new cases insrc/homeStatus.test.tscover each state.src/homeStatus.test.ts.🤖 Generated with Claude Code
Rebase validation (2026-09-25)
Rebased onto current
main(7fb8fce, including #881) in stack order.git range-diffshows every commit in this PR is patch-equivalent to its previous head, and the intended parent remains its PR base. On the final stack tip (40c75cc), Node 24.19.0 lint, tests and build passed; Rust 1.97.1 format check, Clippy and tests passed. An independent review of the updated PR heads found no actionable findings. CI is rerunning on each new head.