StackJack 0.1.0.6281+a828c00

This release adds a protected mode for tenants that are being moved to a new hosting region. During a move, the portal stays readable, actions that would change data are declined with a clear explanation instead of failing confusingly or silently, and connectors, team memberships and billing state arrive intact on the tenant's new home.

New features

• Protected mode during a hosting-region move. While your tenant is being migrated, you can still view your connectors and settings, but changes that could be lost or leave your account in an inconsistent state are declined with a consistent message explaining that the tenant is being moved. This covers adding, editing or removing connector credentials, connecting a connector through its sign-in flow, changing or removing your own Anthropic API key, starting a checkout or buying a credit pack, cancelling or reactivating a subscription, opening the billing management page, and approving a new application's access to your tenant. Agent requests to the MCP endpoint and token issuance are also declined during the window rather than being run against data that is about to move.

Improvements

• Test connection now reports when a test was declined because of a move, rather than marking a healthy connector as failed and suggesting you fix credentials that are fine.
• The connector configure dialog explains once, when opened during a move, why stored values cannot be shown, instead of leaving every field blank and reporting each section as unavailable.
• Removing your Anthropic API key during a move shows the correct explanation rather than a generic "try again or contact support" message.

Bug fixes

• Agents renewing their access during a move no longer have their long-lived sessions invalidated. Previously a renewal attempted in the window could force every agent connection on the tenant to sign in again afterwards; renewals are now declined without side effects and resume working once the move completes.
• Team members who signed in during a move could lose their membership or a pending invitation. Sign-in during the window is now declined before anything is recorded, so memberships and invites are preserved.
• Cancelling a legacy connector subscription during a move could be silently reverted once the move completed, leaving the subscription active again. The cancellation is now declined during the window instead.
• Starting a connector's sign-in flow during a move no longer creates or reactivates a connector subscription before the request is declined.
• Connectors whose vendors rotate a credential on every use could be left broken after a move: a request during the window reached the vendor and rotated the credential, which then could not be saved. Credential use is now declined before the vendor is contacted, so the connector keeps working on the new home.