catence 0.2.0-beta.6 → 0.2.0-beta.7

package/dist/contracts/release.d.ts

@@ -3,7 +3,7 @@
  * Keep these values synchronized with release/manifest.json; release checks
  * deliberately reject drift before a package can be published.
  */
-export declare const CATENCE_RUNTIME_VERSION = "0.2.0-beta.6";
+export declare const CATENCE_RUNTIME_VERSION = "0.2.0-beta.7";
 export declare const CATENCE_PROTOCOL_VERSION = 1;
 export type CatenceRuntimeCapabilities = {
     mcp: true;

package/dist/contracts/release.js

@@ -3,7 +3,7 @@
  * Keep these values synchronized with release/manifest.json; release checks
  * deliberately reject drift before a package can be published.
  */
-export const CATENCE_RUNTIME_VERSION = '0.2.0-beta.6';
+export const CATENCE_RUNTIME_VERSION = '0.2.0-beta.7';
 export const CATENCE_PROTOCOL_VERSION = 1;
 export function catenceRuntimeHealth() {
     return {

package/docs/deployment.md

@@ -59,13 +59,24 @@ that already holds only Console artifacts (`config.json`, `console/`).
 
 ### 3. Store provider credentials (stdin only, never shell history)
 
+Garmin (`email`, `password`), Intervals.icu (`apiKey`, `athleteId`), and Strava
+(`clientId`, `clientSecret`):
+
 ```sh
+# Garmin
 printf %s 'alex@example.com' | catence-data --athlete alex secret set --provider garmin --field email --value-stdin
 printf %s 'your-garmin-password' | catence-data --athlete alex secret set --provider garmin --field password --value-stdin
+# Intervals.icu
 printf %s 'intervals-api-key' | catence-data --athlete alex secret set --provider intervals --field apiKey --value-stdin
 printf %s '12345' | catence-data --athlete alex secret set --provider intervals --field athleteId --value-stdin
+# Strava (create an API application at https://www.strava.com/settings/api)
+printf %s 'strava-client-id' | catence-data --athlete alex secret set --provider strava --field clientId --value-stdin
+printf %s 'strava-client-secret' | catence-data --athlete alex secret set --provider strava --field clientSecret --value-stdin
 ```
 
+Set only the providers you actually sync; `secret set` accepts each field
+independently.
+
 ### 4. Sync data and build retrieval context
 
 ```sh
@@ -153,14 +164,35 @@ docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.e
 
 ### 4. Store provider credentials
 
+Garmin (`email`, `password`), Intervals.icu (`apiKey`, `athleteId`), and Strava
+(`clientId`, `clientSecret`), one `printf` per field:
+
 ```sh
-printf %s 'value' | docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env run --rm -T \
+# Garmin
+printf %s 'alex@example.com' | docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env run --rm -T \
+  --entrypoint catence-data console --athlete alex secret set \
+  --provider garmin --field email --value-stdin
+printf %s 'your-garmin-password' | docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env run --rm -T \
+  --entrypoint catence-data console --athlete alex secret set \
+  --provider garmin --field password --value-stdin
+# Intervals.icu
+printf %s 'intervals-api-key' | docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env run --rm -T \
   --entrypoint catence-data console --athlete alex secret set \
   --provider intervals --field apiKey --value-stdin
+printf %s '12345' | docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env run --rm -T \
+  --entrypoint catence-data console --athlete alex secret set \
+  --provider intervals --field athleteId --value-stdin
+# Strava (create an API application at https://www.strava.com/settings/api)
+printf %s 'strava-client-id' | docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env run --rm -T \
+  --entrypoint catence-data console --athlete alex secret set \
+  --provider strava --field clientId --value-stdin
+printf %s 'strava-client-secret' | docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env run --rm -T \
+  --entrypoint catence-data console --athlete alex secret set \
+  --provider strava --field clientSecret --value-stdin
 ```
 
-Use the same `--entrypoint catence-data` pattern for `sync`, `backfill`, and
-`auth strava`.
+Set only the providers you actually sync. Use the same `--entrypoint
+catence-data` pattern for `sync`, `backfill`, and `auth strava`.
 
 ### 5. Configure the model
 
@@ -176,7 +208,54 @@ docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.e
 With `--home <dir>` (bind mount), edit `<dir>/config.json` on the host
 instead. To add OpenCode Go models, see [model discovery](#model-discovery-opencode-go).
 
-### 6. Expose the Console safely
+### 6. Verify with doctor
+
+`catence-console doctor` checks each profile's environment variables and the
+local Catence runtime. The deploy scaffold includes a helper for it:
+
+```sh
+./catence-deploy/doctor.sh
+```
+
+The helper runs the doctor *inside the running container* with `exec` — the
+container's own loopback holds the live MCP server at `127.0.0.1:8787`, and the
+provider keys from `.env` are already in its environment. (A `docker compose
+run` container has a separate loopback and would report the runtime as
+unreachable.) The equivalent long form is:
+
+```sh
+docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env exec console \
+  /opt/catence-console/bin/catence-console doctor --home /data --mcp-url http://127.0.0.1:8787/mcp
+```
+
+Expect `"ready": true` once the model key is set; missing keys show up per
+profile without ever printing their values.
+
+### 7. Sync, backfill, and inspect athlete data
+
+The deploy scaffold includes a helper that runs `catence-data` *inside the
+running container* with `exec`, so the athlete's provider secrets from the
+data volume are already available:
+
+```sh
+./catence-deploy/sync.sh --athlete alex sync                  # incremental sync, all providers
+./catence-deploy/sync.sh --athlete alex backfill 2026-01-01   # full backfill from a date
+./catence-deploy/sync.sh --athlete alex status                # coverage and errors
+./catence-deploy/sync.sh athletes                             # list athlete IDs
+```
+
+`sync` defaults to `--provider all`; extra flags pass through, for example
+`./catence-deploy/sync.sh --athlete alex sync --refresh` or
+`./catence-deploy/sync.sh --athlete alex backfill 2026-01-01 --provider garmin`.
+Set a default athlete with `export CATENCE_ATHLETE=alex` to drop the
+`--athlete` argument. The equivalent long form is:
+
+```sh
+docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env exec console \
+  catence-data sync --athlete alex --provider all --home /data
+```
+
+### 8. Expose the Console safely
 
 Keep the Console port bound to `127.0.0.1` (the default) and front it with a
 Cloudflare Tunnel or reverse proxy at HTTPS. Never expose Catence's MCP port

package/docs/llm-providers.md

@@ -306,6 +306,14 @@ prints credential values.
 catence-console doctor --home "$HOME/.catence" --mcp-url http://127.0.0.1:8787/mcp
 ```
 
+On Docker, the deploy scaffold includes a helper that runs it inside the
+running container (`exec`, not `run` — the container's loopback hosts the live
+MCP server and the `.env` provider keys are in its environment):
+
+```sh
+./catence-deploy/doctor.sh
+```
+
 ## Docker: generating the Console login hash
 
 `deploy-console.sh` writes a small helper into the deployment directory. Run it

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "catence",
-  "version": "0.2.0-beta.6",
+  "version": "0.2.0-beta.7",
   "description": "Local MCP access to normalized Garmin, Intervals.icu, and targeted Strava fitness data.",
   "license": "AGPL-3.0-or-later",
   "repository": {