Notes from using wicket

I used wicket today mostly successfully to test some stuff. While I had watched demos, there were a few observation that I jotted down trying to use it that I wanted to list here. I'm not sure if these all should be acted upon, but thought I should mention them. I'm leaving triaging off and will let folks working on it figure out what milestone is appropriate if any. I realize these may not be the clearest, so please reach out.

• Would love some way to tell what's present or not at the wicket home page.
• Seeing everything greyed out made me think that nothing was detected (didn't realize I should have tabbed over). Though everything was colored as though it existed when I did.
• Some way to discover available keys. Maybe '?' can pop up how to do things?
• On update screen would love a way to know which sleds exist or are present at all.
• What is the MGS connected status for and what does it mean? I see it counting up which at first made me think it was how long I was connected to it, but then it always resets.
• I had no way to discover that hitting enter on the mupdate screen would have led to showing details while actively performing an update.
• Status for installinator is Waiting for progress (at 0.00ns) during the host update sequence but that's probably related to #3282.

Start by reproducing the Wicket home, update, and mupdate screens described in the issue, including the tab, Enter, and ? interactions. The issue provides no file or test entry point; triage each observation separately and define completion for any selected status, discoverability, or feedback change before implementation.