グカネータ作成 (#041) (#362)

Reviewed-on: #362
Co-authored-by: miteruzo <miteruzo@naver.com>
Co-committed-by: miteruzo <miteruzo@naver.com>

AGENTS.md

@@ -126,12 +126,16 @@ npm run preview
 - In TypeScript and TSX only, replace every leading run of 8 spaces with a tab.
 - Tabs are only for leading indentation, never for spaces after non-space text.
 - Do not add production dependencies without explicit approval.
+- 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.
 
 ## Backend rules
 
 - Inspect existing routes, controllers, models, services, and specs before
   editing backend behavior.
-- For API behavior changes, add or update request specs under `backend/spec/requests`.
+- For API behavior changes, add or update request specs under
+  `backend/spec/requests` only when the user explicitly asks for tests.
 - Prefer RSpec for new backend tests; existing minitest files under
   `backend/test` do not make minitest the default for new coverage.
 - Do not weaken authentication, BAN user checks, or IP BAN checks.
@@ -211,10 +215,11 @@ function PostFormTagsArea ({ tags, setTags }: Props) {
   `node_modules`, `dist`, `tmp`, `log`, and `storage` unless explicitly needed.
 - Before touching wiki, tag, versioning, BAN, IP BAN, or authentication
   behavior, inspect the related request specs and service objects.
-- If frontend code changes, run the existing frontend verification commands
-  that apply: `npm run build`, `npm run lint`, and `npm run test:run`.
-- If backend code changes, run the relevant RSpec command; for broad backend
-  changes, run `bundle exec rspec`.
+- If frontend code changes, run only non-test verification commands that
+  apply, such as `npm run build` and `npm run lint`. Run `npm run test:run`
+  only when the user explicitly asks for tests.
+- If backend code changes, do not run RSpec unless the user explicitly asks
+  for tests.
 - If a verification command cannot be run or fails, report the exact command and failure.
 
 ## Completion criteria
@@ -222,7 +227,8 @@ function PostFormTagsArea ({ tags, setTags }: Props) {
 A task is complete only when:
 
 - implementation is complete,
-- relevant verification commands pass, or failures are clearly explained,
+- relevant non-test verification commands pass, or failures are clearly
+  explained,
 - unrelated files are not changed,
 - migrations and schema are consistent when schema changes are made,
 - user-facing behavior is documented when needed.