@miroshnik/elves 2026.1026.0 → 2026.1026.1

package/dist/spec/scripts/eslint-config.js

@@ -2,7 +2,7 @@
 import { readdirSync } from "node:fs";
 import path from "node:path";
 import { pathToFileURL } from "node:url";
-var FRAGMENT = new Set(["eslint.ts", "eslint.mts", "eslint.mjs", "eslint.js"]);
+var FRAGMENT = /^(?:[^.]+\.)?eslint\.(?:ts|mts|mjs|js)$/;
 var SKIP = new Set(["node_modules", ".git"]);
 var SKIP_REL = new Set(["tests/lib"]);
 function eslintFragments(root, dirs = ["tests"]) {
@@ -19,7 +19,7 @@ function eslintFragments(root, dirs = ["tests"]) {
       if (e.isDirectory()) {
         if (!SKIP.has(e.name) && !SKIP_REL.has(path.relative(root, full).split(path.sep).join("/")))
           walk(full);
-      } else if (FRAGMENT.has(e.name))
+      } else if (FRAGMENT.test(e.name))
         out.push(full);
     }
   };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@miroshnik/elves",
-  "version": "2026.1026.0",
+  "version": "2026.1026.1",
   "type": "module",
   "description": "Elves — a development flow with AI agents: shared rules and skills for any agent; install — bunx @miroshnik/elves install -g; the installer and skill scripts — TypeScript under Bun, tests — bun test in tests/",
   "repository": {
@@ -72,5 +72,5 @@
     "eslint-plugin-boundaries": "^7.2.0",
     "knip": "^6.41.0"
   },
-  "gitHead": "c5e6bd32225415d44c4e961766e72a639142fd1e"
+  "gitHead": "6c5389f526d10b2b11b78bd6a8bdb6d31a6821a9"
 }

package/skills/spec/SKILL.md

@@ -183,7 +183,7 @@ each one — `checks.md` next to this file:
 
 - a convention on every item of a registry from the code — `invariant`
   (`standards/<name>/`);
-- a lint rule — `examples`, `eslintLinter`, the folder's `eslint.ts` fragment
+- a lint rule — `examples`, `eslintLinter`, an `eslint.ts` or `<section>.eslint.ts` fragment
   collected by `collectEslint`;
 - out of scope and exceptions — `fileOf`, marks `spec-outside(<decision>)` /
   `spec-exception(<decision>) #N`, `exceptionsIn()`, `lintExceptions`;

package/skills/spec/canon.md

@@ -44,8 +44,8 @@ no decision claims is dead and is deleted.
   - a topic of one section has the same anatomy — `<topic>.md` and a section
     with a name of its own; a test file named after its folder
     (`<name>/<name>.test.ts`) is a decision not regrouped yet;
