Update test-proxy.md to use comments instead of creating issues

Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>

Author: Copilot

.github/workflows/test-proxy.lock.yml

@@ -4,8 +4,8 @@ on:
     branches: [ "main" ]
   workflow_dispatch:
 
-permissions:
-  issues: write # needed to write the output report to an issue
+output:
+  issue_comment: {}
 
 tools:
   fetch:
@@ -21,7 +21,6 @@ tools:
 
   github:
     allowed:
-      - "create_issue"
       - "create_comment"
       - "get_issue"
 
@@ -44,10 +43,16 @@ Test the MCP network permissions feature to validate that domain restrictions ar
 - Verify that all blocked requests fail at the network level (proxy enforcement)
 - Confirm that only example.com is accessible through the Squid proxy
 
-Create a GitHub issue with the test results, documenting:
-- Which domains were successfully accessed vs blocked
-- Error messages received for blocked domains  
-- Confirmation that network isolation is working correctly
-- Any security observations or recommendations
+## Reporting Instructions
+
+If the test runs successfully and network isolation is working correctly:
+- Write a brief summary to ${{ env.GITHUB_AW_OUTPUT }} confirming the test passed
+
+If there are any failures, security issues, or unexpected behaviors:
+- Write a detailed report to ${{ env.GITHUB_AW_OUTPUT }} documenting:
+  - Which domains were successfully accessed vs blocked
+  - Error messages received for blocked domains  
+  - Any security observations or recommendations
+  - Specific failure details that need attention
 
 The test should demonstrate that MCP containers are properly isolated and can only access explicitly allowed domains through the network proxy.