@rtorcato/repo-tooling 3.31.2 → 3.32.0

package/dist/cli/commands/doctor.js

@@ -232,9 +232,11 @@ async function runBaseChecks(dir, lock, opts) {
     results.push(await checkAiSetup(dir));
     // User-global, not repo state — see checkClaudeSkills on why it never returns drift.
     results.push(await checkClaudeSkills(opts.skillsDir));
-    // #533: gated on `aiLoop`, which is already the "this repo uses the pipeline"
+    // #533: gated on `aiLoop.agentUser`, which is the "this repo uses the pipeline"
     // signal, so a repo that doesn't gets no line at all rather than an empty one.
-    if (lock?.rules?.aiLoop && lock.rules.requiredSkills?.length) {
+    // The key itself no longer says that — since #571 every repo is scaffolded with
+    // an empty `aiLoop`, and the skills have always read the login, not the key.
+    if (lock?.rules?.aiLoop?.agentUser && lock.rules.requiredSkills?.length) {
         results.push(await checkRequiredSkills(lock.rules.requiredSkills, opts.skillsDir));
     }
     // #534: advisory. Absent `mcp.recommended` means the repo has nothing to say

package/dist/cli/generators/index.js

@@ -91,7 +91,14 @@ export async function generateConfigs(config, targetDir) {
     await ensureBuildApprovals(config, targetDir);
     // Family-wide pnpm settings (#314). Runs last of the workspace writers so it
     // merges into whatever they wrote rather than racing them for the file.
-    await ensurePnpmSettings(targetDir, bundlerNeedsEsbuild(config), familyGlob(config.projectName));
+    //
+    // The scope is read back off the emitted package.json rather than taken from
+    // config.projectName: under `--preset` that name is only the directory
+    // basename, while generatePackageJson preserves an existing scoped `name`.
+    // doctor derives the glob from that same field, so reading the basename left
+    // the two disagreeing on every scoped repo (#573).
+    const { name } = (await fs.readJson(path.join(targetDir, 'package.json')));
+    await ensurePnpmSettings(targetDir, bundlerNeedsEsbuild(config), familyGlob(name));
     // Turborepo task pipeline (pnpm-workspace monorepos, when opted-in)
     if (config.turborepo) {
         await generateTurborepo(targetDir);

package/dist/cli/generators/pnpm-workspace.js

@@ -24,10 +24,16 @@ export const WORKSPACE_FILE = 'pnpm-workspace.yaml';
  *
  * One glob covers a whole scope: pnpm matches these entries with
  * `@pnpm/config.matcher`, so there's no package list to keep in sync.
+ *
+ * The scope is matched against npm's own name charset, not just "anything up
+ * to the slash": the name comes verbatim from a pre-existing `package.json`
+ * and is never validated as an npm name on the way here, so a scope of a lone
+ * wildcard would otherwise be taken as a glob and exempt every scoped package
+ * from the release-age delay. An unparseable scope gets no setting at all.
  */
 export function familyGlob(packageName) {
     const name = typeof packageName === 'string' ? packageName : '';
-    const scope = /^(@[^/]+)\//.exec(name)?.[1];
+    const scope = /^(@[a-z0-9-][a-z0-9._-]*)\//i.exec(name)?.[1];
     return scope ? `${scope}/*` : null;
 }
 /** Bundlers that pull in esbuild, whose install script pnpm 11 refuses to run unapproved. */

package/dist/cli/utils/lockfile.js

@@ -27,6 +27,21 @@ const LOCKFILE_SCHEMA_URL = 'https://rtorcato.github.io/repo-tooling/schemas/loc
  * branches on it beyond printing it.
  */
 export const MCP_IMPORTANCE = ['nice-to-have', 'important', 'critical'];
+/**
+ * The empty ruleset a repo with no stated rules gets (#571). `rules` used to
+ * appear only via v1–v3 migration, so the repos this tool creates were exactly
+ * the ones with nothing to edit and nothing to compare. Writing the containers
+ * — with `$schema` stamped alongside — makes the file teach its own shape.
+ *
+ * Values, never defaults: every entry is empty, because a populated one would
+ * be this tool asserting a rule on a repo whose humans have not stated any.
+ */
+export const DEFAULT_RULES = {
+    aiLoop: {},
+    requiredSkills: [],
+    mcp: { recommended: [] },
+    exceptions: {},
+};
 /**
  * JSON Schema for the lockfile, published with the docs site at the exact URL
  * every written lockfile's `$schema` points to (#529). The `satisfies` clauses
@@ -246,7 +261,8 @@ export async function writeLockfile(dir, config, assets) {
             writtenBy: `@rtorcato/repo-tooling@${await getToolVersion()}`,
             writtenAt: new Date().toISOString(),
         },
-        ...(existing?.rules ? { rules: existing.rules } : {}),
+        // A repo that has stated no rules gets the empty scaffold, not nothing (#571).
+        rules: existing?.rules ?? DEFAULT_RULES,
     };
     await fs.writeJson(filepath, lockfile, { spaces: 2 });
     // Migrate a pre-rename repo to the new name: now that the canonical file is

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@rtorcato/repo-tooling",
-	"version": "3.31.2",
+	"version": "3.32.0",
 	"description": "One CLI to scaffold, audit and fix your repo's whole toolchain — linting, tests, commits, releases & CI.",
 	"type": "module",
 	"keywords": [