@almadar/std 5.2.2 → 5.4.0

package/dist/behaviors/exports/atoms/std-agent-provider.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-agent-provider",
+  "name": "AgentProviderOrbital",
   "version": "1.0.0",
-  "description": "Provider routing atom for agent model/provider switching. Composes UI atoms (stdModal for switch form, stdNotification for confirmation) with an agent trait that handles agent/switch-provider, agent/provider, and agent/model operators.",
   "orbitals": [
     {
       "name": "AgentProviderOrbital",
@@ -36,6 +35,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "currentProvider",
             "type": "string",
@@ -401,6 +404,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "AgentProvider updated successfully"
                   ]
                 ]
               }
@@ -894,5 +901,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Provider routing atom for agent model/provider switching. Composes UI atoms (stdModal for switch form, stdNotification for confirmation) with an agent trait that handles agent/switch-provider, agent/provider, and agent/model operators. (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-agent-search.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-agent-search",
+  "name": "AgentSearchOrbital",
   "version": "1.0.0",
-  "description": "Code search flow atom for agent-powered codebase searching. Composes stdBrowse (results table) with an agent trait that handles agent/search-code.",
   "orbitals": [
     {
       "name": "AgentSearchOrbital",
@@ -36,6 +35,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "query",
             "type": "string",
@@ -423,5 +426,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Code search flow atom for agent-powered codebase searching. Composes stdBrowse (results table) with an agent trait that handles agent/search-code. (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-agent-session.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-agent-session",
+  "name": "AgentSessionOrbital",
   "version": "1.0.0",
-  "description": "Session lifecycle atom for agent session management. Composes UI atoms (stdBrowse for session list, stdModal for fork label form) with an agent trait that handles agent/fork, agent/label, and agent/session-id.",
   "orbitals": [
     {
       "name": "AgentSessionOrbital",
@@ -36,6 +35,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "sessionId",
             "type": "string",
@@ -407,6 +410,10 @@
                   [
                     "emit",
                     "LABELED"
+                  ],
+                  [
+                    "notify",
+                    "AgentSession updated successfully"
                   ]
                 ]
               }
@@ -571,6 +578,10 @@
                   [
                     "emit",
                     "FORKED"
+                  ],
+                  [
+                    "notify",
+                    "AgentSession created successfully"
                   ]
                 ]
               },
@@ -604,6 +615,10 @@
                   [
                     "emit",
                     "FORKED"
+                  ],
+                  [
+                    "notify",
+                    "AgentSession created successfully"
                   ]
                 ]
               },
@@ -757,5 +772,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Session lifecycle atom for agent session management. Composes UI atoms (stdBrowse for session list, stdModal for fork label form) with an agent trait that handles agent/fork, agent/label, and agent/session-id. (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-agent-step-progress.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-agent-step-progress",
+  "name": "AgentStepProgressOrbital",
   "version": "1.0.0",
-  "description": "Pipeline/workflow step indicator atom. Tracks progress through a series of named steps with start/advance/complete/fail lifecycle. Listens for ADVANCE, COMPLETE, FAIL so orchestrating traits can drive the progress externally.",
   "orbitals": [
     {
       "name": "AgentStepProgressOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "currentStep",
             "type": "number",
@@ -986,5 +989,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Pipeline/workflow step indicator atom. Tracks progress through a series of named steps with start/advance/complete/fail lifecycle. Listens for ADVANCE, COMPLETE, FAIL so orchestrating traits can drive the progress externally. (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-agent-token-gauge.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-agent-token-gauge",
+  "name": "AgentTokenGaugeOrbital",
   "version": "1.0.0",
-  "description": "Token usage display atom with threshold-based state transitions. Shows current token count, usage percentage, and progress bar. Transitions from normal -> warning -> critical based on configurable thresholds. Provides compact and reset actions.",
   "orbitals": [
     {
       "name": "AgentTokenGaugeOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "current",
             "type": "number",
@@ -1613,5 +1616,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Token usage display atom with threshold-based state transitions. Shows current token count, usage percentage, and progress bar. Transitions from normal -> warning -> critical based on configurable thresholds. Provides compact and reset actions. (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-agent-tool-call.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-agent-tool-call",
+  "name": "AgentToolCallOrbital",
   "version": "1.0.0",
-  "description": "Tool execution atom for agent tool invocation. Composes UI atoms (stdModal for invoke form, stdAgentActivityLog for call history) with an agent trait that handles agent/invoke and TOOL_STARTED/TOOL_COMPLETED emits.",
   "orbitals": [
     {
       "name": "AgentToolCallOrbital",
@@ -36,6 +35,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "toolName",
             "type": "string",
@@ -387,6 +390,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "AgentToolCall created successfully"
                   ]
                 ]
               }
@@ -734,5 +741,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Tool execution atom for agent tool invocation. Composes UI atoms (stdModal for invoke form, stdAgentActivityLog for call history) with an agent trait that handles agent/invoke and TOOL_STARTED/TOOL_COMPLETED emits. (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-async.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-async",
+  "name": "AsyncTaskOrbital",
   "version": "1.0.0",
-  "description": "Async operation behavior: idle, loading, success, error. Covers fetch, submit, retry, and polling patterns in one molecule. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "AsyncTaskOrbital",
@@ -34,6 +33,10 @@
           {
             "name": "createdAt",
             "type": "string"
+          },
+          {
+            "name": "pendingId",
+            "type": "string"
           }
         ]
       },
@@ -231,6 +234,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "AsyncTask created successfully"
                   ]
                 ]
               },
@@ -431,5 +438,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Async operation behavior: idle, loading, success, error. Covers fetch, submit, retry, and polling patterns in one molecule. 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-autoregressive.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-autoregressive",
+  "name": "AutoregressiveOrbital",
   "version": "1.0.0",
-  "description": "Autoregressive text generation molecule (GPT-style). Forward pass in a self-transition loop: generates one token at a time until EOS token or max length is reached.",
   "orbitals": [
     {
       "name": "AutoregressiveOrbital",
@@ -418,4 +417,4 @@
       ]
     }
   ]
-}
+}

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

