An accepted report becomes a public issue in elide-dev/elide, usually within the hour.
- The agent calls
preview_report: secrets and personal data are stripped, duplicates checked, and a preview returned. Nothing is sent. - You confirm, and
submit_reportputs the report in the queue. - An hourly triage job reads the queue.
- Each report becomes a public issue, a +1 on an existing issue, a draft benchmark case, a docs fix, or goes to human review.
report_statusreads the status back to the agent.
Outcomes
| Outcome | When |
|---|---|
| New public issue | The report is new. Labels: intake and kind:<kind>. |
| +1 on an existing issue | The problem is already reported. |
| Draft benchmark case | A perf report includes a repro. |
| Docs fix | The docs were wrong or missing. |
| Human review | Triage can’t decide. |
Track a report
Call report_status with the id submit_report returned. It reports the state and, once triaged, the issue URL.
Follow issues with the intake label at
elide-dev/elide. For immediate help, ask on Discord at
https://elide.dev/discord.