unoverse 0.1.198 → 0.1.199

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "unoverse",
3
- "version": "0.1.198",
3
+ "version": "0.1.199",
4
4
  "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
5
5
  "license": "SEE LICENSE IN README.md",
6
6
  "type": "module",
@@ -15,7 +15,7 @@
15
15
  *
16
16
  * FOUR TIERS (docs/architecture/DECLARATIVE_NODES.md §6). This is tiers 2 and 3.
17
17
  * 1 editor $schema pointers + .vscode yaml.schemas, no tool
18
- * 2 structural every part validated against nodes/_schema/*.json
18
+ * 2 structural every part validated against the node schemas (packages/docs/schemas/nodes)
19
19
  * 3 semantic the cross-file rules a schema cannot express
20
20
  * 4 dry run `unoverse node test`, executes against testData, not here
21
21
  */
@@ -36,16 +36,17 @@ import { lintPackage } from "./package.mjs";
36
36
  /**
37
37
  * Where the node schemas are, for this run.
38
38
  *
39
- * The platform's own tree carries them at `nodes/_schema/`, and every node file points at
40
- * them with `$schema:` for editor squiggles. A DEVELOPER'S WORKSPACE DOES NOT: it holds only
41
- * their packages, and a linter that then warned "no schema found" on every file was
42
- * validating nothing while looking busy. So the schemas travel with the linter. In dist
43
- * they sit beside this file (copy-lint.mjs puts them there, and the CLI vendors that
44
- * folder); from source they are the monorepo's copy, five levels up.
39
+ * Their home is packages/docs/schemas/nodes, which the docs site serves at the URL every
40
+ * node file's `$schema:` names (so any editor validates online). The linter runs offline
41
+ * and a developer's workspace holds no copy, and a linter that warned "no schema found" on
42
+ * every file was validating nothing while looking busy. So the schemas travel with the
43
+ * linter: in dist they sit beside this file (copy-lint.mjs puts them there, and the CLI
44
+ * vendors that folder); from source they are the docs tree's copy. A `_schema` folder in
45
+ * the workspace itself still wins, for anyone pinning a version.
45
46
  */
46
47
  function schemaHome(home) {
47
48
  const here = dirname(fileURLToPath(import.meta.url));
48
- for (const c of [join(home, "_schema"), join(here, "_schema"), resolve(here, "../../../../../apps/unoverse/nodes/_schema")])
49
+ for (const c of [join(home, "_schema"), join(here, "_schema"), resolve(here, "../../../../docs/schemas/nodes")])
49
50
  if (existsSync(c)) return c;
50
51
  return join(home, "_schema");
51
52
  }
@@ -1,5 +1,5 @@
1
1
  /**
2
- * Tier 2: structural validation against nodes/_schema/*.json.
2
+ * Tier 2: structural validation against the node schemas (packages/docs/schemas/nodes).
3
3
  *
4
4
  * A JSON Schema catches shape. Everything a schema CANNOT express (cross-file agreement,
5
5
  * ordering, reachability) is tier 3 and lives in the rule modules.
@@ -53,7 +53,7 @@ export function loadSchemas() {
53
53
  export function validateAgainst(schemaId, doc, file, label) {
54
54
  const schema = state.schemas[schemaId];
55
55
  if (!schema) {
56
- report("warn", file, `no schema found for ${label}. Is nodes/_schema/ present?`);
56
+ report("warn", file, `no schema found for ${label}. The linter's bundled schemas are missing; rebuild base`);
57
57
  return;
58
58
  }
59
59
  const v = new Validator(schema, "7", false);