@timekast/factory 0.1.8 → 0.1.9

package/dist/commands/add.js

@@ -9,10 +9,15 @@
  * Invariants:
  *   - `add` ONLY ever installs `core`. The profile is the literal `PROFILES.core`,
  *     never a flag — `full` is structurally unreachable from this command.
- *   - `add` never touches `src/`, `package.json`, `pj-*`, or any file outside the
- *     `core` manifest. The `core` tarball contains only `core` files, so moving
- *     its contents in cannot reach dev-owned paths; files in the cwd that are not
- *     in the tarball are left byte-identical.
+ *   - `add` never touches `src/`, `pj-*`, or any file outside the `core` manifest.
+ *     The `core` tarball contains only `core` files, so moving its contents in
+ *     cannot reach dev-owned paths; cwd files not in the tarball stay byte-identical.
+ *     ONE surgical exception (H5): if the repo is a Node project — a `package.json`
+ *     sits next to the installed `.claude/` — `add` inserts the `factory:update`
+ *     script (a single key, never overwriting a divergent value) so the dev gets
+ *     `pnpm factory:update`, matching the `full` profile. A non-Node repo
+ *     (Python/Flutter/Go) gets NO `package.json` created — it updates via
+ *     `npx @timekast/factory update` (or a global install of the CLI).
  *   - `add` overwrites manifest files without prompting — the conflict prompt is
  *     exclusive to `update` (DIST-005). Documented in the command's `--help`.
  *   - Atomicity (§7.5): extract + validate in a temp dir before touching the cwd;
@@ -20,12 +25,13 @@
  *
  * Expected failures throw `CLIError`; the top-level handler prints + exits.
  */
-import { mkdtempSync, rmSync } from 'node:fs';
+import { existsSync, mkdtempSync, rmSync } from 'node:fs';
 import { tmpdir } from 'node:os';
 import path from 'node:path';
 import { CLIError } from '../lib/cli-error.js';
 import { PROFILES } from '../lib/constants.js';
 import { writeInitialLockfile } from '../lib/lockfile.js';
+import { insertFactoryUpdateScript } from '../lib/package-json.js';
 import { runPreflight } from '../lib/preflight.js';
 import { detectRepo } from '../lib/repo-detection.js';
 import { downloadProfileTarball, moveContentsInto, stageProfileTarball } from '../lib/unpack.js';
@@ -74,5 +80,29 @@ export async function runAdd() {
         process.removeListener('SIGTERM', onSignal);
         cleanup();
     }
+    // H5: if the repo is a Node project, add the `pnpm factory:update` convenience by
+    // surgically inserting the script into the EXISTING package.json. Non-fatal — a
+    // missing/invalid package.json just means the dev uses `npx` (the brain is already
+    // installed). We NEVER create a package.json in a non-Node repo.
+    const pkgPath = path.join(cwd, 'package.json');
+    let scriptAction = 'none';
+    if (existsSync(pkgPath)) {
+        try {
+            scriptAction = insertFactoryUpdateScript(pkgPath).action;
+        }
+        catch {
+            scriptAction = 'none'; // invalid package.json — skip the alias, brain still installed
+        }
+    }
     console.log('\n✔ Cerebro `core` instalado. Lockfile escrito en `.timekast/lockfile.json`.');
+    if (scriptAction === 'added' || scriptAction === 'already-correct') {
+        console.log('Para actualizar: `pnpm factory:update` (alias de `npx @timekast/factory update`).');
+    }
+    else {
+        if (scriptAction === 'conflict') {
+            console.warn('Aviso: `factory:update` ya existe en package.json con otro valor; no se sobrescribió.');
+        }
+        console.log('Para actualizar: `npx @timekast/factory update` desde la raíz del repo,');
+        console.log('o instala el CLI una vez (`npm i -g @timekast/factory`) y corre `factory update`.');
+    }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timekast/factory",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "Public, thin CLI to bootstrap and maintain TimeKast Factory derived projects.",
   "type": "module",
   "license": "UNLICENSED",