Separate non-production events so one inbox stays trustworthy
Staging and local errors mixed into the production inbox, separated so the production one can be trusted.
The ticket
Route non-production error events away from the production inbox.
Acceptance criteria
- Every event carries an environment tag
- Production filters to production only
- Local development does not report at all by default
- Each environment is verified with a seeded event
What lands as proof
A seeded event from each environment, landing where it should and nowhere else.
Why teams defer it
- Mixed environments make the inbox useless, and an inbox nobody trusts is one nobody reads.
- Nobody notices until a staging error causes a production page.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: route non-production error events away from the production inbox. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means environment stamped on every event, each inbox verified separately, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.