-  - the mechanism — in the same folder: an `eslint.ts` fragment, an ast-grep
-    `rule.yml`. The project's tool configs (`eslint.config.*`, `sgconfig.yml`)
+  - the mechanism — in the same folder: an ESLint fragment (the topic's
+    `eslint.ts`, a section's `<section>.eslint.ts`), an ast-grep `rule.yml`. The project's tool configs (`eslint.config.*`, `sgconfig.yml`)
     only collect them from the tree (the harness's `collectEslint`) — a rule
     has one home;
   - `exceptions/<section>/` — exceptions for elements without a file of their

package/skills/spec/checks.md

@@ -7,8 +7,8 @@ Which check for what:
 | What to check | With what | Where in `tests/` |
 |---|---|---|
 | A convention on every item of a registry from the code ("every mutation writes an audit record") | `invariant` | `standards/<name>/` |
-| A lint rule: «not allowed», «allowed», «outside scope» | `examples`, `eslintLinter` | `standards/<name>/` + an `eslint.ts` fragment |
-| An ESLint rule in a standard's folder | `collectEslint` in `eslint.config.*` | the tree's `eslint.ts` fragments |
+| A lint rule: «not allowed», «allowed», «outside scope» | `examples`, `eslintLinter` | `standards/<topic>/` + an ESLint fragment (`eslint.ts`, `<section>.eslint.ts`) |
+| An ESLint rule in a standard's folder | `collectEslint` in `eslint.config.*` | the tree's `eslint.ts` and `<section>.eslint.ts` fragments |
 | Out of scope and an item's exception with its own file | `fileOf` in `invariant`; a mark `spec-outside(<decision>)` / `spec-exception(<decision>) #N` in the file (`marksIn`), in JSON — the value of the `"//"` key | the item's file (a route, a script, a migration, a workspace package's `package.json`) |
 | Exceptions with a ratchet | `exceptionsIn()` → `exceptions` in `invariant`; a disable `-- #N reason` + `lintExceptions` | the decision folder's `exceptions/<item>.json`; migration — `spec-exceptions` |
 | Architecture model: module boundaries, directories, packages | `boundariesConfig`, `architecture` | `architecture/model.ts`, `architecture/<name>/` |
@@ -142,7 +142,8 @@ Biome will be added when a project needs them (the core doesn't depend on the
 linter, `Linter` is an interface with one required method, `lint`).
 
 **A rule lives in its standard's folder.** A flat config fragment is
-`eslint.ts` next to the test (`export default [{ files: ["src/domain/**"],
+the topic's `eslint.ts` or a section's `<section>.eslint.ts` — each standard
+of a topic keeps its own — next to the test (`export default [{ files: ["src/domain/**"],
 rules: {…} }]`, paths from the project root); the project's `eslint.config.*`
 only collects the tree's fragments — `lint` and the editor see the rule as
 usual:
@@ -168,7 +169,9 @@ export default restrict({ id: "no-alert", selectors: ["CallExpression[callee.nam
 
 A fragment is `eslint.ts`, `eslint.mts` (ESM even in a project without
 `"type": "module"`, without the `MODULE_TYPELESS_PACKAGE_JSON` warning),
-`eslint.mjs` or `eslint.js`; `tests/lib` holds helpers, not fragments.
+`eslint.mjs` or `eslint.js`, a section's — the same under its prefix
+(`<section>.eslint.mts`); a knip entry for the fragments —
+`tests/**/*eslint.{ts,mts}`; `tests/lib` holds helpers, not fragments.
 
 **Exceptions are explicit, have a task, and go away when no longer needed.**
 

package/skills/spec/migration.md

@@ -143,7 +143,7 @@ a flat decision as a topic of one section. One task, one PR, in this order:
    `<topic>/<name>.md` (the other `<name>.*` files alongside), another test
    file of the folder `<name>/<file>.test.ts` → `<topic>/<name>.<file>.test.ts`
    (by its own name it would be a section of its own), a helper file under the
-   section's prefix (`<name>.preload.ts`), `<name>/exceptions/*.json` → `<topic>/exceptions/<name>/`, a package
+   section's prefix (`<name>.preload.ts`, the ESLint fragment `<name>/eslint.ts` → `<topic>/<name>.eslint.ts`), `<name>/exceptions/*.json` → `<topic>/exceptions/<name>/`, a package
    subfolder `<name>/<package>/` → `<topic>/<package>/`. The moves go in a
    commit of their own, without content edits, so history follows the files
    and `pr labels` reads them as mechanical. Each topic gets `<topic>.md`: its

package/skills/spec/scripts/eslint-config.ts

@@ -1,7 +1,8 @@
 /**
- * eslint-config — assembling ESLint rules from the spec tree: a standard's rule lives as an `eslint.ts` fragment
- * (default — a flat config object or array) in its folder, next to the examples and the reason, and the project's
- * `eslint.config.*` only collects the fragments — `lint` and the editor see the rule as usual:
+ * eslint-config — assembling ESLint rules from the spec tree: a standard's rule lives as a fragment (default — a flat
+ * config object or array) in its topic folder, next to the examples and the reason — the topic's `eslint.ts` or a
+ * section's `<section>.eslint.ts`, so each standard of a topic keeps its own —, and the project's `eslint.config.*`
+ * only collects the fragments — `lint` and the editor see the rule as usual:
  *
  *   import { collectEslint } from "@miroshnik/elves/spec/eslint-config";
  *   export default [...base, ...(await collectEslint(import.meta.dirname))];
@@ -20,12 +21,13 @@ import { readdirSync } from "node:fs";
 import path from "node:path";
 import { pathToFileURL } from "node:url";
 
-const FRAGMENT = new Set(["eslint.ts", "eslint.mts", "eslint.mjs", "eslint.js"]);
+/** A topic's fragment `eslint.ts` or a section's `<section>.eslint.ts` (`.mts`, `.mjs`, `.js` too). */
+const FRAGMENT = /^(?:[^.]+\.)?eslint\.(?:ts|mts|mjs|js)$/;
 const SKIP = new Set(["node_modules", ".git"]);
 // test helpers, not the spec: `spec-doc` skips them too
 const SKIP_REL = new Set(["tests/lib"]);
 
-/** Paths of `eslint.ts` fragments in the directories (by default `tests/`), in order. */
+/** Paths of the topics' `eslint.ts` and the sections' `<section>.eslint.ts` fragments in the directories (by default `tests/`), in order. */
 export function eslintFragments(root: string, dirs: string[] = ["tests"]): string[] {
   const out: string[] = [];
   const walk = (dir: string): void => {
@@ -39,7 +41,7 @@ export function eslintFragments(root: string, dirs: string[] = ["tests"]): strin
       const full = path.join(dir, e.name);
       if (e.isDirectory()) {
         if (!SKIP.has(e.name) && !SKIP_REL.has(path.relative(root, full).split(path.sep).join("/"))) walk(full);
-      } else if (FRAGMENT.has(e.name)) out.push(full);
+      } else if (FRAGMENT.test(e.name)) out.push(full);
     }
   };
   for (const d of dirs) walk(path.join(root, d));
@@ -67,7 +69,7 @@ const SPEC_PLUGIN: { meta: { name: string }; rules: Record<string, object> } = {
 
 /**
  * A standard's ban by AST selectors (as in `no-restricted-syntax`) — as its own rule `spec/<id>` in the shared `spec`
- * plugin: bans of different standards on the same files all apply. A standard's `eslint.ts` fragment:
+ * plugin: bans of different standards on the same files all apply. A standard's fragment (`eslint.ts`, `<section>.eslint.ts`):
  *
  *   export default restrict({ id: "no-alert", selectors: ["CallExpression[callee.name='alert']"], message: "…", files: ["src/**"] });
  */