From 603e01dec691af3ba8467cf68e9a1cd4e03692d3 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Tue, 31 Mar 2026 10:08:51 +0200 Subject: [PATCH] docs(claude): document sushi30 fork testing convention New fork-specific tests go in *_sushi30_test.go files so they survive upstream rebases without being silently overwritten. Co-Authored-By: Claude Sonnet 4.6 --- CLAUDE.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 5b3217052..c442f4002 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -84,6 +84,12 @@ Each **channel** (e.g. Telegram) receives messages and forwards them to the **ag Runtime config lives in `~/.picoclaw/workspace/config.json` (template: `config/config.example.json`). API keys can be injected via environment variables or stored encrypted in `.security.yml`. The `env://` scheme passes env var names directly as key values without encryption. +### Fork-specific testing conventions + +New functionality added in the `sushi30` fork **must be tested in isolated test files** named `*_sushi30_test.go`. This prevents upstream rebases from silently overwriting tests and makes fork additions easy to identify. + +Example: `pkg/config/resolve_key_sushi30_test.go` guards the `env://` fix in `resolveKey()`. + ### Frontend stack React 19 + Vite + TanStack Router + Tailwind CSS 4 + Radix UI + Jotai (state). Build output is embedded into the Go web backend binary via `go:embed`.