Prune migration notes and align the notes with the current lint setup

.agents/memory/package-json-shape.md

@@ -1,32 +1,13 @@
 ---
-description: package.json key order is metadata, scripts, exports, imports, devDependencies, dependencies; standard fields only; no peerDependencies or packageManager
+description: package.json keys follow Oxfmt's standard order (vp check --fix); standard fields only; no peerDependencies or packageManager
 ---
 
-## Key order (2026-10-14)
+## Key order (2026-10-16)
 
-Metadata first, then `scripts`, `exports`, `imports`, `devDependencies`,
-`dependencies`. Oxfmt would re-sort the file, so `vite.config.ts` sets
-`fmt: { sortPackageJson: false }`; keep it, and keep the order by hand.
-
-```jsonc
-{
-  "name": "@cunarist/eslint-plugin-x",
-  "version": "0.1.0",
-  "description": "...",
-  "keywords": ["eslint", "eslint-plugin", "eslintplugin", "oxlint"],
-  "license": "MIT",
-  "repository": { "type": "git", "url": "git+https://github.com/..." },
-  "type": "module",
-  "files": ["dist"],
-  "engines": { "node": ">=22" },
-  "eslint-doc-generator": {/* tool options that can only live here */},
-  "scripts": { "docs": "eslint-doc-generator" },
-  "exports": { ".": "./dist/index.js" },
-  "imports": { "#helpers": "./src/helpers/index.ts" },
-  "devDependencies": { "vite-plus": "^1.1.0" },
-  "dependencies": {},
-}
-```
+Oxfmt's standard `package.json` sorting is accepted: there is no
+`fmt: { sortPackageJson: false }`, and `vp check --fix` sets the order. This
+replaces the earlier hand-written order (metadata, `scripts`, `exports`,
+`imports`, `devDependencies`, `dependencies`).
 
 The `imports` key order can carry meaning: import-check's
 `enforce-layer-order` reads it as the layer order. Never reorder it casually.