@reventlessdev/reventless-spec 3.0.0-alpha.101 → 3.0.0-alpha.102

package/CHANGELOG.md

@@ -3,6 +3,13 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# 3.0.0-alpha.102 (2026-08-08)
+
+### Features
+
+* **core,spec:** surface a write-side component's declared error types ([c9c2505](https://github.com/ReventlessDev/reventless-core/commit/c9c25057c70595fe27d73447c9aef9b451f86168))
+
+
 # 3.0.0-alpha.101 (2026-08-05)
 
 **Note:** Version bump only for package @reventlessdev/reventless-spec

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reventlessdev/reventless-spec",
-  "version": "3.0.0-alpha.101",
+  "version": "3.0.0-alpha.102",
   "description": "Specifications for Reventless",
   "license": "Apache-2.0",
   "bin": {

package/src/components/Plugin.res

@@ -288,6 +288,24 @@ type eventDef = {
   references: array<fieldReference>,
 }
 
+/**
+One declared error of a write side, with its field schema. Same shape and same
+derivation as `eventDef` — a refusal is a variant of `Spec.errorSchema` exactly as
+an emitted fact is a variant of `Spec.eventSchema`, so a consumer reading an
+error's payload walks it with the code path it already uses for an event. `name`
+is the variant name (e.g. `CategoryNotFound`) — the same string the runtime puts
+on `errorCode` when a decision is rejected (see `CommandTopic_Helpers`), so a
+caller can match what it reads here against what it receives. Payload-less
+variants (the common case for errors) carry an empty `schema` object and no
+references.
+*/
+@schema
+type errorDef = {
+  name: string,
+  schema: string,
+  references: array<fieldReference>,
+}
+
 @schema
 type writableDef = {
   name: string,
@@ -300,6 +318,13 @@ type writableDef = {
   arrays; `[]` when there are none. The structure is re-derived on every build/
   deploy, so no persisted-data back-compat shim is needed. */
   events: array<eventDef>,
+  /** Declared-error field schemas — what this component can refuse a command with.
+  Required, on the same reasoning as `events`: a structure is re-derived on every
+  build and re-registered on every deploy, and the persisted copy is never decoded
+  through this schema (the event log carries it as an offload reference, and the
+  serving path reads it as raw JSON), so `[]` honestly means "declares no errors"
+  rather than "an older deploy could not say". */
+  errors: array<errorDef>,
   /** Chapter grouping band — see `queryableDef.chapter`. */
   chapter: @s.matches(stringOptionSchema) option<string>,
 }

package/src/components/Plugin.res.mjs

@@ -127,6 +127,12 @@ let eventDefSchema = S.schema(s => ({
   references: s.m(S.array(fieldReferenceSchema))
 }));
 
+let errorDefSchema = S.schema(s => ({
+  name: s.m(S.string),
+  schema: s.m(S.string),
+  references: s.m(S.array(fieldReferenceSchema))
+}));
+
 let writableDefSchema = S.schema(s => ({
   name: s.m(S.string),
   commands: s.m(S.array(commandDefSchema)),
@@ -135,6 +141,7 @@ let writableDefSchema = S.schema(s => ({
   linkedViews: s.m(S.array(S.string)),
   consistencyRead: s.m(stringOptionSchema),
   events: s.m(S.array(eventDefSchema)),
+  errors: s.m(S.array(errorDefSchema)),
   chapter: s.m(stringOptionSchema)
 }));
 
@@ -248,6 +255,7 @@ export {
   commandDefSchema,
   queryableDefSchema,
   eventDefSchema,
+  errorDefSchema,
   writableDefSchema,
   automationSliceDefSchema,
   outboundTranslationSliceDefSchema,