From 32bfabe2847d5b3517fd5d688d59aa2fbc16be02 Mon Sep 17 00:00:00 2001 From: Elmehdi Aitbrahim Date: Sun, 9 Aug 2026 19:03:33 -0400 Subject: [PATCH] docs(config): document the robinhood probe's key names in .env.example `scripts/robinhood_smoke.py` (#216) has required `ROBINHOOD_API_KEY` and `ROBINHOOD_PRIVATE_KEY` since it landed, and #218 exercised it against the live venue twice, but neither PR added the names to `.env.example` -- so the only record of what to put in `.env` was the script's own failure message, which you see after you already went looking. Both are commented as probe-only on purpose. `load_secrets` does not read them, so a reader who fills them in and expects the adapter to come alive in a run has misread the state of this package; the README says the same thing at length and this is the one-line version at the point of use. The seed encoding is called out because a PEM is the likelier guess and fails with a length error rather than anything that names the cause. Co-Authored-By: Claude Opus 5 (1M context) --- .env.example | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.env.example b/.env.example index 244e621f..d17b51eb 100644 --- a/.env.example +++ b/.env.example @@ -1,6 +1,13 @@ CDP_API_KEY= CDP_API_SECRET= +# Read by `scripts/robinhood_smoke.py` ONLY -- the read-only live probe. `load_secrets` does not +# read these yet, so setting them does not wire the Robinhood adapter into a run; see +# `packages/keel-broker-robinhood/README.md`. ROBINHOOD_PRIVATE_KEY is the base64 of the raw +# 32-byte Ed25519 seed, not a PEM. +ROBINHOOD_API_KEY= +ROBINHOOD_PRIVATE_KEY= + # Optional. Where CRITICAL escalations are POSTed as JSON (ntfy, Pushover, a Slack/Discord # webhook, anything that accepts a POST body). Unset means alerting is off entirely and keel # makes no network call for it -- but then `reconcile.position_unprotected` ("this tranche is