Use the unscoped eslint-plugin names in the notes

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

@@ -1,5 +1,5 @@
 ---
-description: bot-agents migration decisions: live @main action for six repos, JSON profiles, Node 24.2+, Deno kept only for agents, no @cunarist plugins needed
+description: bot-agents migration decisions: live @main action for six repos, JSON profiles, Node 24.2+, Deno kept only for agents, no eslint-plugin-* packages needed
 ---
 
 Decisions for `commons/bot-agents` (Capsulizers Gitea), from the Deno to
@@ -22,10 +22,13 @@ Node + Vite+ migration (PR #20, `node-migration`, 2026-10-15/16):
   because the agents still check Deno-based consumer repos (memona,
   memona-home). Remove it once those repos have moved; it is not a
   dependency of this repo's TypeScript.
-- **No `@cunarist/eslint-plugin-*`.** The Deno setup enabled no plugin, so
-  this repo depends on none and CI passes without them being published.
-  Planned (2026-10-17): once the plugins are on npm, add
-  `@cunarist/eslint-plugin-modules` here for its import checks.
+- **No `eslint-plugin-*` packages** (`eslint-plugin-explicit-types`,
+  `eslint-plugin-import-structure`, `eslint-plugin-lit-robust`; unscoped
+  since 2026-10-18, formerly `@cunarist/...`). The Deno setup enabled no
+  plugin, so this repo depends on none and CI passes without them being
+  published. Planned (2026-10-17): once the plugins are on npm, add
+  `eslint-plugin-import-structure` (rule prefix `import-structure/`) here for
+  its import checks.
 - **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.