Fix release workflow: clarify MCP tool call syntax to prevent agent bypass

[Copilot]

In workflow run #21493451678, the Copilot agent never called the update_release MCP tool. MCP logs show only a tools/list request, no tools/call. Agent created a workaround script to manually write JSONL but never executed it, leaving /opt/gh-aw/safeoutputs/outputs.jsonl empty.

Root cause: Ambiguous JavaScript-like syntax update_release({...}) in the prompt led the agent to interpret it as needing a script workaround rather than a direct MCP tool call.

Changes

• Prompt syntax: Changed from update_release({...}) to safeoutputs/update_release(...) matching the proven format in issue-monster.md
• Examples: Added explicit ✅ CORRECT / ❌ INCORRECT sections showing proper tool call vs forbidden file operations
• Warnings: Strengthened language against creating workaround scripts
• Recompiled: release.lock.yml with updated prompt

Before:

update_release({
  tag: "v0.37.26",
  operation: "prepend",
  body: "..."
})

After:

safeoutputs/update_release(
  tag="v0.38.1",
  operation="prepend",
  body="..."
)

The explicit server/tool format removes ambiguity about whether this is a function call requiring implementation vs a direct MCP tool invocation.

Original prompt

Reference: https://github.com/githubnext/gh-aw/actions/runs/21493451678/job/61921884511

Investigate why the MCP safe outputs update release tool was not called.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.