v2.7.0

Sync to Forge plugin v2.7.0.

Changed

• A documents step can save its approved document into the repository. When a step that writes documents routes an approved document into your repository, the agent may create or update that one document with apply_patch or an editor write, following the layout of the documents around it. It does not edit application code or configuration, and it does not commit, push or open a pull request to deliver it. A pointer on the ticket still needs the step's own tracker permission.
• Code-editing permission is described as covering application code and other repository edits beyond that single document.

Fixed

• A blocked question tool no longer rules out the other one. The skills now check each question route on its own: in Default mode, a blocking picker that is limited to Plan mode does not stop the agent from using the async picker, and an unexplained form rejection is not treated as a denial of every route. An explicit policy that forbids the question everywhere still applies, and numbered choices remain the fallback.

The repository-document guidance takes effect once the matching Forge server update is live; until then, behaviour is unchanged.

Diff: #53