StackJack 0.1.0.6995+1d02e82

This release focuses on HaloPSA: item creation now applies pricing and stock fields correctly, and permission errors give clearer instructions on how to re-authorize. It also fixes several problems in the onboarding wizard and the MCP Setup page, and updates the connector documentation for HaloPSA, Copilot Studio, PRTG and ThreatLocker.

Improvements

• When a HaloPSA tool is refused because the connection lacks a permission, the error guidance is now more specific. Item-related tools (including item links, bins and suppliers) name the permission that is missing, and every permission error explains how to re-authorize. For connections that use personal sign-ins, the guidance now points to reconnecting your own sign-in, since re-saving the shared connection does not renew an individual member's access.
• Connector documentation updates:
• The HaloPSA troubleshooting guide now includes the re-authorize step for permission errors.
• The Copilot Studio guide has a new section on several people using one tool.
• The PRTG troubleshooting guide now explains that a valid API key can be rejected when the PRTG core has not enabled the new UI and API v2, not only when the key has been deleted. A broken link in that guide has also been repaired.
• The ThreatLocker connector page now explains how to request the outbound addresses needed for allowlisting, consistent with the other connector pages that require allowlisting.

Bug fixes

• Creating an item in HaloPSA via halo_create_item now correctly sets the item's price, cost and stock-tracking values. Previously these were sent under field names that HaloPSA ignores, so they were silently dropped.
• The onboarding checklist now recognizes a Microsoft 365 Copilot organization connector as an MCP connection. Previously tenants using that connector were shown as not yet connected.
• The onboarding wizard no longer loops endlessly when the AI step cannot be completed; it now closes instead.
• On the MCP Setup page, the role-assignment dialog now opens reliably. Previously it only worked when the Rotate API Key option was also visible.

UI & UX changes

• Step 1 of the onboarding wizard now explains when the wizard is able to detect the Copilot connector and points to the check-now button for re-checking. Pressing Next from the Add Connector step now moves through the wizard instead of closing it.

Fixed customer-reported issues

• PRTG connector rejecting a valid API key with an authorization error 01M2EXQS545ZJ5CCSY15GQ35CC: the PRTG troubleshooting guide now documents the cause (the PRTG core has not activated the new UI and API v2) alongside the existing deleted-key case.