Portal v0.42.0 — Signed dispatch uses your own PKI

Signed dispatch now uses ordinary X.509 certificates, so the authority to run an action can come from the PKI you already operate. This release also tightens the point where identity and session authority becomes a durable grant.

Signed dispatch

• Issue signed-dispatch certificates from your own PKI. Each certificate names the runners it may target, and every runner verifies the chain against its configured anchors.
• Identity-bound runner references and a larger attestation envelope keep the complete enterprise certificate chain inside the signed request.

Security

• MFA, SSO, email, invitation, device-grant, session-revocation, and SCIM decisions are rechecked in the transaction that commits the resulting authority.
• Replaying a still-valid spent OAuth refresh token revokes the backing connection and its active successors; reconnecting is required.
• OIDC requests, tunnels, and tenant work are bounded, and every outbound destination passes the same public-address policy.
• SCIM DELETE retires the directory resource and its independent OIDC authority; an exact later POST revives only the directory resource.

MCP Bridge and CLI

• Every MCP tool is available as a bridge command for scripts and clients without MCP support.
• The bridge now owns client connect and disconnect, drains runbook output automatically, and returns actionable validation errors.
• Windows support includes VS Code, native ARM64, direct authentication, and safer client-config replacement. Backups refuse symlink destinations.

Packs

• emisar pack diff shows upgrade changes, emisar pack verify proves setup, and pack suggest can use a registry catalog URL.
• Nomad namespaces are supported, pack setup requirements appear in the console and CLI, and remote reads keep credentials on configured destinations.
• Metrics, logs, and process diagnostics have explicit cost and disclosure bounds; the Redis Sentinel down-state probe is structurally read-only.

Console and docs

• Owners and administrators have an audited break-glass override for an unreachable approval quorum.
• Pricing cards, comparisons, FAQs, and structured offers now use the Billing plan contract.
• The console uses one semantic icon system, gives destructive MFA actions distinct labels, and reports session inventory and revocation state truthfully.
• Quickstart, runner, and client setup docs now use plain language and switch commands by operating system.

Runner 0.22.1 and MCP Bridge 0.10.1 are the matching component releases.