@crombolo/schema 0.9.1 → 0.10.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crombolo/schema",
-  "version": "0.9.1",
+  "version": "0.10.0",
   "description": "Schema-as-code for crombolo: TOML document, media and member type definitions.",
   "license": "MIT",
   "author": "Crombolo",
@@ -28,7 +28,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@crombolo/core": "0.9.1",
-    "@crombolo/data": "0.9.1"
+    "@crombolo/core": "0.10.0",
+    "@crombolo/data": "0.10.0"
   }
 }

package/src/check.ts

@@ -1,7 +1,7 @@
 /**
  * The pre-upgrade check: what would this change do to the data, and what does
  * it need? One function behind `crombolo upgrade check` and `crombolo schema
- * check`. Read-only. docs/10-packaging-and-upgrades.md, "Three kinds of finding".
+ * check`. Read-only. docs/packaging-and-upgrades.md, "Three kinds of finding".
  */
 import type { ContentTypeAggregate, PropertyTypeModel } from '@crombolo/core'
 import { DEFAULT_BACKOFFICE_PATH } from '@crombolo/core'

package/src/forms.ts

@@ -2,7 +2,7 @@
  * The form model, and the closed set of field types it may use.
  *
  * A form definition is structure, so it is a file like every other type
- * (`docs/18-forms.md`). Field types are an internal registry rather than an
+ * (`docs/forms.md`). Field types are an internal registry rather than an
  * extension point: the TOML vocabulary, the validator, the renderer and the
  * entry value shape all have to agree, and freezing that contract before
  * anything has stressed it would be a promise made too early.

package/src/model.ts

@@ -2,7 +2,7 @@ import type { SchemaForm } from '@crombolo/core'
 
 /**
  * The schema-as-code model: what a site's `schema/*.toml` files describe.
- * The shapes mirror the TOML vocabulary in docs/09-schema-as-code.md, with
+ * The shapes mirror the TOML vocabulary in docs/schema-as-code.md, with
  * defaults applied, so the rest of the system never sees a missing key.
  */
 export interface SchemaProperty {
@@ -108,7 +108,7 @@ export interface SchemaSet {
   memberTypes?: SchemaContentType[]
   dataTypes: SchemaDataType[]
   languages: SchemaLanguage[]
-  /** `schema/forms/*.toml` — form definitions; see `docs/18-forms.md`. */
+  /** `schema/forms/*.toml` — form definitions; see `docs/forms.md`. */
   forms?: SchemaForm[]
 }
 

package/src/sync.ts

@@ -1,7 +1,7 @@
 /**
  * Files → database. Version-gated, locked, and never destructive: removal is
  * retirement, and a type with content refuses to disappear. The algorithm and
- * the multi-node rules are in docs/09-schema-as-code.md, "Synchronisation".
+ * the multi-node rules are in docs/schema-as-code.md, "Synchronisation".
  */
 import { type ContentTypeAggregate, ObjectTypes, type PropertyTypeModel } from '@crombolo/core'
 import {