@seoagent-official/seoagent 1.42.1 → 1.42.2

package/README.md

@@ -35,27 +35,21 @@
 
 ---
 
-> **This package is a scaffolder, not a runtime dependency.** Both forms below do the same thing — scaffold `.seoagent/` + the Claude Code skill in your repo. You don't need to keep it in `package.json` after init runs.
+> **This package is a one-shot scaffolder, not a runtime dependency.** Run `init` once to scaffold `.seoagent/` + the Claude Code skill in your repo. Nothing to keep in `package.json` afterwards. No `postinstall` script — installs are silent and play nicely with npm 11+.
 
 ## Install
 
-**Pick either form. Both work the same:**
-
 ```bash
-# Preferred — no package.json bloat:
 npx -y @seoagent-official/seoagent init
-
-# Also works — `npm install` runs `init` automatically via postinstall:
-npm install @seoagent-official/seoagent
 ```
 
-Either way, the scaffolder will:
+The scaffolder will:
 - Scan your repo for `package.json` `homepage` field + common `.env` files (`NEXT_PUBLIC_SITE_URL`, `SITE_URL`, etc.) to infer your domain
 - Create `.seoagent/` with `project.md`, `context.md`, and folders for audits, briefs, content
 - Install the skill at `.claude/skills/seoagent/SKILL.md` so Claude Code picks it up
 - Add a `PostToolUse` hook to `.claude/settings.json` so edits to `.seoagent/` auto-sync to the cloud (when you're logged in)
 
-After init runs, you can remove `@seoagent-official/seoagent` from `package.json` — the scaffolded sync hook uses `npx -y @seoagent-official/seoagent sync --silent` so the package is fetched on-demand from then on.
+The scaffolded sync hook uses `npx -y @seoagent-official/seoagent sync --silent` so the package is fetched on demand from then on — no `package.json` entry needed.
 
 Then open Claude Code in this repo and say *"audit my site."* The skill takes it from there.
 
@@ -70,19 +64,6 @@ Then open Claude Code in this repo and say *"audit my site."* The skill takes it
 npx -y @seoagent-official/seoagent init --yes --domain example.com
 ```
 
-### Skip the auto-init on `npm install`
-
-If you really want to install the package without scaffolding:
-
-```bash
-SEOAGENT_SKIP_AUTOINIT=1 npm install @seoagent-official/seoagent
-```
-
-You'd want this only when running `init` manually with custom flags. The auto-init also skips automatically when:
-- `CI=true` (or `CI=1`)
-- The package is being installed globally (`npm install -g`)
-- `.seoagent/project.md` already exists in the repo
-
 ### Optional: install globally for a bare `seoagent` command
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seoagent-official/seoagent",
-  "version": "1.42.1",
+  "version": "1.42.2",
   "description": "Scaffolder for Claude Code's SEOAgent skill. Run once: `npx -y @seoagent-official/seoagent init`. Sets up .seoagent/ for persistent audits, keyword strategy, content planning, and optimized writing. Not a runtime dependency.",
   "type": "module",
   "bin": {
@@ -9,9 +9,7 @@
   "files": [
     "index.js",
     "skills",
-    "assets",
-    "postinstall-hint.cjs",
-    "postinstall-lib.cjs"
+    "assets"
   ],
   "dependencies": {
     "@clack/prompts": "^0.9.0",
@@ -31,9 +29,6 @@
     "type": "git",
     "url": "git+https://github.com/Baxter-Inc/seoagent-npm.git"
   },
-  "scripts": {
-    "postinstall": "node ./postinstall-hint.cjs"
-  },
   "publishConfig": {
     "access": "public"
   }

package/postinstall-hint.cjs

@@ -1,200 +0,0 @@
-'use strict';
-
-// =============================================================================
-// @seoagent-official/seoagent — postinstall
-//
-// This package is a SCAFFOLDER, not a runtime dependency. Its entire purpose
-// is to write `.seoagent/` + `.claude/skills/seoagent/` into the user's repo.
-// We learned the hard way that just printing a hint ("run init next") gets
-// ignored — coding agents like Claude Code install the package, see the
-// binary in node_modules/.bin, and stop. The user ends up with a devDep entry
-// and nothing useful.
-//
-// So this script does the scaffolding itself. It runs `init --yes` from
-// INIT_CWD (the directory where the user ran `npm install`) and inherits
-// stdio so all output is visible. Guards below ensure we don't run when it
-// would be wrong (CI, global install, already-scaffolded, opt-out).
-// =============================================================================
-
-const fs = require('fs');
-const path = require('path');
-const { spawnSync } = require('child_process');
-const { isDirectInstall } = require('./postinstall-lib.cjs');
-
-// -----------------------------------------------------------------------------
-// Guards — skip auto-init when it would be wrong or annoying.
-// -----------------------------------------------------------------------------
-
-// CI: postinstall must be non-interactive and side-effect-free in CI builds.
-if (process.env.CI === 'true' || process.env.CI === '1') {
-  process.exit(0);
-}
-
-// User opt-out: bail without touching the repo.
-if (process.env.SEOAGENT_SKIP_AUTOINIT === '1') {
-  printOptOutNotice();
-  process.exit(0);
-}
-
-// Global install: there's no project context to scaffold into.
-if (process.env.npm_config_global === 'true') {
-  printGlobalInstallHint();
-  process.exit(0);
-}
-
-// `INIT_CWD` is the directory where the user ran `npm install`. npm sets it
-// automatically. If it's missing we're probably being run by something other
-// than npm (e.g., yarn 1 used to skip this) — bail safely.
-const projectRoot = process.env.INIT_CWD;
-if (!projectRoot || !fs.existsSync(projectRoot)) {
-  printHintFallback();
-  process.exit(0);
-}
-
-// Don't auto-init when the package is being installed inside another
-// package's `node_modules` (a transitive dep). INIT_CWD would be the
-// transitive consumer's project root, not ours — we'd scaffold their repo.
-//
-// Detecting "transitive" reliably is harder than it looks: when a user runs
-// `npm install @seoagent-official/seoagent` in a fresh project, npm 7+ runs
-// THIS postinstall BEFORE writing the new dep to INIT_CWD/package.json. So
-// "is our package name in INIT_CWD/package.json" is false-negative-prone and
-// silently kills the captive install moment on every fresh install — which
-// is exactly the case we most need it to fire on.
-//
-// Instead: look at sibling node_modules entries. If ANY of them declares us
-// as a dependency, we're being dragged in transitively → bail. Otherwise
-// we're a direct install (or no one else needs us yet) → proceed.
-// We still consult package.json as a positive signal (e.g. for repeat installs
-// where the dep is already saved), since it strengthens the "direct" conclusion.
-if (!isDirectInstall(projectRoot)) {
-  // Most likely transitive — bail silently.
-  process.exit(0);
-}
-
-// Already scaffolded? No need to rerun init.
-const scaffoldMarker = path.join(projectRoot, '.seoagent', 'project.md');
-if (fs.existsSync(scaffoldMarker)) {
-  printAlreadyScaffoldedNotice(projectRoot);
-  process.exit(0);
-}
-
-// -----------------------------------------------------------------------------
-// Run init from the user's project root.
-// -----------------------------------------------------------------------------
-
-const binPath = path.join(__dirname, 'index.js');
-if (!fs.existsSync(binPath)) {
-  // Shouldn't happen in a published package — index.js sits next to this
-  // script in dist/. Fall back to printing the hint.
-  printHintFallback();
-  process.exit(0);
-}
-
-printPreInitBanner();
-
-const result = spawnSync(process.execPath, [binPath, 'init', '--yes'], {
-  cwd: projectRoot,
-  stdio: 'inherit',
-  env: { ...process.env, SEOAGENT_FROM_POSTINSTALL: '1' },
-});
-
-if (result.status === 0) {
-  printPostInitNotice();
-} else {
-  // init failed — most common cause: domain not inferable in --yes mode.
-  printInitFailureFallback();
-}
-
-// -----------------------------------------------------------------------------
-// Helpers — direct-install detection lives in ./postinstall-lib.cjs so it can
-// be unit-tested without firing the side effects above. The print functions
-// stay inline because they don't have meaningful behavior to test.
-// -----------------------------------------------------------------------------
-
-function printPreInitBanner() {
-  process.stdout.write(
-    '\n' +
-      '  ════════════════════════════════════════════════════════════════════\n' +
-      '   @seoagent-official/seoagent — scaffolding your repo\n' +
-      '  ════════════════════════════════════════════════════════════════════\n' +
-      '\n' +
-      '  This package is a one-shot scaffolder. Running `init --yes` now to\n' +
-      '  create .seoagent/ + .claude/skills/seoagent/ in your repo. To skip\n' +
-      '  this on future installs, set SEOAGENT_SKIP_AUTOINIT=1.\n' +
-      '\n'
-  );
-}
-
-function printPostInitNotice() {
-  // init's outro already printed the full next-steps prompt for both
-  // agents and humans. This is just the postinstall-specific cleanup
-  // hint that wouldn't be relevant to someone running `npx init` directly.
-  process.stdout.write(
-    '\n' +
-      '  Note for AGENTS and HUMANS: @seoagent-official/seoagent was added to\n' +
-      '  your package.json (devDependencies) by `npm install`. You can safely\n' +
-      '  remove it — its job is done. Subsequent `sync`/`login`/`status` calls\n' +
-      '  run via `npx -y @seoagent-official/seoagent <cmd>` and fetch on demand.\n' +
-      '\n'
-  );
-}
-
-function printInitFailureFallback() {
-  process.stdout.write(
-    '\n' +
-      '  ⚠ Auto-init didn\'t complete (most likely: domain not inferable from\n' +
-      '  package.json or .env files in --yes mode). Run this in your repo\n' +
-      '  root to finish setup, replacing the domain:\n' +
-      '\n' +
-      '    npx -y @seoagent-official/seoagent init --domain your-domain.com\n' +
-      '\n'
-  );
-}
-
-function printGlobalInstallHint() {
-  process.stdout.write(
-    '\n' +
-      '  @seoagent-official/seoagent installed globally.\n' +
-      '\n' +
-      '  In a project repo where you want SEOAgent, run:\n' +
-      '\n' +
-      '    seoagent init\n' +
-      '\n' +
-      '  That scaffolds .seoagent/ + .claude/skills/seoagent/ in the current\n' +
-      '  directory. Then open Claude Code and say "audit my site."\n' +
-      '\n'
-  );
-}
-
-function printOptOutNotice() {
-  process.stdout.write(
-    '\n' +
-      '  @seoagent-official/seoagent installed (auto-init skipped via\n' +
-      '  SEOAGENT_SKIP_AUTOINIT). Run `npx -y @seoagent-official/seoagent init`\n' +
-      '  in your repo root to scaffold when you\'re ready.\n' +
-      '\n'
-  );
-}
-
-function printAlreadyScaffoldedNotice(root) {
-  process.stdout.write(
-    '\n' +
-      '  @seoagent-official/seoagent installed. .seoagent/ already exists in\n' +
-      `  ${root} — skipping auto-init.\n` +
-      '\n'
-  );
-}
-
-function printHintFallback() {
-  process.stdout.write(
-    '\n' +
-      '  @seoagent-official/seoagent installed — but NOT yet scaffolded.\n' +
-      '\n' +
-      '  This package is a scaffolder, not a runtime dependency. Run this in\n' +
-      '  your repo root to finish setup:\n' +
-      '\n' +
-      '    npx -y @seoagent-official/seoagent init\n' +
-      '\n'
-  );
-}

package/postinstall-lib.cjs

@@ -1,117 +0,0 @@
-'use strict';
-
-// =============================================================================
-// postinstall-lib — pure helpers used by postinstall-hint.cjs
-//
-// Lives in its own file (instead of inline in postinstall-hint.cjs) for two
-// reasons:
-//   1. Unit-testable. The main script has top-level side effects
-//      (process.exit, spawnSync) that fire on require — splitting the pure
-//      logic out means vitest can require THIS file safely.
-//   2. The regression we're guarding against is subtle: npm 7+ writes the
-//      newly-installed package to the parent's package.json AFTER running
-//      the package's postinstall script. So the old "is our name in
-//      INIT_CWD/package.json" check returned false on every fresh install,
-//      silently killing the captive moment we built the package around.
-//      Tests for THIS file pin the corrected behavior in place.
-// =============================================================================
-
-const fs = require('fs');
-const path = require('path');
-
-const PKG_NAME = '@seoagent-official/seoagent';
-
-/**
- * Decide whether this postinstall is firing for a DIRECT install (user/agent
- * explicitly added us) vs a TRANSITIVE install (we're a dep of someone else's
- * dep). Returns true ⇒ scaffold; false ⇒ silent bail.
- *
- * Strategy is two-step because both signals alone are unreliable:
- *   1. POSITIVE — INIT_CWD/package.json already lists us. Confirms direct
- *      (but is FALSE on the most common case: first-time `npm install <us>`,
- *      because npm 7+ writes package.json AFTER lifecycle scripts).
- *   2. NEGATIVE — Look at every sibling under INIT_CWD/node_modules and check
- *      if any of THEIR package.json lists us as a dep. If yes → transitive.
- *      If no → direct (or top-level install with no other consumer yet).
- *
- * If both are inconclusive (e.g. no package.json at all because the user ran
- * `npm install <us>` in an empty dir), default to "direct" — scaffolding is
- * the whole point of the package and the existing `.seoagent/project.md`
- * idempotency guard prevents double-scaffolding on subsequent runs.
- */
-function isDirectInstall(root) {
-  if (!root) return true; // No INIT_CWD: nothing else we can check; scaffold.
-  if (declaredInProjectJson(root)) return true;
-  if (anySiblingDependsOnUs(root)) return false;
-  return true;
-}
-
-function declaredInProjectJson(root) {
-  try {
-    const pkgPath = path.join(root, 'package.json');
-    if (!fs.existsSync(pkgPath)) return false;
-    const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf-8'));
-    const all = mergeAllDepKinds(pkg);
-    return PKG_NAME in all;
-  } catch {
-    return false;
-  }
-}
-
-function anySiblingDependsOnUs(root) {
-  try {
-    const nm = path.join(root, 'node_modules');
-    if (!fs.existsSync(nm)) return false;
-    for (const entry of fs.readdirSync(nm, { withFileTypes: true })) {
-      if (!entry.isDirectory() || entry.name.startsWith('.')) continue;
-      // Scoped packages: recurse one level.
-      if (entry.name.startsWith('@')) {
-        const scopeDir = path.join(nm, entry.name);
-        let scoped;
-        try {
-          scoped = fs.readdirSync(scopeDir, { withFileTypes: true });
-        } catch {
-          continue;
-        }
-        for (const inner of scoped) {
-          if (!inner.isDirectory()) continue;
-          // Skip ourselves.
-          if (entry.name === '@seoagent-official' && inner.name === 'seoagent') continue;
-          if (pkgListsUs(path.join(scopeDir, inner.name, 'package.json'))) return true;
-        }
-        continue;
-      }
-      if (pkgListsUs(path.join(nm, entry.name, 'package.json'))) return true;
-    }
-    return false;
-  } catch {
-    return false;
-  }
-}
-
-function pkgListsUs(pkgJsonPath) {
-  try {
-    if (!fs.existsSync(pkgJsonPath)) return false;
-    const pkg = JSON.parse(fs.readFileSync(pkgJsonPath, 'utf-8'));
-    return PKG_NAME in mergeAllDepKinds(pkg);
-  } catch {
-    return false;
-  }
-}
-
-function mergeAllDepKinds(pkg) {
-  return {
-    ...(pkg.dependencies || {}),
-    ...(pkg.devDependencies || {}),
-    ...(pkg.optionalDependencies || {}),
-    ...(pkg.peerDependencies || {}),
-  };
-}
-
-module.exports = {
-  PKG_NAME,
-  isDirectInstall,
-  declaredInProjectJson,
-  anySiblingDependsOnUs,
-  pkgListsUs,
-};