chore: claw-code progress on #831

Refs #831

.claw/sessions/session-1775428982645-0.jsonl

@@ -0,0 +1,2 @@
+{"created_at_ms":1775428982645,"session_id":"session-1775428982645-0","type":"session_meta","updated_at_ms":1775428982645,"version":1}
+{"message":{"blocks":[{"text":"You are Code Claw running as the Gitea user claw-code.\n\nRepository: Timmy_Foundation/the-nexus\nIssue: #831 — [BUG] Missing robots.txt\nBranch: claw-code/issue-831\n\nRead the issue and recent comments, then implement the smallest correct change.\nYou are in a git repo checkout already.\n\nIssue body:\nThe production site `https://forge.alexanderwhitestone.com/` is missing a `robots.txt` file (404 Not Found). This is a best practice for SEO and crawler control.\n\nRecent comments:\n## Triage — Allegro\n\nThe missing `robots.txt` at `https://forge.alexanderwhitestone.com/robots.txt` is a **Gitea server-level issue**, not a `the-nexus` code defect.\n\nTo fix this, a `robots.txt` file needs to be placed in the Gitea static asset path (typically `/data/gitea/public/` inside the Gitea container or the equivalent host path) or served by the reverse proxy in front of Gitea.\n\n**Suggestion:** Move this issue to `timmy-config` or address it during the next Gitea server maintenance window.\n\nRerouting this small concrete issue to `claw-code` for the new dispatch lane. This is a bounded smoke-on-real-work handoff.\n\n🟠 Code Claw (OpenRouter qwen/qwen3.6-plus:free) picking up this issue via 15-minute heartbeat.\n\nTimestamp: 2026-04-05T22:42:59Z\n\nRules:\n- Make focused code/config/doc changes only if they directly address the issue.\n- Prefer the smallest proof-oriented fix.\n- Run relevant verification commands if obvious.\n- Do NOT create PRs yourself; the outer worker handles commit/push/PR.\n- If the task is too large or not code-fit, leave the tree unchanged.\n","type":"text"}],"role":"user"},"type":"message"}