bug: Forge Integration Service (forge-sync) – Complete Bidirectional Synchronization, Webhook Reliability, and Outbound Action Execution

[AnuragGupta181]

Short Summary

The current forge-sync implementation provides a strong foundation for GitHub/GitLab/Forgejo integrations, including inbound webhook processing, outbound actions, webhook management, and polling-based synchronization. However, several gaps currently prevent the service from functioning as a fully reliable bidirectional forge integration layer. This issue tracks the work required to complete the Forge Integration Service deliverable, improve webhook reliability, ensure inbound and outbound synchronization consistency, and establish a secure event-driven foundation for agent wakeups.

Steps to Reproduce

1. Connect a GitHub repository through the current forge integration flow.
2. Register a webhook through the project settings or CLI.
3. Trigger repository events such as:
   • Issue creation
   • Issue comments
   • Pull request creation
   • Pull request reviews

Expected Behavior

The Forge Integration Service should provide a complete bidirectional synchronization layer between GitMesh and supported forge providers.

Actual Behavior

GitHub webhook callback URL mismatch causing webhook delivery failures

Environment

GitMesh development environment

[AnuragGupta181]

Progress Update

Completed Investigation

• Reviewed current forge integration architecture
• Identified webhook routing mismatch
• Identified inbound webhook processing path
• Documented current limitations and roadmap

Completed Work

• Split inbound and management webhook routes
• Mounted inbound routes at /api/forge/webhook/*
• Updated forge webhook documentation
• Eliminated 404 failures for GitHub webhook deliveries

Current Status

Webhook requests now reach the inbound handler successfully.

During validation, a new issue was discovered:

• withResolvedProjectId() depends on __gitmesh_project_id
• Inbound webhook routes no longer provide this value
• Webhook processing currently fails during project resolution

Next Steps

• Fix project resolution using repository owner/repo lookup
• Continue Phase 1 inbound synchronization work