#41

backend/AGENTS.md

@@ -47,6 +47,10 @@ bundle exec rspec
 
 If a command cannot be run or fails, report the exact command and failure.
 
+Do not create, modify, or run tests unless the user explicitly asks for test
+work. When the user asks for tests, keep working and rerun them until they
+pass or the remaining failure is clearly blocked.
+
 ## Rails structure
 
 - `app/controllers`: API controllers.
@@ -116,7 +120,8 @@ service, representation, and spec.
 - `User#banned?` and `IpAddress#banned?` check `banned_at.present?`.
 - Do not weaken BAN or IP BAN behavior.
 - If changing request authentication or controller before actions, add or
-  update request specs covering banned users and banned IP addresses.
+  update request specs covering banned users and banned IP addresses only when
+  the user explicitly asks for tests.
 
 ## RSpec
 
@@ -130,8 +135,9 @@ service, representation, and spec.
 - `AuthHelper#sign_in_as(user)` stubs
   `ApplicationController#current_user`; use it when matching existing
   request spec style.
-- Add or update request specs for API behavior changes, especially status
-  codes, permissions, response shape, and version conflict behavior.
+- Add or update request specs for API behavior changes only when the user
+  explicitly asks for tests, especially status codes, permissions, response
+  shape, and version conflict behavior.
 
 ## Migrations
 
@@ -164,7 +170,8 @@ service, representation, and spec.
   the record `version_no`.
 - Do not update versioned records without considering whether a version snapshot must be created.
 - For optimistic concurrency paths, preserve `base_version_no`, `force`, and
-  `merge` semantics and cover conflicts in request specs.
+  `merge` semantics. Cover conflicts in request specs only when the user
+  explicitly asks for tests.
 
 ## Domain cautions