An admin reads the last 20 refused first asks on /forges/refused #11589

An admin can now read the last 20 refused first asks at GET /forges/refused. Nothing links to it yet, so for now an admin has to type the path. The 5 tests in test/forges-refused.test.ts pass, as do tsc, design-lint, scripts/gate.ts and the hollow, check-list, and hollow-cli tests. I have not run the full suite, and I did not boot the app and curl the page.

• The page: src/web/pages/forges-refused.ts makes one listRefusals call for the newest 20 rows. Each row shows the time, the actor id (or "no one signed in"), the ask as escaped text, and the refusal's words. An empty list is one quiet line. The rows hold no email or claim code, so none can appear.
• The gate: a non-admin or signed-out visitor gets exactly what /forges gives them, which is the not-found page. The test compares the two responses directly.
• The route: one router.add line in src/http/server.ts, placed right after /forges and before the /forges/:name routes.
• The tests: the file covers the 20-row cap and ordering, the empty case, the non-admin comparison, <script> rendering as text, and no email or claim code in the output. scripts/gate.ts picks the test up by itself.
• Hollow audit: scripts/hollow.ts flags any screen that no page links to. I listed GET /forges/refused in scripts/hollow-allow.ts under #11587, which adds the link from /forges. That pull removes the entry. I left forges.ts and the docs alone, as the issue said.
• Push: the pre-push hook wanted a "Try:" commit message, so there is an empty commit for it.

To try it, sign in as an admin and open /forges/refused. Rows exist only after a stranger's first ask has been refused.

Closes #11586

An admin can now read the last 20 refused first asks at GET /forges/refused. Nothing links to it yet, so for now an admin has to type the path. The 5 tests in test/forges-refused.test.ts pass, as do tsc, design-lint, scripts/gate.ts and the hollow, check-list, and hollow-cli tests. I have not run the full suite, and I did not boot the app and curl the page.

• The page: src/web/pages/forges-refused.ts makes one listRefusals call for the newest 20 rows. Each row shows the time, the actor id (or "no one signed in"), the ask as escaped text, and the refusal's words. An empty list is one quiet line. The rows hold no email or claim code, so none can appear.
• The gate: a non-admin or signed-out visitor gets exactly what /forges gives them, which is the not-found page. The test compares the two responses directly.
• The route: one router.add line in src/http/server.ts, placed right after /forges and before the /forges/:name routes.
• The tests: the file covers the 20-row cap and ordering, the empty case, the non-admin comparison, <script> rendering as text, and no email or claim code in the output. scripts/gate.ts picks the test up by itself.
• Hollow audit: scripts/hollow.ts flags any screen that no page links to. I listed GET /forges/refused in scripts/hollow-allow.ts under #11587, which adds the link from /forges. That pull removes the entry. I left forges.ts and the docs alone, as the issue said.
• Push: the pre-push hook wanted a "Try:" commit message, so there is an empty commit for it.

To try it, sign in as an admin and open /forges/refused. Rows exist only after a stranger's first ask has been refused.

The preview is up: / and /healthz return 200, and /forges/refused returns 404 for an anonymous visitor. The 404 is the designed answer, since non-admins get what /forges gives them.

I changed nothing and pushed nothing. The log shows the app started, passed readiness and reported done. The words "no tests declared, none run" describe the preview step, not a failure in my change. forge.json has no app.test entry, so no preview of any pull runs tests. The same file is on main and is outside this issue's files, so I left it alone.

The checks that do cover this change passed before the push: tsc, scripts/gate.ts, design-lint, hollow, and test/forges-refused.test.ts with 5 tests. The forge's own check runs on each push, and I haven't seen a verdict from it. If the "failed" mark comes from the preview requiring a declared test command, that is a forge.json decision for a person. Please send me that log if it points somewhere else.