feat(accommodation): surface ratings, facilities and metadata

[akoso]

Picks up the accommodation metadata the API now stores and returns, and makes the CLI show it.

What changed

Types — openapi.json snapshot refreshed from production (additive: 210 insertions, 4 changed descriptions). Brings in imageUrl, description, url, the 15-member features enum, externalRating (score + scale + count + source), type / roomDetails on the read path, and locationiqPlaceId on option locations. bun run codegen regenerates cleanly; no existing code broke.

Read path — mna trips show now prints an accommodation table per variant:

Accommodation · Calabria + Sicily
Destination     Option                   Cost      Rating       Details                      Facilities
──────────────  ───────────────────────  ────────  ───────────  ───────────────────────────  ─────────────────────
Split, Croatia  ✓ Field-check Apartment  1200 EUR  8.8/10 (92)  apartment · 2 rooms · 55 m²  Beachfront, Private k…
Split, Croatia    Flat-location probe    500 EUR   4.4/5 (310)  hotel · 1 room               Pool, Free WiFi

Ratings stay in the scale their source published them in — 8.8/10 and 4.4/5 are never normalised or compared against each other. --all-options now changes the human output too (previously it only affected --json); without it you get the selected option per destination.

Write path — no code change needed. mna options add|edit --from-json passes the JSON body straight through, so every new field is already settable. Verified end-to-end against production on a throwaway trip (created, written, read back, deleted): externalRating, features, description, url, imageUrl, type, roomDetails and location.locationiqPlaceId all round-trip.

Skill — skills/mna/SKILL.md and both references:

• ratings/facilities/links go in their own fields, in native units; privateKitchen ≠ sharedKitchen
• name is a display name, not a place to stash price, town or working state — commentary belongs in notes
• a "Heuristics from real sessions" section: estimates aren't decision-grade, cost the trip rather than the room, compare towns before properties when the destination is open, elicit rather than assume (and stop interviewing a user who just wants a pick), forward legs beat backtracks, regional traps, anchors first
• corrected the location write shape (see below)

Found while verifying

• The reference doc had the location shape backwards. It said the flat address/latitude/longitude form is silently dropped and coordinates persist only when nested. Production does the opposite: the flat form persists, the nested formattedAddress/coordinates form is dropped and only name survives. Reproduced on both options add and options edit. Corrected in references/cli-and-schemas.md, along with the fact that location is replaced wholesale rather than merged.
• mna variants add is broken against production — the server rejects a body without dates (400, no message) even though the spec marks only name as required, and the command has no date flags. Reproducible on a fresh trip. Out of scope here, left alone.
• The event-location example still documents coordinates.latitude/.longitude, but the current spec's CreateEventLocationCoordinatesV1Dto requires lat/lng. Not tested, not changed.

Gates

bun run codegen, bun run typecheck, bun run lint, bun test (138 pass, 0 fail — 10 new), bun run build + node dist/mna.js --version all green.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AsdP2hvt4XQhYxkdNREXUq