fix(tools): wrap whole-degree headings at 360 to 0

The query tools rounded courses, headings, bearings and azimuths with
Number(value.toFixed(0)) and no wrap, so a direction of 359.5 degrees or
more came back as 360: find_vessel with course 359.7 and heading 359.6
returned course_deg 360 and heading_deg 360.

Round them through the shared roundHeadingDegrees helper the layers and
UI already use (src/data/headingDegrees.js), which wraps into 0 to 359:
course_deg and heading_deg (vessels), course_deg (aircraft), bearing_deg
(transit), heading_deg (cameras), and rise_azimuth_deg and azimuth_deg
(satellites). Other rounding is unchanged.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/CURRENT-STATE.md

@@ -204,7 +204,10 @@ perimeters, terrain height, military installations and map features, plus a
 combined situation brief, military awareness around a point, the app's heads-up display caption, and a link that
 opens the app over an area. Tools reuse the layers' portable source factories, take a
 shared `area` argument (place name, bounding box, or point and radius) and cap
-lists at 25 rows by default. `aircraft_in_area` and `vessels_in_area` can also
+lists at 25 rows by default. Vessel `course_deg` and `heading_deg`, aircraft
+`course_deg`, transit `bearing_deg`, camera `heading_deg` and satellite
+`rise_azimuth_deg` and `azimuth_deg` are whole degrees from 0 to 359; a
+direction of 359.5° or more reads 0 rather than 360. `aircraft_in_area` and `vessels_in_area` can also
 count every match by a field (`group_by`: airline, read from the ICAO
 designator in the callsign, or operator, country or type for aircraft; type or
 destination for ships; the ten largest groups, then other and unknown counts;