@gregiteen/ssss-cli 0.11.0 → 0.11.1

package/CHANGELOG.md

@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.11.1] - 2026-10-19
+### Fixed
+- The frontmatter parser (`@gregiteen/ssss-cli/frontmatter`) now reads the YAML
+  that Total Recall and other tools actually write. It previously dropped
+  hyphenated keys (`allowed-tools`), truncated wrapped values, split quoted
+  commas inside inline arrays, left JSON flow maps and arrays of JSON objects
+  as strings, turned tags like `context:universal` into maps, and kept
+  trailing `# comments`; `patch` then wrote those mis-parsed values back to
+  disk. Verified against 27,536 vault files across 55 Total Recall brains: the
+  only differences from a js-yaml reading are leading-zero codes and ISO
+  timestamps, which SSSS keeps as strings on purpose (spec §4.5).
+- The serializer quotes strings containing commas or a leading indicator and
+  writes nested objects inside inline arrays as JSON, so values round-trip.
+
+### Added
+- `scripts/check-frontmatter.mjs`, run by `npm test`.
+- Documents a broken writer flattened onto one line with literal `\n` text
+  (23 such vault files exist) are repaired automatically on read, and
+  `repairEscapedNewlines` is exported from `@gregiteen/ssss-cli/frontmatter`.
+  `scripts/autolink.mjs` now uses the shared frontmatter parser.
+
 ## [0.11.0] - 2026-10-13
 ### Added
 - `trigger` gains `event_subject` and `event_match`, and `assistant` gains `owns`.

package/VERSION

@@ -1 +1 @@
-0.11.0
+0.11.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.3"
+      "exporter": "@gregiteen/ssss-cli@0.11.1"
     }
   },
   "files": [

package/docs/ssss-spec.md

@@ -210,9 +210,21 @@ exactly this subset.
   under the first. A map entry may itself hold an inline array.
 - **Folded strings**: `>` and `>-` block scalars.
 
-Anchors, aliases, tags, multi-document streams, and flow maps (`{a: 1}`) are
-outside the subset. A host MAY accept them but MUST NOT require them, and
-authors SHOULD NOT use them in documents that leave the host.
+Anchors, aliases, tags, and multi-document streams are outside the subset.
+Flow maps (`{a: 1}`) and JSON-style inline values (`[{"a": 1}]`) are also
+outside it, but the reference parser reads them because other tools write them
+(for example Total Recall's JSON-shaped metadata). A host MAY accept any of
+these but MUST NOT require them, and authors SHOULD NOT use them in documents
+that leave the host.
+
+Where the reference parser reads a form YAML 1.2 also defines, it follows YAML:
+keys may contain `-`, `.` and `@`; a `:` only splits a key when whitespace or
+end of line follows, so `context:universal` is a value; plain and quoted
+scalars may wrap onto indented continuation lines; a trailing ` # comment` on
+an unquoted value is dropped; and a block list may sit at its key's indent.
+Two deliberate deviations keep values lossless: an integer with a leading zero
+(`07885`) stays a **string**, since it is a code and not a number, and
+timestamps stay strings, as above.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gregiteen/ssss-cli",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "description": "CLI tools and the reference engine for the Structured Semantic Syntax System",
   "main": "src/engine.mjs",
   "exports": {
@@ -56,7 +56,7 @@
   ],
   "scripts": {
     "conformance": "node ./scripts/conformance.mjs conformance",
-    "test": "node ./scripts/conformance.mjs conformance --engine && node ./scripts/check-events-streaming.mjs"
+    "test": "node ./scripts/conformance.mjs conformance --engine && node ./scripts/check-events-streaming.mjs && node ./scripts/check-frontmatter.mjs"
   },
   "keywords": [
     "ssss",

package/registry/extensions/defaults.json

@@ -0,0 +1,5 @@
+{
+  "$schema": "https://ssss.dev/registry/v1",
+  "description": "Extensions composed when a caller does not scope a registry load. Extensions NOT listed here are product-specific: a host loads one only when it is operating on that product's vault, passing the extension name explicitly (`ssss export --ext <name>`). This keeps two unrelated products from colliding on a shared primitive name, which §5.6 makes a load-time error.",
+  "default_extensions": ["festech"]
+}