@gregiteen/ssss-cli 0.10.3 → 0.11.1

package/CHANGELOG.md

@@ -7,6 +7,39 @@ 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`.
+  `@gregiteen/ssss-cli/runtime` exports `triggerMatchesEvent`, `subjectMatches`
+  and `resolveSubjectOwner`; the spec (§11.8) defines event matching and subject
+  ownership, which `source: event` previously left undefined.
+
+### Fixed
+- Work caused by an event is now keyed by `event_id` (and carries it as
+  `causation_id`), not by the event's timestamp. Two events in the same
+  millisecond no longer collapse into one task path and key.
+
 ## [0.10.3] - 2026-10-01
 ### Fixed
 - Read event logs in 64 KiB chunks when building duplicate-ID indexes or

package/VERSION

@@ -1 +1 @@
-0.10.3
+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.
 
 ---
 
@@ -1487,6 +1499,24 @@ Core trigger types are:
 | `file_change` | A matching vault path is created, patched, or deleted. |
 | `condition` | A host-defined predicate over vault/projection state becomes true. |
 
+An `event` trigger selects canonical events (§8) with two optional fields on the
+`trigger` primitive, evaluated as a pure function of the trigger and the event:
+
+- `event_subject` is a glob over the event `subject`. `*` matches within one `/`
+  segment and `**` matches across segments.
+- `event_match` maps dotted event paths (for example `principal.kind`) to a literal
+  or an array of allowed literals. Every entry MUST hold.
+
+A trigger with neither field matches nothing. An event nobody matches is only
+recorded. Work an event causes MUST carry the event's `event_id` as `causation_id`,
+and its idempotency basis uses `event_id` in place of `scheduled_for`, so a replayed
+event creates no second task and two events at the same instant create two.
+
+An `assistant` MAY declare `owns`, a list of subject globs it is responsible for.
+The owner of a subject is the assistant whose claim has the longest literal prefix.
+Equal best claims are a conflict that a host MUST surface rather than resolve
+silently. Ownership says who is responsible; a lease (§7) says who is acting now.
+
 Trigger entries SHOULD use the fields documented in §5.4 `workflow`. Hosts MAY add
 type-specific `x_` fields, but MUST preserve unknown fields when rewriting the
 workflow document (§4.2).
@@ -1497,6 +1527,7 @@ The idempotency basis for runtime-created work is:
 
 ```text
 workspace_id + workflow_id + trigger_id + scheduled_for
+workspace_id + workflow_id + trigger_id + event_id        (event-driven work)
 ```
 
 Two daemon ticks evaluating the same trigger for the same scheduled instant MUST

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gregiteen/ssss-cli",
-  "version": "0.10.3",
+  "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/core.json

@@ -115,6 +115,7 @@
       "append_only": false,
       "portability": "structural",
       "required_fields": ["type", "name"],
+      "optional_fields": ["owns"],
       "spec_ref": "§5.4 assistant"
     },
     "workflow": {
@@ -132,7 +133,7 @@
       "append_only": false,
       "portability": "structural",
       "required_fields": ["type", "name", "source", "status"],
-      "optional_fields": ["slug", "description", "cron", "interval", "timezone", "target_workflow", "target_params", "concurrency", "misfire_policy"],
+      "optional_fields": ["slug", "description", "cron", "interval", "timezone", "target_workflow", "target_params", "concurrency", "misfire_policy", "event_subject", "event_match"],
       "enums": {
         "source": ["cron", "interval", "webhook", "event", "file_change", "condition", "manual"],
         "status": ["active", "paused", "disabled"],

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"]
+}