@kanonak-protocol/cli 5.18.0 → 5.20.0

package/dist/commands/serve.d.ts

@@ -5,8 +5,9 @@
  * rendering lives in `@kanonak-protocol/sdk/server` (`loadServerModel` /
  * `loadResourceModel` + `route`), which makes the SAME `LookRenderer` calls
  * `kanonak publish` does — so a live response is byte-equivalent to the static
- * page `publish` would write, plus the machine-facing endpoints publish omits
- * (`/.well-known/kanonak.json`, `/index.txt`, raw `{package}/{version}.kan.yml`).
+ * page `publish` would write, plus the machine-facing endpoints
+ * (`/.well-known/kanonak.json`, `/kanonak.lock`, raw
+ * `{package}/{version}.kan.yml`), which `publish` freezes to disk.
  *
  * serve does ONE thing — be the origin (render + machine endpoints). It is not
  * a search engine: ad-hoc site search is a separate, stateful concern that

package/dist/commands/validate.d.ts

@@ -1 +1,12 @@
-export declare function validateCommand(path: string): Promise<void>;
+export interface ValidateOptions {
+    /**
+     * Additionally evaluate SHACL INSTANCE conformance over the workspace
+     * scope — every sh:NodeShape in the resolved catalog runs against the
+     * data, and each finding prints with its focus node, path, and constraint
+     * component. Off by default: `kanonak validate` stays definition
+     * validation (the common case), and conformance is the deliberate opt-in
+     * whose scope is the workspace's own pinned closure.
+     */
+    conformance?: boolean;
+}
+export declare function validateCommand(path: string, options?: ValidateOptions): Promise<void>;