unoverse 0.1.152 → 0.1.154

package/bin/unoverse.mjs

@@ -126,15 +126,19 @@ switch (cmd) {
 
   case "_postupdate": {
     // Runs AS the new version, in the developer's cwd. A universe refreshes its
-    // platform images; ANY folder that has authoring skills installed (a Studio
-    // project) gets them refreshed from the public mirror, so `unoverse update` is
-    // the one command that brings everything current. A folder with neither is
-    // left alone, and silence is the right answer.
+    // platform images; the authoring skills install to ~/.claude/skills from the public
+    // mirror, so `unoverse update` is the one command that brings everything current.
+    //
+    // THE SKILLS ARE NOT CWD-SCOPED. This used to refresh `<cwd>/.claude/skills` and only
+    // when that folder already existed, which meant it fired on whichever folder update
+    // happened to be run in — a universe, almost never a design workspace — and never
+    // installed anything at all. They are per developer, so they go to the home directory
+    // and this runs unconditionally.
     if (UNIVERSE) {
       operator(UNIVERSE, ["refresh-images"]);
     }
-    const { refreshSkills } = await import("../lib/skills.mjs");
-    refreshSkills(process.cwd());
+    const { installSkills } = await import("../lib/skills.mjs");
+    installSkills();
     process.exit(0);
   }
 

package/lib/skills.mjs

@@ -1,40 +1,57 @@
-// Refresh the Claude Code authoring skills installed in a folder.
+// Install the Claude Code authoring skills for this developer.
 //
 // The public mirror github.com/unoverse-platform/skills is the one place installed
-// skills come from (publish syncs it from the platform repo's .claude/skills). This
-// runs on `unoverse update` (_postupdate) in the developer's cwd: a folder that HAS
-// .claude/skills gets every skill the mirror carries, replaced whole; a folder that
-// never had them is left alone — installing skills is Studio's job at project
-// creation, not update's.
-import { mkdtempSync, existsSync, readdirSync, rmSync, cpSync } from "node:fs";
+// skills come from (publish syncs it from the platform repo's .claude/skills).
+//
+// PER DEVELOPER, NOT PER PROJECT (2026-08-21). These install to ~/.claude/skills, so
+// Claude Code picks them up in every folder the developer opens and nothing lands
+// inside a workspace where it could be committed. They used to be copied into each
+// Studio workspace's own .claude/skills by Studio's scaffold, out of a snapshot
+// vendored in the Studio npm package: that reproduced the platform repo's .claude
+// folder on every remote developer's disk, pinned to whichever Studio version they
+// installed. Studio no longer writes them (packages/studio/local/scaffold.mjs) and
+// the mirror is the only channel.
+//
+// INSTALLS, NOT JUST REFRESHES. This used to return early when the folder was absent,
+// because seeding was Studio's job. Nothing seeds them now, so an absent folder is the
+// FIRST install and creating it is the whole point.
+//
+// Runs on `unoverse update` (_postupdate), which is the one command that brings a
+// developer's tooling current.
+import { mkdtempSync, existsSync, mkdirSync, readdirSync, rmSync, cpSync } from "node:fs";
 import { join } from "node:path";
-import { tmpdir } from "node:os";
+import { tmpdir, homedir } from "node:os";
 import { spawnSync } from "node:child_process";
 
 const TARBALL = "https://codeload.github.com/unoverse-platform/skills/tar.gz/refs/heads/main";
 
-export function refreshSkills(dir) {
-  const target = join(dir, ".claude", "skills");
-  if (!existsSync(target)) return;
+export function installSkills() {
+  const target = join(homedir(), ".claude", "skills");
   const tmp = mkdtempSync(join(tmpdir(), "unoverse-skills-"));
   try {
     const dl = spawnSync("bash", ["-c", `curl -fsSL "${TARBALL}" | tar -xz -C "${tmp}" --strip-components=1`], {
       stdio: "pipe",
     });
     if (dl.status !== 0) {
-      console.log("  Skills refresh skipped (github.com unreachable). They refresh on the next update.");
+      console.log("  Skills install skipped (github.com unreachable). They install on the next update.");
       return;
     }
-    // Same filter as Studio's scaffold: a skill is a directory holding a SKILL.md.
-    // The mirror's README and dotfiles never install.
+    // A skill is a directory holding a SKILL.md. The mirror's README and dotfiles never
+    // install.
     const names = readdirSync(tmp, { withFileTypes: true })
       .filter((e) => e.isDirectory() && existsSync(join(tmp, e.name, "SKILL.md")))
       .map((e) => e.name);
+    if (!names.length) return;
+    mkdirSync(target, { recursive: true });
+    // REPLACED WHOLE, ours only. Each skill folder the mirror carries is removed and
+    // re-copied, so a deleted file upstream really goes. Anything else in the
+    // developer's ~/.claude/skills is THEIRS and is never touched: this folder is
+    // shared with every skill they have installed from anywhere else.
     for (const name of names) {
       rmSync(join(target, name), { recursive: true, force: true });
       cpSync(join(tmp, name), join(target, name), { recursive: true });
     }
-    if (names.length) console.log(`  ✓ authoring skills refreshed (${names.join(", ")})`);
+    console.log(`  ✓ authoring skills installed to ~/.claude/skills (${names.join(", ")})`);
   } finally {
     rmSync(tmp, { recursive: true, force: true });
   }

package/operator/operator.sh

@@ -157,6 +157,17 @@ case "${1:-}" in
       if [ -n "$(docker compose -f "$ROOT/docker-compose.yml" ps -q 2>/dev/null)" ]; then
         docker compose -f "$ROOT/docker-compose.yml" --env-file "$ROOT/.env" up -d --remove-orphans >/dev/null 2>&1 \
           && ok "Running services moved to the new images"
+        # MIGRATIONS RUN ON UPDATE, same as deploy and start. An update is exactly when a
+        # new migration arrives (it ships inside the image just pulled), and this was the
+        # one path that skipped db-setup: a universe could run new code against a schema
+        # missing the columns that code expects, silently, until something read them.
+        # Additive-by-rule until Retire and idempotent, so re-running costs nothing.
+        # Subshell because cmd_db_setup exits rather than returns on failure.
+        if ! (cmd_db_setup) >/dev/null 2>&1; then
+          warn "Migrations did not apply. Run ${BOLD}unoverse check${NC} to see why"
+        else
+          ok "Database migrations are current"
+        fi
         echo ""
         echo -e "  ${GREEN}unoverse where${NC}     Links to your Canvas and API"
         echo ""

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.152",
+  "version": "0.1.154",
   "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
   "license": "SEE LICENSE IN README.md",
   "type": "module",