fartlek-mcp 0.3.0__tar.gz

fartlek_mcp-0.3.0/.dockerignore

@@ -0,0 +1,21 @@
+.git
+.github
+.env
+.venv
+.pytest_cache
+__pycache__
+*.pyc
+*.pyo
+*.egg-info
+.coverage
+htmlcov
+.mypy_cache
+.ruff_cache
+*.db
+*.db-journal
+data/
+scratchpad/
+private/
+.fartlek/
+garmin_tokens.json
+.DS_Store

fartlek_mcp-0.3.0/.github/workflows/ci.yml

@@ -0,0 +1,18 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      - run: uv sync --frozen
+      - run: uv run ruff check fartlek/ tests/
+      - run: uv run pytest -q

fartlek_mcp-0.3.0/.github/workflows/release.yml

@@ -0,0 +1,27 @@
+name: release
+
+# Publish to PyPI via trusted publishing (OIDC) on version tags.
+# Requires a one-time PyPI trusted-publisher setup and a GitHub environment named `pypi`.
+# No API tokens: identity is proven by GitHub Actions to PyPI directly.
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi  # must match the environment name configured on PyPI
+    permissions:
+      id-token: write  # required for trusted publishing (OIDC)
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      # Gate the release on the same checks as CI — a bad version can't be
+      # re-uploaded, so don't ship one that fails its own tests.
+      - run: uv sync --frozen
+      - run: uv run ruff check fartlek/ tests/
+      - run: uv run pytest -q
+      - run: uv build
+      - run: uv publish

fartlek_mcp-0.3.0/.gitignore

@@ -0,0 +1,54 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+*.egg
+*.egg-info/
+build/
+dist/
+
+# Virtual environments
+.venv/
+venv/
+env/
+
+# Environment / secrets
+.env
+.env.local
+*.pem
+*.key
+
+# uv
+.uv-cache/
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# macOS
+.DS_Store
+
+# Logs
+*.log
+
+# Test artifacts
+.pytest_cache/
+.coverage
+htmlcov/
+.mypy_cache/
+.ruff_cache/
+
+# Local data
+*.db
+*.sqlite
+*.sqlite3
+
+# Playwright MCP page snapshots
+.playwright-mcp/
+
+# Local agent instructions
+CLAUDE.md

fartlek_mcp-0.3.0/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "fartlek": {
+      "command": "uv",
+      "args": ["run", "fartlek-mcp"]
+    }
+  }
+}

fartlek_mcp-0.3.0/Dockerfile

@@ -0,0 +1,28 @@
+# syntax=docker/dockerfile:1
+FROM python:3.12-slim
+
+# Install uv
+COPY --from=ghcr.io/astral-sh/uv:latest /uv /bin/uv
+
+WORKDIR /app
+
+# Copy project metadata and install dependencies first (better layer caching)
+COPY pyproject.toml README.md LICENSE ./
+COPY fartlek/ ./fartlek/
+
+# The base install reads a Garmin account export and needs no Garmin login.
+# The direct connection is optional and left out of the image by default:
+#   docker build --build-arg CONNECT=true -t fartlek-mcp .
+# adds the `connect` extra (garminconnect). Read the README warning first.
+ARG CONNECT=false
+RUN if [ "$CONNECT" = "true" ]; then uv pip install --system ".[connect]"; \
+    else uv pip install --system .; fi
+
+# The store (and tokens, with the direct connection) live on a volume, not in the image
+ENV FARTLEK_HOME=/data
+VOLUME /data
+
+# The MCP server speaks stdio. To import an export, override the entrypoint:
+#   docker run --rm -v "$PWD/fartlek-data:/data" -v "$PWD/export.zip:/export/export.zip:ro" \
+#     --entrypoint fartlek fartlek-mcp import /export/export.zip
+ENTRYPOINT ["fartlek-mcp"]

fartlek_mcp-0.3.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Matis Despujols
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

fartlek_mcp-0.3.0/PKG-INFO

