@reventlessdev/reventless-spec 3.0.0-alpha.125 → 3.0.0-alpha.126

package/CHANGELOG.md

@@ -3,6 +3,14 @@
 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.126 (2026-09-01)
+
+**Note:** Version bump only for package @reventlessdev/reventless-spec
+
+
+
+
+
 # 3.0.0-alpha.125 (2026-09-01)
 
 ### Bug Fixes

package/package.json

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

package/src/components/Aggregate.res

@@ -70,10 +70,11 @@ module type Spec = {
   type lifecycleState
 
   /** The lifecycle edge each command owns, read while the plugin structure is
-      assembled. Auto-injected as `_ => Unrestricted` by `@@reventless.spec`,
-      which leaves `@transition` in charge; a host that writes the switch by
-      hand takes charge instead, and gets an exhaustive one over typed states.
-      See `Transition`. */
+      assembled. Auto-injected as `_ => Unrestricted` by `@@reventless.spec`, so
+      a component whose commands guard nothing needs no line; a host that writes
+      the switch by hand gets an exhaustive one over typed states. Refused rather
+      than injected when the command type splices, since a spliced command must
+      be answered for. See `Transition`. */
   let commandTransition: command => Transition.t<lifecycleState>
 
   /** The domain traits grafted into this component, as values the trait packages

package/src/components/InboundTranslationSlice.res

@@ -72,8 +72,8 @@ module type Spec = {
 
   /** The lifecycle edge each command owns, read while the plugin structure is
       assembled. Auto-injected as `_ => Unrestricted` by `@@reventless.spec`,
-      which leaves `@transition` in charge; a host that writes the switch by
-      hand takes charge instead, and gets an exhaustive one over typed states.
+      so a component whose commands guard nothing needs no line; a host that
+      writes the switch by hand gets an exhaustive one over typed states.
       See `Transition`. */
   let commandTransition: command => Transition.t<lifecycleState>
 }

package/src/components/Plugin.res

@@ -137,10 +137,10 @@ type commandDef = {
   aggregateIdField: @s.matches(stringOptionSchema) option<string>,
   mutationField: string,
   references: array<fieldReference>,
-  /** The `@transition` *from* set — lifecycle states this command is meaningful in.
+  /** The declared *from* set — lifecycle states this command is meaningful in.
       `None` means always available; `Some([])` means never show. */
   allowedStates: @s.matches(stringArrayOptionSchema) option<array<string>>,
-  /** The `@transition` *to* state this command's handler writes. `None` with a
+  /** The declared *to* state this command's handler writes. `None` with a
       from-set present means the command does not move the row. */
   targetState: @s.matches(stringOptionSchema) option<string>,
   /** Whether the variant is exposed in the generated API (non-`@noApi`). */

package/src/components/StateAnnotations.res

@@ -54,7 +54,7 @@ otherwise see the same negative marker on every record they can read.
   two-valued enum.
 - `Some(v)` — the **state** form. The row is retired when the field equals `v`,
   and the field is the record's `@lifecycle` field. One field then carries the
-  fact once instead of twice, and `@transition(([Deactivated]) => Active)` on the
+  fact once instead of twice, and `Moves([Deactivated], Active)` on the
   way-back command is enough to make a generated menu offer it there and nowhere
   else —
   because retirement is finally expressible in the vocabulary that stance is
@@ -158,7 +158,7 @@ type stateAnnotationSpec = {
   metric: array<(string, metricSpec)>,
   /**
   Field annotated `@lifecycle` on the state record (PPX-emitted) — the enum a
-  command's `@transition` is written in terms of, a board draws its columns
+  command's declared edge is written in terms of, a board draws its columns
   from and a state diagram renders. `Some(name)` when one such annotation
   exists; the PPX errors on duplicate `@lifecycle` annotations within the same
   record. Codegen consumes this to populate `queryableDef.lifecycleField`, and

package/src/components/StateChangeSlice.res

@@ -94,8 +94,8 @@ module type Spec = {
 
   /** The lifecycle edge each command owns, read while the plugin structure is
       assembled. Auto-injected as `_ => Unrestricted` by `@@reventless.spec`,
-      which leaves `@transition` in charge; a host that writes the switch by
-      hand takes charge instead, and gets an exhaustive one over typed states.
+      so a component whose commands guard nothing needs no line; a host that
+      writes the switch by hand gets an exhaustive one over typed states.
       See `Transition`. */
   let commandTransition: command => Transition.t<lifecycleState>
 

package/src/types/Transition.res

@@ -1,13 +1,12 @@
 // The lifecycle edge a command owns, declared as a value rather than as an
 // attribute on the constructor.
 //
-// `@transition([Orders.Placed] => Orders.Shipped)` says the same thing and is
-// still the shorter spelling for a command a host declares itself. It cannot say
-// it for a command a host did NOT declare: a variant spread splices members,
-// while the annotation lowers to a dict on the parent union, so a spliced
-// command arrives carrying no edge at all. Nor can the annotation be checked —
-// the PPX extracts leaf identifiers as strings, and the states belong to another
-// component's enum, so a misspelling survives to the plugin structure.
+// The attribute this replaces could not say it for a command a host did NOT
+// declare: a variant spread splices members, while the attribute lowered to a
+// dict on the parent union, so a spliced command arrived carrying no edge at
+// all. Nor could it be checked — the PPX extracts leaf identifiers as strings,
+// and the states belong to another component's enum, so a misspelling survived
+// to the plugin structure.
 //
 // A `command => t<'state>` switch answers both. It is exhaustive, so a spliced
 // constructor is a compile error until the host says what it does; and `'state`