🤖 feat: bump goplaces for metric units

What:
- update goplaces source rev to include units support
- note metric units default in goplaces skill guidance

Why:
- allow human directions output to be metric by default

Tests:
- nix build .#goplaces --accept-flake-config

nix/pkgs/goplaces.nix

@@ -7,8 +7,8 @@ buildGoModule rec {
   src = fetchFromGitHub {
     owner = "joshp123";
     repo = "goplaces";
-    rev = "c7be7782989c4f2d24aba8c1122d0b6207247d31";
-    hash = "sha256-noyIyj7dtVscUUSUlcUhKt45QUH/bZL/fINwqR6fZS0=";
+    rev = "a71fe3de986a78607d923f397113d7eb1babc111";
+    hash = "sha256-Lufp9+fwcoluNZR9iDYoIJ1yu3sM/8Q/EOkAlq5VLdk=";
   };
 
   subPackages = [ "cmd/goplaces" ];

tools/goplaces/skills/goplaces/SKILL.md

@@ -37,6 +37,7 @@ Directions (A → B)
   - `goplaces resolve "Hotel Zelos San Francisco" --json`
 - Compare driving ETA alongside walking:
   - `goplaces directions --from-place-id <fromId> --to-place-id <toId> --compare drive --steps --json`
+- Units default to metric; use `--units imperial` only when explicitly requested.
 - Prefer metric output: format from JSON using `distance_meters` (m/km) and `duration_seconds` (mins). Use step `distance_meters` for each step.
 - Never paraphrase or reinterpret directions; emit `steps[].instruction` verbatim and do not reword compass directions.
 - `goplaces route` is only for searching places along a route (Routes API), not directions/ETA.