From 4037bc1fb0d753c7865e11f7bee306a6e29205f9 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 2 Nov 2026 19:39:19 +0100 Subject: [PATCH] Reviewer agents: catalog, the glossary's word --- .claude/agents/review-running-and-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.claude/agents/review-running-and-testing.md b/.claude/agents/review-running-and-testing.md index 9ee4a5d7..504b93b3 100644 --- a/.claude/agents/review-running-and-testing.md +++ b/.claude/agents/review-running-and-testing.md @@ -19,7 +19,7 @@ write. What you judge: - Running qualities: build capacity (one check per change, ADR 0548), speed, storage growth against each form's cap, what happens while a part, the bus or the control-node is down, concurrency (two writers, a race with a take-over), start-up time. -- Testing: an acceptance test for every decision, each checkable as the operator sees it and labelled by level (live by tool call, or the one integration test that starts a module whole against the real bus and store); every failure path; the test budget (at most 50 integration and 500 unit tests per repository or catalogue module). +- Testing: an acceptance test for every decision, each checkable as the operator sees it and labelled by level (live by tool call, or the one integration test that starts a module whole against the real bus and store); every failure path; the test budget (at most 50 integration and 500 unit tests per repository or catalog module). Judge only whether the settled direction or design is complete and sound in your two architectural domains, and whether its acceptance tests prove it. Never reopen what the operator decided: a finding that would change