AGENTS.md: remember the e621 OpenAPI spec and the project constraints

Future sessions are told to fetch and grep https://e621.wiki/openapi.yaml before touching e621 endpoints, with the response-shape gotchas we hit (bare arrays vs wrapped objects, pool search parameters, the form-encoded PATCH for user settings). The durable constraints — token auth, no server-side media processing, no imgdd, no chat — are recorded too so a compacted session cannot regress them.
2026-09-17 22:03:09 -05:00
parent a152063d76
commit 1053e3ee55
2 changed files with 32 additions and 0 deletions
@@ -161,3 +161,6 @@ Files now stage first and are resolved before entering the library.
 - IQDB and e621 matching depend on e621 credentials being configured; the SPA
  talks to e621 directly for browsing, while the backend e621 client
  (`apps/library/e621.py`) handles metadata matching and batch scans.
+- Anything touching e621 endpoints follows the OpenAPI spec
+  (https://e621.wiki/openapi.yaml) — see AGENTS.md for how to fetch and
+  which response shapes to watch out for.