@gregiteen/ssss-cli 0.10.0 → 0.10.1

package/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.10.1] - 2026-09-28
+### Fixed
+- A required list field set to an empty list (`deferred_steps: []`) was
+  rejected as "Missing required field". Required means present: only an
+  absent, `null` or empty-string value is missing now. Hosts had to patch the
+  package to write valid documents with empty lists.
+
+### Behavior changes hosts should check
+- Documents with a required list field set to `[]` now validate.
+- New conformance checks: an empty list satisfies a required list field;
+  absent, `null` and empty-string values are still missing.
+
 ## [0.10.0] - 2026-09-28
 ### Added
 - **`asset` primitive**: Text-encoded files (Base64 for small binaries, UTF-8 for code/SVGs) and pointer metadata for large files (`resource_ref`, `storage_uri`, `hash`).

package/VERSION

@@ -1 +1 @@
-0.10.0
+0.10.1

package/conformance/reference-bundle.ucw.json

@@ -106,7 +106,7 @@
     "file_count": 14,
     "provenance": {
       "content_hash": "sha256:7febd673938a3dc04c068e0bf08097a9783c09e612606d2df9a4db8dcb8907f5",
-      "exporter": "@gregiteen/ssss-cli@0.10.0"
+      "exporter": "@gregiteen/ssss-cli@0.10.1"
     }
   },
   "files": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gregiteen/ssss-cli",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "description": "CLI tools and the reference engine for the Structured Semantic Syntax System",
   "main": "src/engine.mjs",
   "exports": {

package/scripts/conformance-09.mjs

@@ -9,6 +9,7 @@ import {
   createRegistryLock,
   loadRegistries,
   resolvePrimitiveDefinition,
+  validateDataConstraints,
   verifyRegistryLock,
 } from '../src/registry.mjs';
 import { createValidator } from '../src/validator.mjs';
@@ -258,6 +259,16 @@ function checkFrontmatterSubset(check) {
     JSON.stringify(parseDocument(serializeDocument(data, '\nbody')).data) === JSON.stringify(data));
 }
 
+// A required field is satisfied by any present value, including an empty
+// list; only an absent, null or empty-string value is missing.
+function checkRequiredPresence(check) {
+  const def = { required_fields: ['steps', 'name'] };
+  const missing = (data) => validateDataConstraints(def, data).map((i) => i.field).sort().join(',');
+  check('required fields: an empty list satisfies a required list field', missing({ steps: [], name: 'x' }) === '');
+  check('required fields: absent, null and empty-string values are missing',
+    missing({ name: '' }) === 'name,steps' && missing({ steps: null, name: 'x' }) === 'steps');
+}
+
 // Capabilities (spec §6.6): trailing-`*` grants are prefix scoped, and the
 // pre-0.9 façade still honors the role permissions it always documented.
 async function checkCapabilities(root, check) {
@@ -606,6 +617,7 @@ export async function runKernel09Conformance() {
     check('UI planning redacts prompt-injection content and falls back safely', planned.generated && planned.manifest.components[0].bind === 'status');
     await checkResourceLifecycle(check);
     checkFrontmatterSubset(check);
+  checkRequiredPresence(check);
     await checkCapabilities(temp, check);
   } finally {
     fs.rmSync(temp, { recursive: true, force: true });

package/src/registry.mjs

@@ -355,8 +355,9 @@ export function documentHash(content) {
 }
 
 function isEmpty(value) {
-  return value === undefined || value === null || value === '' ||
-    (Array.isArray(value) && value.length === 0);
+  // "Required" means present: an empty array (e.g. `deferred_steps: []`) is a
+  // valid value for a required list field, so it is not treated as missing.
+  return value === undefined || value === null || value === '';
 }
 
 /**