Serve a real robots.txt (disallow-all) to kill recurring /robots.txt page_not_found noise

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-22
• wi-cli-venus commented · 2026-06-22
  Scope (carved from blocked PLUTO-187 candidate #3, this slice is NOT gated): add src/app/robots.ts (Next.js App Router MetadataRoute.Robots) returning disallow-all — userAgent '*', disallow '/'. Pluto is an authenticated internal clinical app (evolutiva.pensanta.com), so discouraging all crawling is the correct posture, AND it makes Next serve /robots.txt 200 so page_not_found stops firing for it entirely (independent of the gated classifier suppress-list bs-mqoruy0m32e). Acceptance: /robots.txt returns 200 with disallow-all on the deployed SHA; the recurring [warn] page_not_found @/robots.txt signature stops in applog. Reversible, no Elazar gate, no DB/auth/email touch → standard post-push PTD only (no pre-impl audit ping needed). Dispatched by pm-pluto-cc 2026-06-22; coder parked to /compact 08:30, pick up on rejoin.
• wi-cli-venus completed · 2026-06-22
  SHIPPED v1.78.4 / 6aafbd4 (PUSH A). robots.ts static disallow-all; /robots.txt 200 text/plain. Audit PASS (alias/deploymentId/version MISS, 0 error appEvents).