StackJack 0.1.0.9347+aba8fc4

This release adds keyless sign-in and several new management controls for Azure Foundry connections. Personal sign-ins and member keys are more reliable, and support-ticket files are now deleted when a ticket is closed. It also adds a way to cancel paused runs and fixes a number of misleading status messages.

New features

• Keyless sign-in for Azure Foundry. StackJack can now reach your Foundry account through the StackJack Foundry Runner instead of a stored key. Turnkey setup uses keyless sign-in by default where the runner is already allowed in the chosen subscription's directory. The Foundry tab adds:
• Switch to keyless sign-in for an existing connection
• Attach an existing Foundry account without a key
• Narrow StackJack's access to a minimal role
• StackJack Foundry Runner consent. The Foundry tab shows a runner card where an owner or administrator can allow the runner once for a directory. The card explains what allowing it does and how to take it away.
• Scheduled key rotation. Stored-key Foundry connections can let StackJack rotate the key on a schedule. Automatic rotation stops after repeated failures, and you get an email for each rotation outcome.
• Azure cost card. A Foundry connection can show its daily Azure cost next to StackJack's estimate.
• Run StackJack's AI help on your Azure Foundry. A new option on the Foundry tab runs AI help on your own Foundry. When it is on, the builder's cost line says when a turn ran there.
• Full teardown of a Foundry connection. Removing a connection can also remove the Azure resources StackJack created, with a preview of what will be deleted and what stays.
• Revoke my key. Team members can now revoke their own personal StackJack key from their personal sign-in card, after a confirmation.
• Cancel a paused run. Paused Managed Agents runs and paused Foundry runs now offer Cancel run. A confirmation explains that the run stops right away and is charged for what it already used.

Improvements

• Ticket files are deleted on close. Closing a support ticket now deletes the files attached to it. Deleting an organization deletes every support-ticket file StackJack stores for it.
• Re-authorizing keeps your key. Re-authorizing or reconnecting a personal sign-in now keeps your existing StackJack key. You no longer get a new key that has to be swapped into your AI tools. The one-time key page appears only on your first personal sign-in for a connection.
• Kept keys stay current. When a personal sign-in renews, the key it keeps is updated to your current tools.
• Member keys follow role changes consistently. A member's personal keys now update their tool list when you:
• Edit their tools
• Assign, remove, edit or delete a role
• Run a directory sync
• Transfer a role through an invite
• Demote a co-owner
• Removing a Foundry connection can be retried by someone else. If another owner or administrator presses Retry on a stopped Foundry operation, the operation now continues under that person's Azure sign-in.

Bug fixes

• Personal sign-in cards now show real problems. Cards no longer say "Connected" while the sign-in is failing:
• HaloPSA and NinjaOne: a failing sign-in shows Re-authorize Required.
• Microsoft Azure and Microsoft Graph: a refused sign-in shows Re-authorize Required, or Administrator Action Required when only an administrator can fix it.
• N-central: a rejected token shows Token Refused.
• Unreachable services: these show Can't reach it.
• Health and session checks report expired personal sign-ins. Both checks now say when a personal sign-in needs to be re-authorized, instead of reporting a generic connector problem.
• Move memory no longer archives unread memories. If Move memory cannot read the full source, it now stops with a message instead of archiving memories it never read.
• Failed Foundry attaches stay visible. A failed attach now stays on the Foundry tab after a reload, with its reason and a Retry button. Previously you had to remove the connection and start over.
• "Grant cost access again" now repairs the access. If the cost-reading access was deleted in Azure, the button now restores it. Previously it reported success without fixing anything.
• Allow returns when the runner is removed. If the StackJack Foundry Runner is removed from your directory, the Foundry tab now offers Allow again instead of showing the runner as still allowed.
• Accurate Disconnect confirmation. The Disconnect confirmation for a Foundry connection now correctly says whether StackJack's key will stay valid.
• Your Marketplace subscriptions are protected. A full Foundry teardown no longer deletes a resource group that contains one of your own Azure Marketplace subscriptions. The group is kept, and the preview and receipt name the item.
• AI help stops after Disconnect. AI help now stops calling your Azure Foundry as soon as the connection is disconnected, even partway through a turn.
• No false failed checks during changes. Keyless Foundry connections that are being disconnected or re-granted no longer get a failed status from the daily check.
• Stop buttons report refusals. If a run cannot be stopped, the run page now says why and reloads the run's real status, instead of always reporting success.
• Stops that lose to other updates still work. A stop request that conflicted with another update to the run now retries instead of reporting success while the run kept going.

UI & UX changes

• Full names in the tool picker. The tool picker's left-hand list now shows every connector and category name in full, and widens in wide dialogs.
• Correct buttons in messages. Messages, emails and setup guides now name the buttons and pages that actually exist:
• Your personal sign-ins instead of the retired My Connectors page
• Update credentials for shared HaloPSA connections
• Remove connection on the Foundry page
• Test and Re-test in the Avanan outage warning
• Messages match each reader's permissions. Foundry messages now name a button only to people who can see it. Other team members get a plain description of the state.
• Clearer re-authorize emails. These emails now link straight to the Connectors page and name the exact card to use. They also explain what to do with an old personal sign-in card.
• Microsoft connectors named in full. Both connector lists in the personal sign-ins section now name Microsoft Azure and Microsoft Graph.

Fixed customer-reported issues

• A HaloPSA personal sign-in kept failing on live calls while the portal still showed it as connected, even after repeated re-authorization (01M3Q6ZKKGYKYZE9WCDR1HKAA1). The personal card now shows Re-authorize Required when the sign-in is failing. Error messages tell you to re-authorize that specific personal sign-in, and re-authorizing keeps your existing StackJack key.