Export TypeScript types for btcmap.org via ts-rs

[escapedcat]

Implements #102 — TypeScript type generation for btcmap.org as a parallel dev tool.

What this does

• Adds ts-rs and derives TS on the 39 v4 response/request structs btcmap.org consumes (opt-in per struct; the unconsumed events module is deliberately skipped)
• Adds a type-export-only all-optional Place struct describing the dynamic fields-driven responses of GET /v4/places, kept in sync with service::element::TAGS by a unit test
• Commits bindings/ (the generated output) so consumers fetch it straight from GitHub — no Rust toolchain or checkout of this repo needed. cargo test regenerates the directory, and a new CI step fails if a commit leaves it stale
• Adds a devtools export-ts-types [target-dir] subcommand for exporting the bindings to an arbitrary directory locally
• Structs whose names repeat across modules get #[ts(rename = ...)] so every binding has a unique file/type name; 64-bit integers are exported as number (JSON transport), RFC 3339 timestamps as string

What this deliberately does not do

• No changes under docs/rest/ — the MD docs workflow is untouched
• No route, main.rs, or handler changes; nothing new is served or published
• No runtime code — the derive is compile-time only

Test plan

• cargo test — full suite green, including the 39 export_bindings_* tests and place_type_covers_all_generate_tags_fields
• devtools export-ts-types <dir> verified against a scratch dir (39 files) and a real btcmap.org checkout, where pnpm typecheck and pnpm lint pass over the generated files
• Docs: README section on the bindings workflow, AGENTS.md rules for agents touching exported structs

Companion frontend PR: teambtcmap/btcmap.org#1243 (should land after this one).

🤖 Generated with Claude Code