From b06d01e09e272f9ed8ee16899f41ec02c3a62269 Mon Sep 17 00:00:00 2001
From: Harrison Weinstock <hkobew@amazon.com>
Date: Fri, 8 May 2026 13:10:04 +0000
Subject: [PATCH 1/2] docs: add AGENTS.md and testing anti-patterns section

---
 AGENTS.md  | 6 ++++++
 TESTING.md | 4 ++++
 2 files changed, 10 insertions(+)
 create mode 100644 AGENTS.md

diff --git a/AGENTS.md b/AGENTS.md
new file mode 100644
index 00000000..f34b7bca
--- /dev/null
+++ b/AGENTS.md
@@ -0,0 +1,6 @@
+# Agents
+
+## Useful Resources
+
+- [TESTING.md](TESTING.md)
+- [CONTRIBUTING.md](CONTRIBUTING.md)
diff --git a/TESTING.md b/TESTING.md
index 5cc9cd45..02a3bbad 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -87,3 +87,7 @@ Stream delivery tests fail in CI unless `MEMORY_KINESIS_ARN` and `MEMORY_ROLE_AR
 - Each test class should correspond to the object under test (e.g. `TestMemoryClient`).
 - Expensive resources (e.g. memories) should be created the minimum number of times, ideally once in `setup_class`.
 - All resources created during tests must be cleaned up in `teardown_class`.
+
+## Anti-Patterns
+
+**Excessive mocking.** Over-mocking weakens correctness guarantees and couples tests to implementation details. Functionality that requires mocking should have integration or e2e test coverage.
\ No newline at end of file

From 1d62d1f22647ae55b775aa62e99e513e3ac519ac Mon Sep 17 00:00:00 2001
From: Harrison Weinstock <hkobew@amazon.com>
Date: Fri, 8 May 2026 13:23:59 +0000
Subject: [PATCH 2/2] docs: fix lint and formatting

---
 TESTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/TESTING.md b/TESTING.md
index 02a3bbad..d900d3ac 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -90,4 +90,4 @@ Stream delivery tests fail in CI unless `MEMORY_KINESIS_ARN` and `MEMORY_ROLE_AR
 
 ## Anti-Patterns
 
-**Excessive mocking.** Over-mocking weakens correctness guarantees and couples tests to implementation details. Functionality that requires mocking should have integration or e2e test coverage.
\ No newline at end of file
+**Excessive mocking.** Over-mocking weakens correctness guarantees and couples tests to implementation details. Functionality that requires mocking should have integration or e2e test coverage.