unoverse 0.1.197 → 0.1.199

package/lib/skills.mjs

@@ -80,11 +80,19 @@ export function skillFileText(skill, rel, text) {
   return `---\nname: ${skill}\ndescription: ${desc}\n---\n\n${body}`;
 }
 
+/**
+ * The site sits behind a CDN that serves llms.txt and pages from cache for a while after
+ * a release (observed 2026-09-05: ninety minutes, and the new skill pages absent from the
+ * listing throughout). An installer that read the cache would install last release's
+ * skills right after this one. A fresh query string is a fresh cache key.
+ */
+const fresh = (url) => `${url}?t=${Date.now()}`;
+
 export async function installSkills() {
   const target = join(homedir(), ".claude", "skills");
   let files;
   try {
-    const res = await fetch(`${DOCS}/llms.txt`);
+    const res = await fetch(fresh(`${DOCS}/llms.txt`));
     if (!res.ok) throw new Error(`HTTP ${res.status}`);
     files = skillFilesFromLlms(await res.text());
   } catch {
@@ -101,7 +109,7 @@ export async function installSkills() {
   const tmp = mkdtempSync(join(tmpdir(), "unoverse-skills-"));
   try {
     for (const f of files) {
-      const res = await fetch(f.url);
+      const res = await fetch(fresh(f.url));
       if (!res.ok) throw new Error(`${f.url}: HTTP ${res.status}`);
       const p = join(tmp, f.skill, f.rel);
       mkdirSync(dirname(p), { recursive: true });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.197",
+  "version": "0.1.199",
   "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",

package/vendor/base/lint/nodes/index.mjs

@@ -15,7 +15,7 @@
  *
  * FOUR TIERS (docs/architecture/DECLARATIVE_NODES.md §6). This is tiers 2 and 3.
  *   1  editor    $schema pointers + .vscode yaml.schemas, no tool
- *   2  structural   every part validated against nodes/_schema/*.json
+ *   2  structural   every part validated against the node schemas (packages/docs/schemas/nodes)
  *   3  semantic     the cross-file rules a schema cannot express
  *   4  dry run      `unoverse node test`, executes against testData, not here
  */
@@ -36,16 +36,17 @@ import { lintPackage } from "./package.mjs";
 /**
  * Where the node schemas are, for this run.
  *
- * The platform's own tree carries them at `nodes/_schema/`, and every node file points at
- * them with `$schema:` for editor squiggles. A DEVELOPER'S WORKSPACE DOES NOT: it holds only
- * their packages, and a linter that then warned "no schema found" on every file was
- * validating nothing while looking busy. So the schemas travel with the linter. In dist
- * they sit beside this file (copy-lint.mjs puts them there, and the CLI vendors that
- * folder); from source they are the monorepo's copy, five levels up.
+ * Their home is packages/docs/schemas/nodes, which the docs site serves at the URL every
+ * node file's `$schema:` names (so any editor validates online). The linter runs offline
+ * and a developer's workspace holds no copy, and a linter that warned "no schema found" on
+ * every file was validating nothing while looking busy. So the schemas travel with the
+ * linter: in dist they sit beside this file (copy-lint.mjs puts them there, and the CLI
+ * vendors that folder); from source they are the docs tree's copy. A `_schema` folder in
+ * the workspace itself still wins, for anyone pinning a version.
  */
 function schemaHome(home) {
   const here = dirname(fileURLToPath(import.meta.url));
-  for (const c of [join(home, "_schema"), join(here, "_schema"), resolve(here, "../../../../../apps/unoverse/nodes/_schema")])
+  for (const c of [join(home, "_schema"), join(here, "_schema"), resolve(here, "../../../../docs/schemas/nodes")])
     if (existsSync(c)) return c;
   return join(home, "_schema");
 }

package/vendor/base/lint/nodes/schema.mjs

@@ -1,5 +1,5 @@
 /**
- * Tier 2: structural validation against nodes/_schema/*.json.
+ * Tier 2: structural validation against the node schemas (packages/docs/schemas/nodes).
  *
  * A JSON Schema catches shape. Everything a schema CANNOT express (cross-file agreement,
  * ordering, reachability) is tier 3 and lives in the rule modules.
@@ -53,7 +53,7 @@ export function loadSchemas() {
 export function validateAgainst(schemaId, doc, file, label) {
   const schema = state.schemas[schemaId];
   if (!schema) {
-    report("warn", file, `no schema found for ${label}. Is nodes/_schema/ present?`);
+    report("warn", file, `no schema found for ${label}. The linter's bundled schemas are missing; rebuild base`);
     return;
   }
   const v = new Validator(schema, "7", false);