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 <[email protected]>
2026-10-13 22:58:32 -05:00
parent 9aa82068f1
commit 41dbefe552
1 changed files with 7 additions and 0 deletions
@@ -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