StackJack 0.1.0.8881+de643c0

This release helps agent runs get through busy periods at the AI provider, adds roadmap and feature-request commands to the StackJack Discord bot, and makes the portal more reliable and faster to load.

New features

• Scheduled and webhook runs wait out AI provider overloads. Previously, a webhook or scheduled agent run failed immediately if the AI provider refused to start it because it was overloaded. StackJack now holds the run and retries it automatically for up to two hours. Retries start one minute apart and back off to every 10 minutes. A scheduled run's waiting window is capped at half of its schedule interval. Interactive runs, such as Run now, still fail right away as before.
• A held run keeps its place and its credit reservation. If it never starts, it ends as failed.
• A webhook that triggers a held run gets an accepted response with the run's ID. If the sender retries the same event, the retry goes to that held run instead of creating a duplicate.
• You can cancel a held run at any time.
• Roadmap and feature requests in Discord. The StackJack Discord bot has two new commands:
• /roadmap looks up items on the public feature-request board. It shows each item's title, status, vote count and a link to vote.
• /feature submits a feature or connector request. If a matching request already exists, the bot links to it. Otherwise, it adds your request to the review queue.
• Requests for a new connector need a link to the vendor's API documentation or an attached specification.
• Each person can submit a limited number of requests per day.

Improvements

• Starting an agent session now retries automatically, a few times over a few seconds, when the AI provider reports that it is overloaded. Many runs that used to fail at launch will now start normally.
• When a ConnectWise request fails because of how the AI built the request, the error now says so. The agent no longer offers to draft a support ticket for these errors, since the fix is to correct the request.
• The EU data-region notice for Azure AI Foundry connections now covers every model StackJack deploys, not only Claude models. Organizations that already acknowledged the notice are not asked again.
• If the roadmap board is slow to respond, the Discord bot now quickly replies that it can't reach the roadmap instead of hanging.

Optimizations

• Portal stylesheets, scripts and connector logos can now be cached by your browser until they change. Repeat page loads make far fewer requests and load faster.

Bug fixes

• Fixed portal sessions in background browser tabs disconnecting and reconnecting about once a minute.
• Fixed pages sometimes appearing unstyled or unresponsive right after a StackJack update until you reloaded them.
• Fixed the reconnect message closing for good if you pressed Escape twice while disconnected, which left you on a page that was no longer live.

UI & UX changes

• A StackJack-styled card, in light and dark themes, now replaces the plain default box when the portal loses its connection:
• It shows when StackJack is reconnecting.
• It offers Retry and Reload buttons when StackJack can't be reached.
• It reloads the page automatically when your session has ended.
• Short connection blips no longer show it at all.
• Held runs appear as Waiting for the AI service in the run list. The run detail page shows the next retry time, when the waiting window ends, what happens to the reserved credits, and a Cancel button.
• The agent run status tool now reports that a held run is waiting for the AI service, instead of saying it is still running, and keeps checking on it.