v0.16.11 — sign in against your tenant, not /common

Two bug fixes, both from field reports:

The setup wizard now authenticates against the tenant you actually signed into. Silent token calls no longer go to the /common authority (which fails for some accounts even when the same sign-in works tenant-specifically), the wizard re-points itself at your tenant the moment sign-in reveals it, and post-sign-in failures surface the real Microsoft error instead of a misleading "resource may not be registered" message.

npm 12's install-script blocking no longer breaks secure token storage. If npm blocked keytar's install script, sign-in appeared to work and then everything reported "not authorized." Setup and --doctor now detect and repair this automatically — or install with the scripts allowed up front:

npm install -g --allow-scripts=@azure/msal-node-extensions,keytar powerautomate-mcp

Upgrade: quit your AI clients, then npm install -g powerautomate-mcp@latest. Full detail in CHANGELOG.md.