⚖️ Sailing report conflicts

Reports where the guest's version disagrees with the cruise-data sources, so the auto-task held them instead of guessing. Pick which version is correct — your choice is applied to the database on the next data run.

🔎 Look up a user

Search by name OR username and open any user's profile card and cruises without being their friend — for checking how the app is displaying real accounts. Email, phone and date of birth are never shown, private messages are never shown, and every lookup is logged. Disclosed in Terms §5b.

🚩 User reports

Reports users have filed about a conversation, newest first, with the last 30 messages captured at the time of reporting (kept even if either side later deletes the thread). Mark each one Reviewed or Actioned once handled.

…

When ON, new visitors must enter an access code to use the app. Every account already has a code assigned — look it up in Supabase (or the query in access-gate-v2.sql) to share it.

…

Roll the Keepsake Maps feature out to all users. It stays visible and usable for you either way.

🧭 Routing diagnostic

Checks whether the land-avoidance map + pathfinder tables built on THIS device, and whether the shipped canonical map loaded (source + hash match). Run on any device to confirm identical routing.

🩺 Route health scan

Computes every one of your saved cruises' routes (same pipeline the map uses) and flags any that clip land or depend on the proxy. Runs one at a time — proxy legs can be slow on a cold proxy.

🧵 Dump a route

Prints one cruise's exact computed route + where it crosses land, so a precise carve/fix can be designed. Works on your saved cruises AND any sailing in the database — for a database lookup, include the exact date.

🔎 Preview any sailing

Opens the full sailing card + route map for any sailing in the database — without adding it to your profile. Include the exact date, e.g. "Celebrity Summit 2027-04-18". Press Enter or tap Preview.

📍 Geocode backfill

Find unresolved ports: ports with no pin yet — look up + save. Audit ALL pins: steps through every port already on the map (most-used first), pre-filling its current pin with a map link so you can eyeball it — correct any downtown/wrong berth and Save. Saving locks it so it overrides the shipped coord and never re-snaps.

Find unresolved ports Audit misplaced pins Audit every pin

🧭 Create a Carve

Trace a routing channel (fjord, port entry/exit, strait) by dragging pins on a satellite map. Enter a name, then either one place to center on, or "Start -> End" (e.g. Dixon Entrance -> Sitka, AK) to seed the pins strung along that line. Named ports resolve to their cruise pier from the app's own tables (not a region centroid). Choose how many pins, then Start. Drag each numbered pin into the water — 0 = the seaward mouth, last = nearest the pier; insert/remove pins as needed. Show entry gives the PORT_CHANNELS line to paste into index.html (then run the routing gate), and Save to database keeps a backup. Nothing affects live routing until the entry is pasted + deployed.

Pins Start

↻ Refresh Copy queue SQL

Carves you saved wait here for Claude to validate (land-crossing / pier-match check) before you paste + run the gate. A carve started from a map report shows 🔗 and gets checked against that sailing too.

Connect

See exact field names returned by the scraper for any ship — helps debug mapping issues.

Cancel Save Sailing

These corrections override the database whenever that ship is searched.