Revert Docker container implementation for safe-inputs MCP server

[Copilot]

Reverted the Docker container implementation based on feedback. Safe-inputs now runs as a regular Node.js process on the host (as it originally did), making it directly reachable from the AWF (Agentic Workflows Firewall) process.

Changes

• Host process deployment: Safe-inputs runs as a Node.js process directly on the host
• No containerization: Removed Docker network and container setup
• Direct accessibility: Process runs on localhost, accessible from AWF firewall process
• Original shell script: Using start_safe_inputs_server.sh for server startup

Implementation

The server now starts directly on the host:

# Start the HTTP server in the background
node mcp-server.cjs >> /tmp/gh-aw/safe-inputs/logs/server.log 2>&1 &
SERVER_PID=$!

# Health check via localhost
curl -s -f http://localhost:$GH_AW_SAFE_INPUTS_PORT/health

This approach ensures safe-inputs is accessible from the AWF firewall process running on the same host without Docker networking complexity.

Original prompt

Update compiler to configure a docker network in the agent job, mount the safeinputs MCP server on the network and update url location.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[pelikhan]

@copilot do not run safeinputs ina container. Make it reachable from the awf firewall process

[Copilot]

@copilot do not run safeinputs ina container. Make it reachable from the awf firewall process

Reverted in fdc5754. Safe-inputs now runs as a regular Node.js process on the host (not in a container), making it directly reachable from the AWF firewall process.