If you can't run winapp yourself (no shell, or the command is denied), give the user the exact winapp devtools / winapp run command(s) that would answer their question instead of only reasoning from source. Say which values you read from source and which only the running app can confirm.

Start with the target

Use winapp ui and the winapp-ui-automation skill for general Windows UI Automation: actions, screenshots, waits and accessibility across app frameworks. DevTools is for WinUI 3 XAML trees/source, bindings and dependency-property diagnosis or edits. Both tools accept an element's AutomationId as its selector, so an AutomationId from winapp ui works in winapp devtools and the aid= shown by DevTools works in winapp ui invoke/click. Generated selectors (slugs, handles) belong to one tool; copy a fresh one from that tool's inspect or search.

winapp run .

winui-devtools

Start with the target