@jterrazz/test 18.0.2 → 18.0.3

package/dist/checker.js

@@ -3787,14 +3787,15 @@ function configIn(directory, names) {
 	const name = names.find((candidate) => existsSync(join(directory, candidate)));
 	return name === void 0 ? void 0 : join(directory, name);
 }
-/** The outermost of each subtree, which covers the ones inside it. */
+/** The outermost of each subtree, which covers the ones inside it, found as git lists the tree, so a folder git ignores is never entered and a config inside it never loaded. */
 function nestedConfigDirectories(root) {
 	const found = [];
 	const walk = (directory) => {
-		for (const entry of readdirSync(directory, { withFileTypes: true })) {
+		for (const entry of treeEntries(directory)) {
 			if (!entry.isDirectory() || UNWALKED.has(entry.name)) continue;
 			const path = join(directory, entry.name);
-			if (NESTED_CONFIG_NAMES.some((name) => existsSync(join(path, name)))) found.push(relative(root, path));
+			const names = treeNames(path);
+			if (NESTED_CONFIG_NAMES.some((name) => names.includes(name))) found.push(relative(root, path));
 			else walk(path);
 		}
 	};

package/docs/reference/linting.md

@@ -417,7 +417,7 @@ This package records and judges its consumers' debt. The family keeps one tracke
 
 - **It re-records both falls** (lowering an entry or dropping it) before it judges.
 - **It runs the plugin's own autofixes first**, after its own rewrites and movers: the project's oxlint, under a wrapper of its root config that arms the `jterrazz/*` rules alone, in that config and in every config it extends: a plugin armed through `extends` keeps its fixes, and a JSON config, `.jsonc` or extended, is read as oxlint reads it, comments and trailing commas allowed. So no other rulebook's fixer writes a byte, and the ratchets count the checker's findings and the plugin's diagnostics over the one tree they leave: one `typescript fix` settles a diagnostic its fix writes (`no-repeated-chain-setting`'s view, `one-describe-per-file`'s describe, `expected-constant-shared`'s shared expectation).
-- **A nested oxlint config gets a run of its own**, under the same wrapper of ITS config: a config handed with `-c` turns oxlint's nested discovery off, so the root's run leaves the subtree alone rather than write where another config governs, and the subtree's run fixes it by the config the ratchet's count judges it by.
+- **A nested oxlint config gets a run of its own**, under the same wrapper of ITS config: a config handed with `-c` turns oxlint's nested discovery off, so the root's run leaves the subtree alone rather than write where another config governs, and the subtree's run fixes it by the config the ratchet's count judges it by. The configs are found as `typescript check` lists the tree, through git: a folder git ignores is never entered, so a config below it, a clone under a sealed workbench, is never loaded.
 - **A config oxlint could not load under the wrapper stops `typescript fix`**, naming it: oxlint exits 1 for it as for diagnostics left, and a pass that read it as the latter would have fixed nothing and said nothing.
 
 #### Which run owns the verdict

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@jterrazz/test",
-    "version": "18.0.2",
+    "version": "18.0.3",
     "description": "Declarative testing framework for HTTP APIs, CLIs, background jobs, websites, mobile apps, rendered components and the rules a project ships: one entry point, real infrastructure and a real browser, golden-file assertions, plus an oxlint convention plugin.",
     "keywords": [
         "api-testing",