@refactco/refact-os 1.5.1 → 1.5.2

package/CHANGELOG.md

@@ -4,6 +4,12 @@ Notable changes to the refact-os standard and scaffolder.
 
 **Staying current:** a consumer repo updates with `npm run refact:update` (or `npx @refactco/refact-os init`). That refreshes the package-managed `agent/` payload, **prunes** skills this package has removed or renamed (safe — only skills the package previously shipped, never your own), regenerates `.cursor/` + `.claude/`, and flags `agent/AGENTS.md` drift for a manual merge. The version it last applied is recorded in `.refact-os.json` under `_scaffold.version`, and `init` prints the `old → new` transition so you can scan the entries below for anything needing manual action. Run `npm run refact:validate` afterward.
 
+## 1.5.2
+
+### Added
+- **npm auto-publish on tags.** A GitHub Actions workflow (`.github/workflows/publish.yml`) publishes to npm (with provenance) when a `vX.Y.Z` tag is pushed, after checking the tag matches `package.json`. Requires the repo secret `NPM_TOKEN` (an npm "Automation" token for the `refactco` org). Release flow: bump `package.json` + `CHANGELOG` → commit → `git tag vX.Y.Z` → `git push origin vX.Y.Z`.
+- **Restored the `--adopt` flag** (it was lost before reaching `main`). `refact-os init --adopt` forces gentle / agent-layer-only mode on any repo — to re-adopt one an older `init` over-scaffolded, or update an existing repo without re-imposing the `docs/` seed, `apps/`, or WordPress dirs. It's the opposite of `--seed` (force full scaffold); `--adopt` wins if both are passed.
+
 ## 1.5.1
 
 ### Changed

package/README.md

@@ -80,7 +80,7 @@ refact-os validate  [--target <dir>]                     # check structure + ski
 refact-os migrate   [--target <dir>]                     # move an older layout into the current one
 ```
 
-- **`init`** — scaffold a project. An **empty** repo gets the thin seed + base `agent/` skills + type overlays + adapters; an **existing** repo gets only the agent layer (then run `/adopt`). `--seed` forces the full scaffold on a non-empty repo; `--no-force` never overwrites existing files.
+- **`init`** — scaffold a project. An **empty** repo gets the thin seed + base `agent/` skills + type overlays + adapters; an **existing** repo gets only the agent layer (then run `/adopt`). `--seed` forces the full scaffold on a non-empty repo; `--adopt` forces agent-layer-only on any repo (re-adopt one an older `init` over-scaffolded, or update an existing repo without imposing structure); `--no-force` never overwrites existing files.
 - **`sync`** — after editing `agent/`, regenerate `.cursor/` and `.claude/`. Never edit those by hand.
 - **`validate`** — checks the required folders/files exist, every skill declares its resolver frontmatter (the fields the agent routes on — `name`, `pattern`, `description`, `when_to_use`, `when_not_to_use`, `next_skills`), the generated skill index isn't stale, and the adapters are in sync.
 - **`migrate`** — moves an old-layout repo into the current one and tops up the `package.json` scripts. Safe: it never overwrites an existing file, and merges old chat folders into the new location.

package/bin/refact-os.js

@@ -26,7 +26,7 @@ function isAllowedTarget(target) {
 }
 
 function parseArgs(argv) {
-  const args = { command: "init", sub: undefined, target: process.cwd(), projectType: undefined, overlays: [], force: true, seed: false };
+  const args = { command: "init", sub: undefined, target: process.cwd(), projectType: undefined, overlays: [], force: true, seed: false, adopt: false };
   const raw = [...argv];
   if (raw[0] && !raw[0].startsWith("-")) args.command = raw.shift();
   if (raw[0] && !raw[0].startsWith("-")) args.sub = raw.shift();
@@ -37,6 +37,7 @@ function parseArgs(argv) {
     else if (token === "--target") args.target = raw.shift();
     else if (token === "--no-force") args.force = false;
     else if (token === "--seed") args.seed = true;
+    else if (token === "--adopt") args.adopt = true;
   }
   return args;
 }
@@ -47,6 +48,7 @@ async function runScaffold(args, { force }) {
     overlays: args.overlays,
     force,
     seed: args.seed,
+    adopt: args.adopt,
     interactive: process.stdin.isTTY,
   });
   console.log(`Scaffolded ${result.filesWritten} files in ${result.target}`);

package/lib/scaffold.js

@@ -216,13 +216,17 @@ async function scaffoldProject(targetDir, options = {}) {
   }
 
   // Brownfield vs greenfield. Decided once (at first init) and recorded, so a
-  // later `init`/update never suddenly imposes structure on an adopted repo.
-  // `--seed` (options.seed) forces the full scaffold and graduates a brownfield
-  // repo to it. On a brownfield repo we add ONLY the agent layer (base skills,
-  // root pointers, config, adapters) and defer the docs/ seed, apps/, and type
-  // overlays to the `adopt` skill, which reconciles them with existing dirs.
+  // later `init`/update never suddenly imposes structure on an adopted repo. On a
+  // brownfield repo we add ONLY the agent layer (base skills, root pointers,
+  // config, adapters) and defer the docs/ seed, apps/, and type overlays to the
+  // `adopt` skill. The two flags are opposites and override detection/recorded
+  // state: `--adopt` (options.adopt) forces gentle mode (re-adopt a repo an older
+  // init over-scaffolded, or update an existing one without imposing structure);
+  // `--seed` (options.seed) forces the full scaffold. `--adopt` wins if both pass.
   let brownfield;
-  if (options.seed) {
+  if (options.adopt) {
+    brownfield = true;
+  } else if (options.seed) {
     brownfield = false;
   } else if (!hadConfig) {
     brownfield = repoHasOwnContent(resolvedTarget);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@refactco/refact-os",
-  "version": "1.5.1",
+  "version": "1.5.2",
   "description": "Installable scaffolder for the agent-first repo standard: minimum-seed substrate + canonical agent/ skill catalog with generated tool adapters",
   "keywords": [
     "agent",