Why
- tools/gogcli was pinned to an older root rev, so plugin output still resolved
gogcli 0.9.0 even after package bump.
What
- update tools/gogcli root input to openclaw/nix-steipete-tools rev eddb00d...
- refresh tools/gogcli/flake.lock root input to same rev
Tests
- cd tools/gogcli && nix build .#gogcli
- cd tools/gogcli && ./result/bin/gog version # 0.11.1
Why
- Need immediate delivery of refresh-token rotation persistence fix before upstream release.
- Keep existing binary-tar packaging flow (no package-model changes).
What
- bump gogcli package version 0.11.0 -> 0.11.1
- switch release artifact URLs to joshp123/gogcli v0.11.1
- update SRI hashes for darwin arm64, linux amd64, linux arm64 assets
Tests
- nix build .#gogcli
- ./result/bin/gog version
What:
- delete oracle package and plugin exports
- remove oracle from tool update and skill sync pipelines
- remove oracle mentions from README
Why:
- oracle is no longer part of the bundled toolchain
- keep package/update surface aligned with active bundled plugins only
Tests:
- go test ./... (pass)
- nix flake check --no-build (pass)
What:
- update goplaces skill to use Apple Maps links from current location
- document preview behavior for fixed origins
Why:
- ensure Go button appears on iOS for turn-by-turn
Tests:
- not run (skill text change)
What:
- update goplaces skill with Apple Maps transit + cycling guidance
Why:
- ensure Apple Watch links cover all supported modes
Tests:
- not run (skill text change)
What:
- update goplaces plugin root input to latest nix-steipete-tools rev
Why:
- keep plugin aligned with new goplaces units default
Tests:
- not run (pin update only)
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
What:
- update goplaces skill to always use directions --steps
- enforce verbatim instructions (no paraphrase)
- prefer metric formatting from JSON distances
Why:
- avoid directional confusion in bot responses
- standardize on metric output
Tests:
- not run (skill text change)
What:
- add guidance for closest-place queries
- document directions via Google Maps links (not Routes API)
Why:
- make behavior explicit for “closest X” and A→B requests
- avoid misleading ETA/distance guesses
Tests:
- go test ./...
What:
- remove GOOGLE_PLACES_API_KEY from goplaces plugin requiredEnv
Why:
- keep default plugin enablement from failing HM activation
- still document env requirement in skill text
Tests:
- go test ./...
