docs: note Mini 3 Plus tracking-interval autoextend in IPC quick-ref (#197)#202
Open
brockamer wants to merge 1 commit into
Open
docs: note Mini 3 Plus tracking-interval autoextend in IPC quick-ref (#197)#202brockamer wants to merge 1 commit into
brockamer wants to merge 1 commit into
Conversation
During #197 investigation, real-device tracing confirmed the Mini 3 Plus autonomously flaps its tracking interval (mc=11 events with status.intervalChange toggling between configured 120s and 14400s) based on stationary detection. Worth documenting alongside the existing IPC schema/auth quick-ref so future readers don't trip on "why are there so few MapShare breadcrumbs" the same way #197 did. Also notes that MapShare KML and IPC Outbound mc=0 streams are independent — same window, different ping counts. References #201 (decode + persist current interval) as the follow-up. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CLAUDE.md's Garmin IPC quick-ref documenting the device's autonomous tracking-interval flap (status.intervalChangetoggling between configured 120s and 14400s during stationary periods), discovered during fix(tracking): single-ping Stop Track sessions publish zero-distance "ghost" posts (LLM hallucinates speeds) #197 investigation.Why
Future readers grepping CLAUDE.md for Garmin IPC behavior will need to know:
Both were costly insights in this session that aren't in any spec we keep locally.
Test plan
🤖 Generated with Claude Code