@almadar/std 5.2.2 → 5.4.0

package/dist/behaviors/exports/molecules/std-event-handler-game.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-event-handler-game",
+  "name": "EventHandlerGameOrbital",
   "version": "1.0.0",
-  "description": "Educational game molecule: menu -> playing -> complete. Uses the `event-handler-board` pattern for the playing state.",
   "orbitals": [
     {
       "name": "EventHandlerGameOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "score",
             "type": "number",
@@ -226,5 +229,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Educational game molecule: menu -> playing -> complete. Uses the `event-handler-board` pattern for the playing state. (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/dist/behaviors/exports/molecules/std-form-advanced.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-form-advanced",
+  "name": "FormEntryOrbital",
   "version": "1.0.0",
-  "description": "Advanced form molecule with relation-select for linked entity fields. Absorbs: relation-select.",
   "orbitals": [
     {
       "name": "FormEntryOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "notes",
             "type": "string",
@@ -509,6 +512,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "FormEntry created successfully"
                   ]
                 ]
               },
@@ -647,5 +654,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Advanced form molecule with relation-select for linked entity fields. Absorbs: relation-select. (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}