From af12061cc01e4c32ba8e154170959b8fbbf48bdb Mon Sep 17 00:00:00 2001 From: Cameron Cordes Date: Tue, 29 Sep 2026 20:40:45 -0400 Subject: [PATCH 1/2] docs: document LOCAL_BIND_URL (constitution IV) #145 added the optional LOCAL_BIND_URL (the secondary loopback listener, default localhost:8088, empty = skip) but documented it only in CLAUDE.md. Constitution IV requires every new environment variable in the README environment section; also add it to .env.example. Co-Authored-By: Claude Opus 5.5 --- .env.example | 3 +++ README.md | 1 + 2 files changed, 4 insertions(+) diff --git a/.env.example b/.env.example index 3ec0662..1ec01c3 100644 --- a/.env.example +++ b/.env.example @@ -11,6 +11,9 @@ VIDEO_PATH=/path/to/video/hls GIFS_DIRECTORY=/path/to/gifs PREVIEW_CLIPS_DIRECTORY=/path/to/preview-clips BIND_URL=0.0.0.0:8080 +# Secondary loopback listener (default localhost:8088). Empty = don't bind it +# (e.g. a second instance next to one that already owns 8088). +# LOCAL_BIND_URL=localhost:8088 CORS_ALLOWED_ORIGINS=http://localhost:3000 SECRET_KEY=replace-me-with-a-long-random-secret RUST_LOG=info diff --git a/README.md b/README.md index 693d977..16a161c 100644 --- a/README.md +++ b/README.md @@ -71,6 +71,7 @@ They should be defined where the binary is located or above it in an `.env` file - `VIDEO_PATH` is a path where HLS playlists and video parts should be stored - `GIFS_DIRECTORY` is a path where generated video GIF thumbnails should be stored - `BIND_URL` is the url and port to bind to (typically your own IP address) +- `LOCAL_BIND_URL` (optional) is a second, loopback listener [default: `localhost:8088`]. Set it to an empty string to skip it, e.g. to run a second instance such as the `dev/e2e` harness alongside one that already owns 8088 - `SECRET_KEY` is the *hopefully* random string to sign Tokens with - `RUST_LOG` is one of `off, error, warn, info, debug, trace`, from least to most noisy [default: `info` for spans, `error` for dev console logs]. It also gates tracing-span export, so keep it at `info` or `debug` - `OTLP_OTLS_ENDPOINT` (optional) is an OTLP/gRPC collector URL (e.g. SigNoz, Jaeger) for span export, in any build [default: unset, no export] -- 2.54.0 From d29d3c0e9ba73711f54907396ed10e8d80febcf6 Mon Sep 17 00:00:00 2001 From: Cameron Cordes Date: Tue, 29 Sep 2026 20:43:20 -0400 Subject: [PATCH 2/2] docs(agents): labels must exist before tea can apply them MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The tracker doc said labels that don't exist are created on first use. They aren't: `tea issues create --labels` and `issues edit --add-labels` silently drop unknown names (the command succeeds, the issue stays unlabelled) — observed filing #151/#152 while the repo had no labels. Document creating them with `tea labels create` and checking the result. The five triage labels now exist on the server; the wayfinder:* family still has to be created before first use. Co-Authored-By: Claude Opus 5.5 --- docs/agents/issue-tracker.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/docs/agents/issue-tracker.md b/docs/agents/issue-tracker.md index 6a63ea0..f2c9db4 100644 --- a/docs/agents/issue-tracker.md +++ b/docs/agents/issue-tracker.md @@ -7,7 +7,8 @@ Issues and specs for this repo live as issues on Gitea - **Create an issue**: `tea issues create --title "..." --description-file -` (read the body from a heredoc on stdin), or `--description "..."` for a - one-liner. Add labels at creation with `--labels "..."`. + one-liner. Add labels at creation with `--labels "..."` (the labels + must already exist — see below). - **Read an issue**: `tea issues --comments`. Use `tea issues list -f index,title,body,labels,comments -o json` for machine-readable output. @@ -16,8 +17,16 @@ Issues and specs for this repo live as issues on Gitea - **Comment on an issue**: `tea comments add "..."` (alias: `tea comments "..."`). - **Apply / remove labels**: `tea issues edit --add-labels "..."` / - `--remove-labels "..."`. Labels that don't exist yet are created by the - server on first use. + `--remove-labels "..."`. +- **Labels must exist first.** Neither `issues create --labels` nor + `issues edit --add-labels` creates a missing label: an unknown name is + **silently dropped** — the command succeeds and the issue ends up + unlabelled (verified against this server, tea 0.16). Check with + `tea labels list`; create with + `tea labels create --name "..." --color "#rrggbb" --description "..."`, + then apply. After labelling, confirm it stuck (`tea issues `). + The triage labels (`triage-labels.md`) exist; the `wayfinder:*` labels + below must be created before first use. - **Close**: `tea issues close `. It does not accept a closing comment, so post the explanation first with `tea comments add "..."`, then close. -- 2.54.0