v2.6.0

Sync to Forge plugin v2.6.0.

Added

• Large workflow catalogs are read in full before Forge says nothing fits. When the list of workflows is too long for one reply, Forge sends it in pages or with shortened entries, and the routing skill tells the agent how to read the rest: the remaining pages, or the full detail of a few workflows. If a reply arrives cut short, the agent reads the catalog again before it reports that no workflow covers a request or offers to build one.

Changed

• Forge's questions use the host's own question controls when they are compatible and permitted. The routing, workflow-authoring and feedback skills now give one rule for asking: use a native control that fits the question, keep every choice, and show numbered choices when no such control can be used. On Claude Code this is still the built-in question tool.
• Saving or deleting a workflow, and sending feedback, follow only an explicit answer. The skills show the complete proposal or payload before they ask, act only on an explicit confirmation of what was shown, and ask again when it changes. A preselected default never counts as a yes.

Fixed

• A question that was only delivered, or a question call that failed, no longer counts as the user having been asked. Forge refuses an answer to one of its questions unless the question reached the user first, so an answer cannot be posted on their behalf. On Claude Code the built-in question tool already waits for the answer, so nothing changes in practice.

Reading large catalogs in pages needs the matching Forge server update; until it is live, behaviour is unchanged.

Diff: #38