@@ -1,7 +1,6 @@
 {
-  "name": "std-browse",
+  "name": "BrowseItemOrbital",
   "version": "1.0.0",
-  "description": "Data grid browsing atom. Renders a list of entities with configurable item actions. The browsing view that molecules compose with modal/confirmation atoms.",
   "orbitals": [
     {
       "name": "BrowseItemOrbital",
@@ -34,6 +33,10 @@
           {
             "name": "createdAt",
             "type": "string"
+          },
+          {
+            "name": "pendingId",
+            "type": "string"
           }
         ],
         "instances": [
@@ -243,5 +246,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Data grid browsing atom. Renders a list of entities with configurable item actions. The browsing view that molecules compose with modal/confirmation atoms. (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-cache-aside.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-cache-aside",
+  "name": "CacheEntryOrbital",
   "version": "1.0.0",
-  "description": "Cache management behavior: empty, cached, stale with fetch/invalidate cycle. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "CacheEntryOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "hitCount",
             "type": "number",
@@ -637,6 +640,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "CacheEntry updated successfully"
                   ]
                 ]
               },
@@ -1089,5 +1096,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Cache management behavior: empty, cached, stale with fetch/invalidate cycle. 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-calendar.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-calendar",
+  "name": "CalendarEventOrbital",
   "version": "1.0.0",
-  "description": "Calendar browsing atom with month/day/slot views. Absorbs: calendar-grid, day-cell, time-slot-cell, date-range-selector.",
   "orbitals": [
     {
       "name": "CalendarEventOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "date",
             "type": "string",
@@ -767,5 +770,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Calendar browsing atom with month/day/slot views. Absorbs: calendar-grid, day-cell, time-slot-cell, date-range-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-circuit-breaker.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-circuit-breaker",
+  "name": "ServiceNodeOrbital",
   "version": "1.0.0",
-  "description": "Circuit breaker pattern behavior: closed, open, halfOpen. Protects services from cascading failures with automatic recovery. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceNodeOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "failureCount",
             "type": "number",
@@ -991,5 +994,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Circuit breaker pattern behavior: closed, open, halfOpen. Protects services from cascading failures with automatic recovery. 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-collision.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-collision",
+  "name": "CollidableBodyOrbital",
   "version": "1.0.0",
-  "description": "std-collision as a Function",
   "orbitals": [
     {
       "name": "CollidableBodyOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "x",
             "type": "number",
@@ -686,5 +689,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Game collision detection parameterized for any domain. Provides idle and detecting states for checking collisions between game entities. Tracks collision targets via entity fields. 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-combat-log.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-combat-log",
+  "name": "CombatLogEntryOrbital",
   "version": "1.0.0",
-  "description": "Scrollable combat event log atom using the `combat-log` pattern. Displays timestamped combat events with icons and colors. Supports appending new events and clearing the log.",
   "orbitals": [
     {
       "name": "CombatLogEntryOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "type",
             "type": "string",
@@ -260,5 +263,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Scrollable combat event log atom using the `combat-log` pattern. Displays timestamped combat events with icons and colors. Supports appending new events and clearing the log. (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-combat.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-combat",
+  "name": "CombatantOrbital",
   "version": "1.0.0",
-  "description": "Attack cycle behavior: ready, attacking, cooldown, defeated. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "CombatantOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "hp",
             "type": "number",
@@ -413,5 +416,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Attack cycle behavior: ready, attacking, cooldown, defeated. 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-confirmation.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-confirmation",
+  "name": "ConfirmActionOrbital",
   "version": "1.0.0",
-  "description": "std-confirmation as a Function",
   "orbitals": [
     {
       "name": "ConfirmActionOrbital",
@@ -492,5 +491,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Confirmation dialog behavior parameterized for any domain. Provides a two-step confirm/cancel flow before performing destructive actions. The caller handles the actual action via emits/listens. 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-dialogue-box.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-dialogue-box",
+  "name": "DialogueNodeOrbital",
   "version": "1.0.0",
-  "description": "RPG dialogue atom using the `dialogue-box` pattern. Shows speaker, portrait, typewriter text, and choices.",
   "orbitals": [
     {
       "name": "DialogueNodeOrbital",
@@ -35,6 +34,10 @@
             "name": "createdAt",
             "type": "string"
           },
+          {
+            "name": "pendingId",
+            "type": "string"
+          },
           {
             "name": "speaker",
             "type": "string",
@@ -241,5 +244,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "RPG dialogue atom using the `dialogue-box` pattern. Shows speaker, portrait, typewriter text, and choices. (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."
+}