@almadar/std 5.2.1 → 5.3.0

package/dist/behaviors/exports/atoms/std-upload.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-upload",
+  "name": "UploadFileOrbital",
   "version": "1.0.0",
-  "description": "File upload atom with drag-and-drop zone and progress tracking. Absorbs: upload-drop-zone.",
   "orbitals": [
     {
       "name": "UploadFileOrbital",
@@ -532,5 +531,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "File upload atom with drag-and-drop zone and progress tracking. Absorbs: upload-drop-zone. (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/atoms/std-validate-on-save.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-validate-on-save",
+  "name": "ValidateOnSave",
   "version": "1.0.0",
-  "description": "OS trigger that watches .orb files and validates them on save. Shows a status dashboard with validation results. Emits AGENT_INTERRUPT with validation results to interrupt autonomous agents with ground truth.",
   "orbitals": [
     {
       "name": "ValidateOnSave",
@@ -163,6 +162,10 @@
                     "type": "array"
                   }
                 ]
+              },
+              {
+                "key": "NAVIGATE",
+                "name": "NAVIGATE"
               }
             ],
             "transitions": [
@@ -575,6 +578,30 @@
                     }
                   ]
                 ]
+              },
+              {
+                "from": "idle",
+                "to": "idle",
+                "event": "NAVIGATE",
+                "effects": []
+              },
+              {
+                "from": "validating",
+                "to": "validating",
+                "event": "NAVIGATE",
+                "effects": []
+              },
+              {
+                "from": "valid",
+                "to": "valid",
+                "event": "NAVIGATE",
+                "effects": []
+              },
+              {
+                "from": "invalid",
+                "to": "invalid",
+                "event": "NAVIGATE",
+                "effects": []
               }
             ]
           }
@@ -592,5 +619,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "OS trigger that watches .orb files and validates them on save. Shows a status dashboard with validation results. Emits AGENT_INTERRUPT with validation results to interrupt autonomous agents with ground truth. (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/atoms/std-wizard.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-wizard",
+  "name": "WizardEntryOrbital",
   "version": "1.0.0",
-  "description": "Multi-step wizard behavior parameterized for any domain. Generates a dynamic number of steps based on the `steps` parameter, with a review screen and completion view. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "WizardEntryOrbital",
@@ -1094,5 +1093,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Multi-step wizard behavior parameterized for any domain. Generates a dynamic number of steps based on the `steps` parameter, with a review screen and completion view. Pure function: params in, OrbitalDefinition out. (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."
+}