Record the 2026-10-19 lint decisions and the UPPER_SNAKE value rule in the agent notes

.agents/memory/bot-agents-migration-decisions.md

@@ -21,13 +21,11 @@ Node + Vite+ migration (PR #20, `node-migration`, 2026-10-15/16):
 - **Published lint plugins** (2026-10-18, after they reached npm):
   `eslint-plugin-import-structure` (`modules` config) and
   `eslint-plugin-explicit-types` (`concrete` and `absence` configs) are
-  devDependencies, enabled in `vite.config.ts`. explicit-types' `naming`
-  config is left off: its `upper-snake-string-unions` and
-  `no-upper-snake-object-keys` rules fire on wire tokens this repo does not
-  name (profile types such as `"claude"`, failure reasons posted to Gitea,
-  environment variable names), which cannot change without changing
-  behavior. Open question for the user. `eslint-plugin-lit-robust` does not apply
-  (no Lit).
+  devDependencies, enabled in `vite.config.ts` through their `all` configs.
+  `upper-snake-string-unions` was off while the user decided; since
+  2026-10-19 it is on and profile types, failure reasons, and anchor sides
+  are `UPPER_SNAKE` ([[enum-values-upper-snake]]). `eslint-plugin-lit-robust`
+  does not apply (no Lit).
 - **Stricter input checks were accepted** in the migration: Gitea `/user` and
   comment responses, the runtime manifest, and the outcome's profile type are
   validated; some type errors became `TypeError` with the same messages.