Contribution outcome tracking

[sajeetharan]

Problem

Public GitHub events are not connected to mission previews and explicit attribution, making it difficult to understand whether a developer action led to an issue, PR, or merged contribution. The history also lacks a clear privacy-safe funnel across contribution outcomes.

Proposed solution

Track public GitHub contribution outcomes by linking mission previews to issue or PR opened and merged events with explicit attribution. Aggregate the funnel in a privacy-safe way and ensure the workflow extends the existing #201 integration without exposing sensitive identity details.

Acceptance criteria

• Link mission preview to public GitHub issue or PR events.
• Capture opened and merged outcomes with explicit attribution.
• Aggregate privacy-safe funnel metrics.
• Support attribution and event review for public records.
• Documentation for data sources and interpretation.
• Extend existing work from Agent analytics: measure privacy-safe MCP adoption and outcomes #201 with clear contract and privacy boundaries.

Privacy and trust

Only public GitHub event data should be used, and all reporting must be aggregate and privacy-safe. Public attribution should be explicit and optional rather than inferred from private activity.

Dependencies

• Existing Agent analytics: measure privacy-safe MCP adoption and outcomes #201 contribution tracking model.
• Public GitHub event ingestion and attribution logic.
• Mission preview and funnel telemetry.