StackJack 0.1.0.6312+a17c9f6

This release adds document downloads for ConnectWise Manage, a new HaloPSA tool for removing quotation lines, filters for the CIPP OAuth app listing, and a tool catalog that shows only what your organization can actually use. It also rebuilds the HaloPSA sales order line update so edits reliably persist, and fixes an intermittent failure in postcondition checks.

New features

• ConnectWise Manage: download ticket and system documents. A new cw_download_document tool retrieves the actual contents of a document (for example an email file or header dump attached to a ticket), where previously only document metadata could be listed. The tool returns a short-lived download link rather than embedding the file in the response. Downloads are limited to 16 MB and a three-minute transfer window; the filename is taken from the vendor response, falling back to the document's metadata.
• HaloPSA: remove specific quotation lines. A new halo_remove_quotation_lines tool removes the lines you name from a quotation while leaving every other line exactly as it was. If any named line is not on the quote, the tool refuses before making any change, and after the write it confirms that the named lines are gone and all other lines survived.
• CIPP: filter the OAuth app listing. cipp_list_oauth_apps now accepts an optional nameFilter (case-insensitive substring match on the app name) and appId (case-insensitive exact match on either the application ID or the object ID). When both are supplied, a row must match both. With neither supplied the response is unchanged.

Improvements

• Tool catalog is scoped to your organization and caller. stackjack_get_tool_catalog now lists only the connectors your organization is subscribed to and has configured, and within each connector only the tools your plan tier and access grants allow. Connectors you do not have are omitted rather than shown as unsubscribed, and a connector with no usable tools is dropped instead of appearing empty. The connector and per-plan totals are scoped to match. Each connector entry also gains a configured flag.
• HaloPSA sales order line update rebuilt. halo_update_sales_order_lines no longer relies on a vendor endpoint that does not accept the request. It now reads the order, applies your edits to the full existing line set, writes the complete set back, and returns the order as read back afterwards. The write is reported as unverified if a previously existing line disappeared, if a protected header field changed, or if an edited field does not hold the submitted value.
• HaloPSA sales order field guidance corrected. The descriptions for halo_create_sales_order and halo_update_sales_order_lines now reflect verified behavior: quantity is writable, price drives the line total, unit_price is not a valid field, and user_id is required on create. halo_create_sales_order now refuses a payload that carries an existing line ID.
• Tool reference layout. halo_update_sales_order_lines is now listed under the Sales Orders group in the HaloPSA tool reference, alongside the create and get tools.

Bug fixes

• Postcondition pattern checks could intermittently report a mismatch and fail a step on the first evaluation after a deployment, even when the value matched the pattern. The evaluation time limit was too tight for a cold start and has been raised; a genuinely runaway pattern is still treated as a mismatch, never a pass.
• HaloPSA instances that return line IDs as strings rather than numbers caused sales order line updates to succeed but be reported as unverified, with every subsequent call on that order failing the same way. Both ID formats are now handled consistently.
• Reading a HaloPSA sales order now always includes its line details, so line updates no longer fail because the line collection was missing from the fetched order.
• A HaloPSA sales order write that succeeds but returns an empty response is no longer reported as a transport failure.
• Subscribed but unconfigured connectors were previously shown in the tool catalog as available. They are now omitted until configured.

Breaking changes

• stackjack_get_tool_catalog no longer returns the full product catalog with a per-connector subscribed flag. Connectors your organization does not have, and tools outside your plan or access grants, are omitted entirely, and the totals are scoped accordingly. Requesting a connector you do not have returns the same unknown-connector response as requesting a connector that does not exist. Any automation that depended on seeing the full catalog should be reviewed.