v2.8.0

Sync to Forge plugin v2.8.0.

Changed

• "Keep a record?" is asked at most once a session. After you decline it, Forge doesn't offer it again later in the same session. You can still ask Forge to track the session yourself, and the next session asks afresh. A snooze you chose ("remind me later") still comes back.
• Helper agents keep working while Forge waits for your answer. While a Forge question is open, an agent the main conversation started can still read, search and run checks. Its writes stay held until you answer, as the main conversation's are.
• Workflows you author no longer need a closing feedback step. Every run's recap already says how to send feedback, so the authoring skill doesn't add one. A baseline that has one keeps it unless you ask to drop it.
• Removing an org's workflow configuration says what really happens. Most built-in workflows stop running when their org configuration is removed, but a built-in that ships switched on keeps running, and the authoring skill now says so. A configuration that only switches a workflow on, renames it or limits who sees it is no longer treated as a broken override.
• The routing skill names GPT-6.1 Terra for balanced Codex steps, in its model-routing example.

Added

• README: how to have Claude Code ask before destructive commands. A settings snippet with ask rules for commands that are hard to take back, such as git push, git reset --hard and rm -rf. It only adds a confirmation; nothing is blocked.

Fixed

• A workflow started in the middle of another no longer strands the first one. The earlier run is held while the new one runs, with its own question and write lock, and it comes back when the new one ends. Previously it was refused until it was recovered.

Diff: #40