@@ -0,0 +1,122 @@
+Metadata-Version: 2.5
+Name: fartlek-mcp
+Version: 0.3.0
+Summary: Fartlek — a coach's morning report from your Garmin data, for any LLM via MCP
+Project-URL: Homepage, https://github.com/matisdsp/fartlek
+Project-URL: Repository, https://github.com/matisdsp/fartlek
+Project-URL: Issues, https://github.com/matisdsp/fartlek/issues
+Author: Fartlek contributors
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: coaching,garmin,llm,mcp,running,training
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Information Analysis
+Classifier: Topic :: Utilities
+Requires-Python: >=3.12
+Requires-Dist: fitdecode>=0.11.0
+Requires-Dist: mcp[cli]<2,>=1.27.1
+Provides-Extra: connect
+Requires-Dist: garminconnect>=0.3.6; extra == 'connect'
+Description-Content-Type: text/markdown
+
+<!-- mcp-name: io.github.matisdsp/fartlek -->
+
+# Fartlek
+
+*A coach's morning report from your Garmin data, for any LLM via MCP.*
+
+Every other Garmin MCP server hands the LLM a filing cabinet of raw JSON: one night of sleep is ~52K tokens, one activity stream ~155K. The model can't read it, so it skims and improvises. Fartlek does the synthesis server-side: computed sports-science metrics (CTL/ATL/TSB, ACWR, monotony, calibrated training load), personal baselines with significance floors, safety alerts, delivered as compact, verdict-first reports the model can actually reason about.
+
+**The token contract:** calling every tool in the catalog once, at default arguments, costs under 17K tokens, about a third of one raw Garmin sleep payload (the sum of the caps below is 16,970; `tests/test_guardrails.py` fails above 17,000). Without `garmin_raw` and `garmin_reference` the sum is 9,970. Hard caps are enforced per response by the renderer, with disclosed truncation, and `tests/test_budget_gate.py` counts golden renders with a real tokenizer.
+
+## The tools
+
+Caps are in tokens, as set in the code (`CAP` constants in `fartlek/mcp_server/tools/`).
+
+| Tool | What it answers | Cap |
+|---|---|---|
+| `garmin_brief` | "How am I today, can I train hard?" Fused GREEN/AMBER/RED verdict vs your own baselines | 600 |
+| `garmin_activities` | Browse the log, get activity IDs | 1,300 |
+| `garmin_activity` | One session in depth: reps, fade, comparison to your most similar past session (`detail` standard, splits, full) | 1,000 / 2,000 / 4,000 |
+| `garmin_athlete` | Reference card: zones, PRs, goal, data coverage | 600 |
+| `garmin_gear` | Shoe and bike mileage vs the retirement limits you set in Garmin Connect, and what you actually rotate | 500 |
+| `garmin_set_profile` | Tell it your goal race, phase and availability (local only) | 200 |
+| `garmin_log` | Log RPE, wellness, illness or injury; the athlete outranks the sensors | 120 |
+| `garmin_sync` | Re-read the export, or deepen history | 150 |
+| `garmin_setup` | Is the server configured, and what is missing; starts with the export | 400 |
+| `garmin_recovery` | Sleep, HRV, resting HR and load structure vs baselines, plus the overtraining audit | 1,100 |
+| `garmin_load` | Multi-week load: CTL/ATL/TSB, ramp, ACWR, monotony, intensity drift | 1,100 |
+| `garmin_fitness` | VO2max and efficiency trends, race projection against your goal, taper guidance | 1,000 |
+| `garmin_week` | One week in session-level detail, with load vs recent weeks | 1,200 |
+| `garmin_whats_changed` | Only the statistically significant changes of the last N days | 700 |
+| `garmin_reference` | How a number was computed, and whether to trust it | 2,000 per topic |
+| `garmin_raw` | Bounded, compacted escape hatch to named raw sources | 5,000 |
+
+## Quickstart
+
+```bash
+pipx install fartlek-mcp        # or: uv tool install fartlek-mcp
+```
+
+1. In your Garmin account, open **Data Management > Export Your Data** and request the export. Garmin
+   emails you a download link. It says this usually takes about 48 hours and can take up to 30 days.
+2. Import the zip. Nothing connects to Garmin and no credentials are involved:
+
+```bash
+fartlek import ~/Downloads/<your-export>.zip
+```
+
+3. Point your MCP client at the server. Claude Code:
+
+```bash
+claude mcp add fartlek -- fartlek-mcp
+```
+
+Any other MCP client: add a stdio server whose command is `fartlek-mcp`.
+
+The report stops at the day of the export. Importing a newer export updates the store. Your own settings
+and log entries are kept.
+
+## What the export does not contain
+
+Compared on one real account against the Connect API, over 530 activities and 356 days: activities, laps,
+overnight HRV and sleep scores are identical after converting units, and daily totals match on 99 % of days
+or more. A one-account check is not a guarantee for other devices. The export lacks:
+
+| Missing | Effect |
+|---|---|
+| Per-minute sleep stages | Sleep regularity index unavailable |
+| Garmin's nightly sleep need | Sleep debt uses 8 h, or the need you set |
+| HRV status and weekly average | Not shown; Fartlek's own HRV band does not use them |
+| Grade-adjusted speed per lap | Efficiency and decoupling use plain speed |
+| Model names of unrenamed gear | Gear may appear under its brand only |
+| Raw detail per session | `garmin_raw` and `garmin_activity detail=full` have nothing to return |
+
+## CLI
+
+| Command | What it does |
+|---|---|
+| `fartlek import <zip>` | fill the local store from a Garmin account export (`--since YYYY-MM-DD` limits how far back) |
+| `fartlek accounts` | list local accounts |
+| `fartlek export [dir]` | export the store (SQLite snapshot and one CSV per table) |
+| `fartlek reset` | wipe all local data (asks confirmation) |
+
+`FARTLEK_HOME` sets the data directory (default `~/.fartlek`). The `Dockerfile` builds the same server: mount
+a data volume on `/data`.
+
+## Privacy and Garmin's terms
+
+Stdio transport, local SQLite store: your health data stays on your machine, and importing an export contacts
+nobody. The code also contains a direct connection to Garmin Connect. It is off by default and unsupported: it
+reads endpoints Garmin does not publish for third parties, which Garmin's
+[Terms of Use](https://www.garmin.com/en-US/legal/terms-of-use/) do not allow, and Garmin can suspend accounts
+for automated access.
+
+## License & trademark
+
+Apache 2.0. Fartlek is an independent open-source project, **not affiliated with, endorsed by, or sponsored by Garmin Ltd.** "Garmin" is used only to describe compatibility with Garmin Connect data.

fartlek_mcp-0.3.0/README.md

@@ -0,0 +1,96 @@
+<!-- mcp-name: io.github.matisdsp/fartlek -->
+
+# Fartlek
+
+*A coach's morning report from your Garmin data, for any LLM via MCP.*
+
+Every other Garmin MCP server hands the LLM a filing cabinet of raw JSON: one night of sleep is ~52K tokens, one activity stream ~155K. The model can't read it, so it skims and improvises. Fartlek does the synthesis server-side: computed sports-science metrics (CTL/ATL/TSB, ACWR, monotony, calibrated training load), personal baselines with significance floors, safety alerts, delivered as compact, verdict-first reports the model can actually reason about.
+
+**The token contract:** calling every tool in the catalog once, at default arguments, costs under 17K tokens, about a third of one raw Garmin sleep payload (the sum of the caps below is 16,970; `tests/test_guardrails.py` fails above 17,000). Without `garmin_raw` and `garmin_reference` the sum is 9,970. Hard caps are enforced per response by the renderer, with disclosed truncation, and `tests/test_budget_gate.py` counts golden renders with a real tokenizer.
+
+## The tools
+
+Caps are in tokens, as set in the code (`CAP` constants in `fartlek/mcp_server/tools/`).
+
+| Tool | What it answers | Cap |
+|---|---|---|
+| `garmin_brief` | "How am I today, can I train hard?" Fused GREEN/AMBER/RED verdict vs your own baselines | 600 |
+| `garmin_activities` | Browse the log, get activity IDs | 1,300 |
+| `garmin_activity` | One session in depth: reps, fade, comparison to your most similar past session (`detail` standard, splits, full) | 1,000 / 2,000 / 4,000 |
+| `garmin_athlete` | Reference card: zones, PRs, goal, data coverage | 600 |
+| `garmin_gear` | Shoe and bike mileage vs the retirement limits you set in Garmin Connect, and what you actually rotate | 500 |
+| `garmin_set_profile` | Tell it your goal race, phase and availability (local only) | 200 |
+| `garmin_log` | Log RPE, wellness, illness or injury; the athlete outranks the sensors | 120 |
+| `garmin_sync` | Re-read the export, or deepen history | 150 |
+| `garmin_setup` | Is the server configured, and what is missing; starts with the export | 400 |
+| `garmin_recovery` | Sleep, HRV, resting HR and load structure vs baselines, plus the overtraining audit | 1,100 |
+| `garmin_load` | Multi-week load: CTL/ATL/TSB, ramp, ACWR, monotony, intensity drift | 1,100 |
+| `garmin_fitness` | VO2max and efficiency trends, race projection against your goal, taper guidance | 1,000 |
+| `garmin_week` | One week in session-level detail, with load vs recent weeks | 1,200 |
+| `garmin_whats_changed` | Only the statistically significant changes of the last N days | 700 |
+| `garmin_reference` | How a number was computed, and whether to trust it | 2,000 per topic |
+| `garmin_raw` | Bounded, compacted escape hatch to named raw sources | 5,000 |
+
+## Quickstart
+
+```bash
+pipx install fartlek-mcp        # or: uv tool install fartlek-mcp
+```
+
+1. In your Garmin account, open **Data Management > Export Your Data** and request the export. Garmin
+   emails you a download link. It says this usually takes about 48 hours and can take up to 30 days.
+2. Import the zip. Nothing connects to Garmin and no credentials are involved:
+
+```bash
+fartlek import ~/Downloads/<your-export>.zip
+```
+
+3. Point your MCP client at the server. Claude Code:
+
+```bash
+claude mcp add fartlek -- fartlek-mcp
+```
+
+Any other MCP client: add a stdio server whose command is `fartlek-mcp`.
+
+The report stops at the day of the export. Importing a newer export updates the store. Your own settings
+and log entries are kept.
+
+## What the export does not contain
+
+Compared on one real account against the Connect API, over 530 activities and 356 days: activities, laps,
+overnight HRV and sleep scores are identical after converting units, and daily totals match on 99 % of days
+or more. A one-account check is not a guarantee for other devices. The export lacks:
+
+| Missing | Effect |
+|---|---|
+| Per-minute sleep stages | Sleep regularity index unavailable |
+| Garmin's nightly sleep need | Sleep debt uses 8 h, or the need you set |
+| HRV status and weekly average | Not shown; Fartlek's own HRV band does not use them |
+| Grade-adjusted speed per lap | Efficiency and decoupling use plain speed |
+| Model names of unrenamed gear | Gear may appear under its brand only |
+| Raw detail per session | `garmin_raw` and `garmin_activity detail=full` have nothing to return |
+
+## CLI
+
+| Command | What it does |
+|---|---|
+| `fartlek import <zip>` | fill the local store from a Garmin account export (`--since YYYY-MM-DD` limits how far back) |
+| `fartlek accounts` | list local accounts |
+| `fartlek export [dir]` | export the store (SQLite snapshot and one CSV per table) |
+| `fartlek reset` | wipe all local data (asks confirmation) |
+
+`FARTLEK_HOME` sets the data directory (default `~/.fartlek`). The `Dockerfile` builds the same server: mount
+a data volume on `/data`.
+
+## Privacy and Garmin's terms
+
+Stdio transport, local SQLite store: your health data stays on your machine, and importing an export contacts
+nobody. The code also contains a direct connection to Garmin Connect. It is off by default and unsupported: it
+reads endpoints Garmin does not publish for third parties, which Garmin's
+[Terms of Use](https://www.garmin.com/en-US/legal/terms-of-use/) do not allow, and Garmin can suspend accounts
+for automated access.
+
+## License & trademark
+
+Apache 2.0. Fartlek is an independent open-source project, **not affiliated with, endorsed by, or sponsored by Garmin Ltd.** "Garmin" is used only to describe compatibility with Garmin Connect data.