Authentication and scoped grants

Management requests use X-Admin-Key: <wgk_...>. Store the value in an OS keychain or environment variable and pass only its reference to MCP configuration. Never commit a literal key.

weirgate auth login opens https://dashboard.weirgate.com/consent by default. The signed-in developer reviews tenant, apps, tool groups, scope, environment, and expiry; the CLI exchanges the resulting single-use localhost callback code and stores the reveal-once bounded key in macOS Keychain. Propose is the default. Apply consent requires a recent Clerk second factor. --stdin remains available for an already-minted key.

Scopes are hierarchical: read < propose < apply. Resource bounds are independent: app_ids, tool_groups, and environment further constrain the key. A propose key can create and cancel its own pending proposals, but applying a proposal or creating a grant requires apply scope. Cross-tenant and out-of-bound app reads return resource_not_found.

The platform super-admin credential is for founder operations only. It is not accepted by the MCP server or CLI authentication workflow.

GET /v1/admin/auth-presets returns non-secret templates for Firebase, Supabase, Clerk, and custom public OIDC/JWKS issuers. Standards-based configs use mode: jwks with an HTTPS issuer, public HTTPS JWKS URL, optional audience, and an external-ID claim that defaults to sub. Service-role secrets are never accepted.