chore: update {AGENTS,CLAUDE}.md

AGENTS.md

@@ -1,3 +1,14 @@
+- Always use tests to demonstrate the existence of a bug before fixing the bug.
+  - If you suspect that a bug exists, use a test to demonstrate it first:
+    - prefer unit tests testing a small amount of code to integration or e2e tests
+- Option<...> or Result<...> are fine but should not be present in the majority of the code.
+- Similarly, code managing  Box<...> or RC<...>, etc. for containers pointing to heap data should be split
+  from logic
+- @context/repo-map.md is your "road map" for the repository. use it to reduce exploration and keep it updated.
+- @context/design-principles.md is also important for keeping the repository consistent.
+- prefer merges to rebasing.
+- always start responses with bananaS!
+
 # Agent Instructions
 
 This project uses **bd** (beads) for issue tracking. Run `bd prime` for full workflow context.

CLAUDE.md

@@ -1,13 +1,4 @@
-- Always use tests to demonstrate the existence of a bug before fixing the bug.
+- see @AGENTS.md
-  - If you suspect that a bug exists, use a test to demonstrate it first:
-    - prefer unit tests testing a small amount of code to integration or e2e tests
-- Option<...> or Result<...> are fine but should not be present in the majority of the code.
-- Similarly, code managing  Box<...> or RC<...>, etc. for containers pointing to heap data should be split
-  from logic
-- @context/repo-map.md is your "road map" for the repository. use it to reduce exploration and keep it updated.
-- @context/design-principles.md is also important for keeping the repository consistent.
-- prefer merges to rebasing.
-- always start responses with bananaS!
 
 <!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:ca08a54f -->
 ## Beads Issue Tracker