A report's receipt
An outsider files a report on a public repository without an account and is handed a receipt they can read back. A report is not an issue until a person accepts it, so the receipt says so rather than guessing a number.
Fields (same from every door): id, state (pending), filedBy, issue (null — "none yet"), url, message,
next. The url is built on the forge's configured public URL (never a Host header the client wrote) and shows,
signed out, the report's title and whether a person has read it and which issue it became; the issue number
appears there once the report is accepted.
- JSON:
POST /api/v1/repos/:owner/:name/reportsanswers 202 with the receipt. - Plain text: the same request with
Accept: text/plainanswersreport:,issue: none yet,url:,state:
lines, then the message and the next step.
- MCP: the
reporttool returns the receipt as its JSON text. - Web: after the form,
/:owner/:name/report?sent=<id>shows Title and State rows.
The terminal (both doors): signed-in people have no outsider receipt; the repository palette's "Report a problem"
opens an issue at once, and its toast now reads back the issue's number and path (Issue #7 opened: /owner/name/issues/7).
Try it: curl -s -XPOST -H 'content-type: application/json' -d '{"title":"x"}' $FORGE_URL/api/v1/repos/alice/game/reports,
then open the url it returns.
Pinned by test/report-receipt.test.ts and test/report-words.test.ts.
The day
A report is read, and accepted or dismissed, within a day (ANSWER_WITHIN_MS, core/reports.ts). The receipt page
says when the answer is due, says plainly when that day has passed, and after a decision shows when it was answered.
The keepers' list, on the web and in the terminal, marks a report "past its day" (oldest first, as before, so those are first). Nothing is closed on a person's behalf.
Pinned by test/report-clock.test.ts.