StackJack 0.1.0.4720+39b81f6

This release introduces per-connector MCP endpoint URLs in the Portal, pins template installs to the version you actually reviewed, and tightens what the CIPP and HaloPSA write tools will accept and how honestly they report the result of a write.

New features

• Per-connector MCP endpoints. The Endpoints page and the onboarding wizard can now list a separate MCP URL for each connected system, so a client can be pointed at one connector instead of your whole tool catalog. The list appears only where these endpoints are available for your organization; if you do not see it, nothing is broken.
• Template installs are pinned to the version you reviewed. If a template is republished between the moment you review it and the moment you install, the install now stops with a clear conflict message instead of quietly installing different content — a different prompt, model, credit cost or trigger than the one you consented to.

Improvements

• Several CIPP write tools (mailbox forwarding, mailbox restore, scheduled items) now refuse a call when a value passed through the free-form additional-fields parameter disagrees with the same value passed as a typed parameter — for example the tenant or the target of the operation. Previously the free-form value silently replaced it.
• Those refusal messages no longer imply that the call was aimed at a completely different record when the only difference was letter casing. The call is still refused, but the wording no longer sends you looking for something that does not exist.
• HaloPSA ticket updates: when StackJack could not read the ticket before writing, a response that merely echoes the stored value is now reported as unverified rather than as a confirmed change. The same response shape can mean the write was ignored, and the tool no longer guesses.
• HaloPSA quotation line updates: retry guidance is now scoped to the edits it was actually proven for, with properties the read-back could not check called out separately. The tool description now names all four failure cases instead of three.
• The deprecated raw-JSON parameter on the scheduled-item tool is now clearly marked as deprecated and never read, and points to the correct parameter to use. Its behavior is unchanged — values sent there are still refused.
• Product documentation now covers per-connector endpoints and explains which URL parameters actually narrow the tools a client sees and which have no effect.

Bug fixes

• Scheduled-item re-runs were incorrectly refused when the call also carried parameters that CIPP ignores. Those inert parameters no longer block the documented two-call workflow.
• Per-connector endpoint URLs are now taken from the hostname each connector actually published, rather than recomposed from current settings, so the URL you are shown is always the one that is live.
• In the onboarding wizard, a failure to load the connector endpoint list also (incorrectly) reported that catalog modes were not enabled for your organization and disabled the copy button on a URL that worked. The two are now independent.
• The endpoint list and the page that hosts it now agree on when a subscription counts as active, so a deactivated subscription withdraws its connector URL consistently on both surfaces.
• New agents created from an older template no longer carry tools that have since been removed from the platform.

UI & UX changes

• The template install step no longer tells you that you can install a template whose tools are not all available — that install is refused. It now shows one sentence per reason (connector not enabled, plan does not include the tool, tool not available on the platform) with only the tools affected by that reason, so a message about one connector can no longer point at tools from another.
• The onboarding wizard's compact endpoint row now states the same catalog-mode prerequisite the Endpoints card has always stated, and keeps copy disabled until your organization opts in, instead of promising a folded catalog that would not be served.