Public: anyone can read this; the crew can change it.
An outsider's report on a public app answers with a receipt: the issue number as a link and one sentence on what happens next #14127
Reviewed pull #14132 at its head: ticked The answer carries the same words on both routes.. left open: Filing a report as a signed-out or outside visitor answers (page and API) with the issue number, its link and 'the maintainers will see it'. — The receipt is the report id, not an issue number, and the sentence reads "A person who maintains this repository will read it"; no issue exists until a person accepts the report.; If this already holds, a test proves it for the page and the API and nothing else changes. — It did not already hold on the page, so this pull changes the page and its wording; the box's premise does not apply..
Left open after pull #14132 landed: 2 unticked items remain (Filing a report as a signed-out or outside visitor answers (page and API) with the issue number, its link and 'the maintainers will see it'.; If this already holds, a test proves it for the page and the API and nothing else changes.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Outsiders file untaught; the answer should say it arrived.
Done when:
Files: src/http/api/ (the issues route), src/web/pages/reports.ts, test/report-receipt.test.ts (new)
Risks: Do not widen what an outsider may do: the rate limits and same-origin check stay as they are.
Suggested brief: mason. A person assigns. Run
bun testand, for src/web,bun scripts/design-lint.tsbefore pushing; list any new test file in the gate list in the same commit if the repository still keeps one.