From 41dbefe55218c61f7ddef364d970af379374c934 Mon Sep 17 00:00:00 2001 From: ekklesia Date: Tue, 13 Oct 2026 22:58:32 -0500 Subject: [PATCH] docs(claude): file an issue for what you find outside the task Findings that only live in a chat reply get lost. Agents now open a descriptive issue in the repository a problem belongs to (after searching for an existing one), mark it found-by-claude, leave it unassigned, and list what they filed when they report back. Co-Authored-By: Claude Opus 5.5 --- CLAUDE.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index d959dec..2bb21ff 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -64,6 +64,13 @@ decision gets a new ADR that supersedes the old one; never rewrite a historical with the compatibility boundary explicit. Do not copy platform logic into Signage to avoid it. - Every defect fix gets a regression test. Signage never reads the environment, opens its own socket, builds an Ekklesia URL, or applies a migration; all of that reaches it through the host. +- Report what you find. A defect, flaky test, documentation/ADR conflict, or CI problem outside the + task at hand gets an issue in the repository it belongs to (here or `Zayin/Ekklesia`), as soon as + you find it. Search for an existing issue first; something fixed in the same PR goes in that PR's + description instead. Be descriptive: what you saw, the evidence (run and job links, commit, file + and line), how to reproduce it, the impact, and options, and never a secret. Label it + `found-by-claude` (an agent that cannot apply labels ends the body with a line saying so), leave + it unassigned, and list what you filed when you report back. ## Verification