@almadar/std 5.2.2 → 5.3.0

package/dist/behaviors/exports/atoms/std-service-twilio.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-service-twilio",
+  "name": "ServiceTwilioOrbital",
   "version": "1.0.0",
-  "description": "Twilio messaging integration behavior: compose, send SMS or WhatsApp, track delivery. Wraps the `twilio` service integration with sendSMS and sendWhatsApp operations. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceTwilioOrbital",
@@ -608,5 +607,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Twilio messaging integration behavior: compose, send SMS or WhatsApp, track delivery. Wraps the `twilio` service integration with sendSMS and sendWhatsApp operations. 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."
+}

package/dist/behaviors/exports/atoms/std-service-youtube.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-service-youtube",
+  "name": "ServiceYoutubeOrbital",
   "version": "1.0.0",
-  "description": "YouTube service integration behavior: search videos, view video details. Wraps the `youtube` service integration with search and getVideo operations. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceYoutubeOrbital",
@@ -693,5 +692,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "YouTube service integration behavior: search videos, view video details. Wraps the `youtube` service integration with search and getVideo operations. 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."
+}

package/dist/behaviors/exports/atoms/std-simulation-canvas.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-simulation-canvas",
+  "name": "SimulationWorldOrbital",
   "version": "1.0.0",
-  "description": "2D physics simulation renderer atom using the `simulation-canvas` pattern. Runs built-in Euler integration for educational presets (pendulum, spring, etc.). Supports start, stop, and reset controls.",
   "orbitals": [
     {
       "name": "SimulationWorldOrbital",
@@ -186,5 +185,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "2D physics simulation renderer atom using the `simulation-canvas` pattern. Runs built-in Euler integration for educational presets (pendulum, spring, etc.). Supports start, stop, and reset controls. (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-sort.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-sort",
+  "name": "SortableItemOrbital",
   "version": "1.0.0",
-  "description": "Sort atom. Shows sort-by buttons for each sortable field. Clicking a field name sorts by that field. Clicking again toggles direction.",
   "orbitals": [
     {
       "name": "SortableItemOrbital",
@@ -708,5 +707,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Sort atom. Shows sort-by buttons for each sortable field. Clicking a field name sorts by that field. Clicking again toggles direction. (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-sprite.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-sprite",
+  "name": "SpriteEntityOrbital",
   "version": "1.0.0",
-  "description": "Sprite renderer atom using the `sprite` pattern. Renders a single frame from a spritesheet with position and scale. Handles frame changes and click events.",
   "orbitals": [
     {
       "name": "SpriteEntityOrbital",
@@ -307,5 +306,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Sprite renderer atom using the `sprite` pattern. Renders a single frame from a spritesheet with position and scale. Handles frame changes and click events. (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-tabs.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-tabs",
+  "name": "TabContentOrbital",
   "version": "1.0.0",
-  "description": "Tab navigation atom. Uses the `tabs` pattern component with clickable tab headers. Each tab shows different entity data.",
   "orbitals": [
     {
       "name": "TabContentOrbital",
@@ -282,5 +281,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Tab navigation atom. Uses the `tabs` pattern component with clickable tab headers. Each tab shows different entity data. (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-text-effects.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-text-effects",
+  "name": "TextContentOrbital",
   "version": "1.0.0",
-  "description": "Text animation and highlighting atom. Absorbs: typewriter-text, text-highlight, law-reference-tooltip.",
   "orbitals": [
     {
       "name": "TextContentOrbital",
@@ -655,5 +654,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Text animation and highlighting atom. Absorbs: typewriter-text, text-highlight, law-reference-tooltip. (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-theme.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-theme",
+  "name": "ThemePreferenceOrbital",
   "version": "1.0.0",
-  "description": "Theme selection atom with toggle and full selector. Absorbs: theme-toggle, theme-selector.",
   "orbitals": [
     {
       "name": "ThemePreferenceOrbital",
@@ -570,5 +569,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Theme selection atom with toggle and full selector. Absorbs: theme-toggle, theme-selector. (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-timer.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-timer",
+  "name": "TimerSessionOrbital",
   "version": "1.0.0",
-  "description": "std-timer as a Function",
   "orbitals": [
     {
       "name": "TimerSessionOrbital",
@@ -1420,5 +1419,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Timer behavior parameterized for any domain. Provides a countdown timer with start, pause, resume, and reset controls. The state machine structure is fixed. The caller controls data and presentation. (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-undo.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-undo",
+  "name": "UndoActionOrbital",
   "version": "1.0.0",
-  "description": "Undo/Redo atom using array operators as a stack. - PUSH: appends to undoStack, clears redoStack - UNDO: pops from undoStack, pushes to redoStack - REDO: pops from redoStack, pushes to undoStack - CLEAR: empties both stacks",
   "orbitals": [
     {
       "name": "UndoActionOrbital",
@@ -822,5 +821,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Undo/Redo atom using array operators as a stack. - PUSH: appends to undoStack, clears redoStack - UNDO: pops from undoStack, pushes to redoStack - REDO: pops from redoStack, pushes to undoStack - CLEAR: empties both stacks Entity fields: undoStack (array), redoStack (array), current (string) (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-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."
+}