fix(compile): trust generated SafeOutputs MCP for Copilot

[Copilot]

Summary

Copilot CLI requires compiler-generated MCP servers to be explicitly trusted and allowed, even when the workflow uses wildcard tool access. Without that, generated SafeOutputs MCP access depends on non-source lock-file edits.

• Copilot MCP config

  • Marks generated MCPG server entries as default/trusted:

    .value.tools = ["*"] | .value.isDefaultServer = true

• Copilot permissions

  • Preserves compiler-owned extension grants on the --allow-all-tools path.
  • Generated invocations now include:

    --allow-all-tools --allow-tool safeoutputs

• Coverage

  • Pins wildcard/default Copilot args to include --allow-tool safeoutputs.
  • Pins MCPG-to-Copilot conversion to emit isDefaultServer: true.

Test plan

• cargo build
• cargo test
• cargo clippy --all-targets --all-features
• Manual compile of a SafeOutputs workflow and inspection of generated lock YAML

[jamesadevine]

@copilot Merge main and ensure the new copilot/ safeoutputs contract test succeeds.

[Copilot]

@copilot Merge main and ensure the new copilot/ safeoutputs contract test succeeds.

Merged origin/main in bfdb795 and enabled/validated the Copilot SafeOutputs contract checks in 4ef7b9a (latest cleanup a46d0a0). cargo test --test copilot_cli_safeoutputs_tests passes locally.

[jamesadevine]

@copilot Restore ignore in the tests.

[Copilot]

@copilot Restore ignore in the tests.

Restored the ignored markers for the Copilot SafeOutputs tests in 8417509. cargo test --test copilot_cli_safeoutputs_tests now reports all three tests ignored by default.