Audit and port missing gateway.py functionality

[james-in-a-box]

Summary

The egg gateway/gateway.py (2209 lines) is approximately 533 lines shorter than the jib gateway-sidecar/gateway.py (2742 lines). This difference suggests missing functionality that may be needed for a complete standalone sandbox.

Current State

Component	jib (lines)	egg (lines)	Difference
gateway.py	2742	2209	-533 (19% less)

Investigation Required

Compare the two files to identify:

1. Missing API endpoints - Are all required endpoints present?
2. Missing policy enforcement - Branch ownership, merge blocking, etc.
3. Missing health check details - Full status reporting
4. Missing session management features - Container lifecycle handling
5. Missing worktree operations - Full worktree management
6. Missing git operations - Any git commands not supported

Key Features to Verify

From jib's gateway.py:

• Git push with branch ownership policy
• Git fetch/pull operations
• Git remote operations (read-only)
• GitHub PR create/comment/edit/close
• GitHub merge blocking
• Session token validation
• Container registration/lifecycle
• Health endpoint with detailed status
• Rate limiting integration
• Audit logging

Files to Compare

• james-in-a-box/gateway-sidecar/gateway.py
• egg/gateway/gateway.py

Acceptance Criteria

• Complete audit of gateway.py differences
• Document any intentionally omitted features
• Port any missing essential functionality
• Ensure all security policies are enforced

Authored-by: jib