Make the agent API self-describing and add regression CI

[MaxBittker]

Summary

• replace regex API extraction with the TypeScript compiler AST and emit complete async signatures, defaults, return types, and untruncated JSDoc
• enforce public-method parity and generated-doc drift, including the four methods previously missing from the reference
• correct agent snippets and execution-environment guidance across combat, navigation, dialogs, mining, smithing, fishing, banking, shops, and background scripts
• improve NPC page generation with exact spawn samples and map-square bounds
• add root and webclient typechecks, focused regression tests, and GitHub CI; fix the two existing banking test nullability errors

Why

Recent benchmark transcripts repeatedly treated async scans as synchronous, copied ctx-based snippets into execute_code, and relied on stale state paths or navigation guidance. This makes the shipped documentation an executable contract and prevents API drift from recurring.

Validation

• bun run check
• root TypeScript check passes
• webclient TypeScript check passes
• existing chat-history and click-dialog suites pass
• 5 new docs/API tests pass with 345 assertions
• generated API check reports 43 BotActions methods, 93 BotSDK methods, and 39 result/state interfaces
• GitHub check workflow passes

Notes

• The initial wiki search helper was removed after review found worse recall than grep and misleading map-square matching; the guide now explicitly directs agents to grep learnings/ and wiki/.
• Existing NPC markdown pages were not bulk-regenerated; exact spawn samples appear on future generation.
• Documentation describes current main only and does not depend on stale PRs Add get_state MCP tool #1 or Add name-based combat style API (issue #20) #27.
• Merge this after Fix agent state telemetry and browser action contracts #45 and Make high-level actions report observed, exact outcomes #46, then regenerate sdk/API.md once those action surfaces land.