docs(hackathon-analysis): verify, archive and merge specs (closes change 3)

[TOMOKI977]

Summary

Closes change 3, hackathon-analysis (roadmap change 3 of 4). This PR is documentation only and changes no code.

• Archive: openspec/changes/hackathon-analysis/ moves to openspec/changes/archive/2026-09-29-hackathon-analysis/. It was moved with git mv, so history and the full apply-progress.md are preserved. The archive adds:
  • verify-report.md: sdd-verify gave PASS WITH WARNINGS with 803 tests and a clean typecheck. A post-verify update records that the archive blockers are resolved.
  • archive-report.md.
  • The Phase 11 operator tasks 11.1–11.5, ticked with evidence.
  • A fix for a line in design.md that had a literal newline where \n belonged.
• Main specs: the change's delta specs are merged into new main specs:
  • openspec/specs/hackathon-analysis/spec.md (12 requirements)
  • openspec/specs/page-fetch/spec.md (7 requirements)
  • openspec/specs/llm-extraction/spec.md (6 requirements)

Production evidence (2026-09-29)

• General chat: /hackathon <url> produced full analyses for bnbchain bnb-ai-hack and tokenized-stocks.
• Topic: /hackathon bnb-hack-tokenized-stocks-edition linked and pinned the analysis. In D1, thread_id is 262 and pinned_message_id is 271.
• 11.3: the bot must be a group administrator with "Pin Messages". The Bot API requires the admin can_pin_messages right, and the member permission toggle is not enough.

Non-blocking follow-ups (recorded in verify-report.md)

• An all-null response counts as usable.
• The static text/plain path is not normalized.
• The escape test gap.
• 405 is not in the bot-wall set.
• The harness always runs the rendered fetch.
• A transient retry on a claimed job keeps the claim.
• A pin failure on a fresh run is not reported to the user.

🤖 Generated with Claude Code