From e1034a2cb7a5f70c4f738bd030235978f1170c44 Mon Sep 17 00:00:00 2001
From: Don Garrett <dgarrett@acm.org>
Date: Wed, 23 Sep 2026 23:45:02 +0000
Subject: [PATCH] Show which config key refers to each example secret

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---
 .env.example | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/.env.example b/.env.example
index fc774ee..bda36a0 100644
--- a/.env.example
+++ b/.env.example
@@ -5,9 +5,12 @@
 # which refers to these by name, e.g. `token: ${NISSE_LLM_TOKEN}`. The live
 # integration tests use the same names, from tests/integration/nisse-test.yaml.
 
-NISSE_LLM_TOKEN=sk-your-litellm-virtual-key
-NISSE_MATRIX_TOKEN=syt_your_matrix_access_token
-NISSE_GITEA_TOKEN=your-scoped-service-account-token
+# llm.token: the LiteLLM virtual key (A5)
+NISSE_LLM_TOKEN=replace-me
+# matrix.token: the Matrix access token for the agent's account (A1)
+NISSE_MATRIX_TOKEN=replace-me
+# gitea.token: the Gitea service account's scoped token (B2)
+NISSE_GITEA_TOKEN=replace-me
 
 # Where the config file is, if not ./nisse-dev.yaml. Where this file is, if
 # not ./.env, is NISSE_ENV, which has to be set in the real environment.