@almadar/std 6.1.0 → 6.1.7

package/{behaviors/exports → dist/behaviors/registry}/molecules/std-service-devops-toolkit.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceDevopsToolkitOrbital",
+  "name": "std-service-devops-toolkit",
   "version": "1.0.0",
+  "description": "DevOps toolkit molecule. Three independent traits on a single page sharing one entity via the event bus: - GitHubTrait: PR creation flow (ghIdle -> creatingPR -> prCreated / ghError) - RedisTrait: cache get/set/delete (redisIdle -> redisExecuting -> redisComplete / redisError) - StorageTrait: file upload/download/list/delete (storageIdle -> storageExecuting -> storageComplete / storageError)",
   "orbitals": [
     {
       "name": "ServiceDevopsToolkitOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "title",
             "type": "string",
@@ -1526,6 +1523,5 @@
         }
       ]
     }
-  ],
-  "description": "DevOps toolkit molecule. Three independent traits on a single page sharing one entity via the event bus: - GitHubTrait: PR creation flow (ghIdle -> creatingPR -> prCreated / ghError) - RedisTrait: cache get/set/delete (redisIdle -> redisExecuting -> redisComplete / redisError) - StorageTrait: file upload/download/list/delete (storageIdle -> storageExecuting -> storageComplete / storageError) Each trait renders its own UI section. No cross-trait events needed (independent flows). (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/{behaviors/exports → dist/behaviors/registry}/molecules/std-service-notification-hub.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceNotificationHubOrbital",
+  "name": "std-service-notification-hub",
   "version": "1.0.0",
+  "description": "Unified notification sender molecule. Composes email and twilio into a single trait with channel selection (Email, SMS, WhatsApp). A single state machine routes to the appropriate call-service based on the chosen channel.",
   "orbitals": [
     {
       "name": "ServiceNotificationHubOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "recipient",
             "type": "string"
@@ -696,6 +693,5 @@
         }
       ]
     }
-  ],
-  "description": "Unified notification sender molecule. Composes email and twilio into a single trait with channel selection (Email, SMS, WhatsApp). A single state machine routes to the appropriate call-service based on the chosen channel. States: idle -> sending -> sent | error Channels: email (call-service email/send), sms (call-service twilio/sendSMS),           whatsapp (call-service twilio/sendWhatsApp) (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/{behaviors/exports → dist/behaviors/registry}/molecules/std-service-payment-flow.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServicePaymentFlowOrbital",
+  "name": "std-service-payment-flow",
   "version": "1.0.0",
+  "description": "Payment flow molecule. Composes stripe payment and email receipt into a single orchestrated flow: pay, then auto-send receipt email.",
   "orbitals": [
     {
       "name": "ServicePaymentFlowOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "amount",
             "type": "number"
@@ -91,7 +88,8 @@
           "category": "interaction",
           "emits": [
             {
-              "event": "SEND_RECEIPT"
+              "event": "SEND_RECEIPT",
+              "scope": "internal"
             }
           ],
           "stateMachine": {
@@ -651,7 +649,8 @@
           "listens": [
             {
               "event": "SEND_RECEIPT",
-              "triggers": "SEND_RECEIPT"
+              "triggers": "SEND_RECEIPT",
+              "scope": "internal"
             }
           ],
           "stateMachine": {
@@ -873,6 +872,5 @@
         }
       ]
     }
-  ],
-  "description": "Payment flow molecule. Composes stripe payment and email receipt into a single orchestrated flow: pay, then auto-send receipt email. Two inline traits share one entity and one page: - Payment trait: idle -> creating -> confirming -> succeeded -> error   Emits SEND_RECEIPT when payment is confirmed. - Receipt trait: waiting -> sending -> sent -> receiptError   Listens for SEND_RECEIPT and calls the email service. Traits on the same page share the event bus automatically. (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/{exports → behaviors/registry}/molecules/std-simulator-game.orb

@@ -1,6 +1,7 @@
 {
-  "name": "SimulatorGameOrbital",
+  "name": "std-simulator-game",
   "version": "1.0.0",
+  "description": "Educational game molecule: menu -> playing -> complete. Uses the `simulator-board` pattern for the playing state.",
   "orbitals": [
     {
       "name": "SimulatorGameOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "score",
             "type": "number",
@@ -229,6 +226,5 @@
         }
       ]
     }
-  ],
-  "description": "Educational game molecule: menu -> playing -> complete. Uses the `simulator-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/{exports → behaviors/registry}/molecules/std-turn-based-battle.orb

@@ -1,6 +1,7 @@
 {
-  "name": "BattleUnitOrbital",
+  "name": "std-turn-based-battle",
   "version": "1.0.0",
+  "description": "Turn-based strategy game molecule (Fire Emblem, XCOM style). Composes game atoms into a two-trait orbital:",
   "orbitals": [
     {
       "name": "BattleUnitOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "turn",
             "type": "number",
@@ -509,6 +506,5 @@
         }
       ]
     }
-  ],
-  "description": "Turn-based strategy game molecule (Fire Emblem, XCOM style). Composes game atoms into a two-trait orbital: 1. BattleFlow trait (primary): menu -> playing -> paused -> gameover    Renders game-menu, game-hud + combat-log, game-over-screen per state. 2. BattleLog trait (secondary): idle state, combat-log pattern.    Only renders when LOG_EVENT fires from the shared event bus. Composition pattern: extractTrait from atom orbitals, assemble into one orbital with one shared entity and one page. (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/{behaviors/exports → dist/behaviors/registry}/organisms/std-agent-assistant.orb

@@ -1,6 +1,7 @@
 {
-  "name": "Agent Assistant",
+  "name": "std-agent-assistant",
   "version": "1.0.0",
+  "description": "Full chat assistant organism. Composes molecule + atoms into a multi-turn conversational agent with memory persistence, context compaction, provider switching, tabbed views, and a memory sidebar drawer.",
   "orbitals": [
     {
       "name": "AssistantOrbital",
@@ -609,10 +610,6 @@
                         }
                       ]
                     }
-                  ],
-                  [
-                    "notify",
-                    "Assistant created successfully"
                   ]
                 ]
               },
@@ -746,10 +743,6 @@
                         }
                       ]
                     }
-                  ],
-                  [
-                    "notify",
-                    "Assistant deleted successfully"
                   ]
                 ]
               },
@@ -883,10 +876,6 @@
                         }
                       ]
                     }
-                  ],
-                  [
-                    "notify",
-                    "Assistant deleted successfully"
                   ]
                 ]
               }
@@ -1201,23 +1190,28 @@
           "listens": [
             {
               "event": "MEMORIZED",
-              "triggers": "INIT"
+              "triggers": "INIT",
+              "scope": "internal"
             },
             {
               "event": "PINNED",
-              "triggers": "INIT"
+              "triggers": "INIT",
+              "scope": "internal"
             },
             {
               "event": "FORGOT",
-              "triggers": "INIT"
+              "triggers": "INIT",
+              "scope": "internal"
             },
             {
               "event": "REINFORCED",
-              "triggers": "INIT"
+              "triggers": "INIT",
+              "scope": "internal"
             },
             {
               "event": "DECAYED",
-              "triggers": "INIT"
+              "triggers": "INIT",
+              "scope": "internal"
             }
           ],
           "stateMachine": {
@@ -1463,10 +1457,12 @@
           "category": "interaction",
           "emits": [
             {
-              "event": "SAVE"
+              "event": "SAVE",
+              "scope": "internal"
             },
             {
-              "event": "MEMORIZED"
+              "event": "MEMORIZED",
+              "scope": "internal"
             }
           ],
           "stateMachine": {
@@ -1602,10 +1598,6 @@
                   [
                     "emit",
                     "MEMORIZED"
-                  ],
-                  [
-                    "notify",
-                    "Memory created successfully"
                   ]
                 ]
               }
@@ -1804,10 +1796,6 @@
                     "create",
                     "Memory",
                     "@payload.data"
-                  ],
-                  [
-                    "notify",
-                    "Memory created successfully"
                   ]
                 ]
               },
@@ -4694,10 +4682,12 @@
           "category": "interaction",
           "emits": [
             {
-              "event": "SAVE"
+              "event": "SAVE",
+              "scope": "internal"
             },
             {
-              "event": "SWITCHED"
+              "event": "SWITCHED",
+              "scope": "internal"
             },
             {
               "event": "PROVIDER_CHANGED",
@@ -5111,10 +5101,6 @@
                         }
                       ]
                     }
-                  ],
-                  [
-                    "notify",
-                    "ProviderConfig updated successfully"
                   ]
                 ]
               }
@@ -5458,7 +5444,8 @@
           "listens": [
             {
               "event": "SWITCHED",
-              "triggers": "SWITCHED"
+              "triggers": "SWITCHED",
+              "scope": "internal"
             }
           ],
           "stateMachine": {
@@ -6331,6 +6318,5 @@
         }
       ]
     }
-  ],
-  "description": "Full chat assistant organism. Composes molecule + atoms into a multi-turn conversational agent with memory persistence, context compaction, provider switching, tabbed views, and a memory sidebar drawer. Composed from: - stdAgentConversation: multi-turn chat with generate + context tracking - stdAgentMemory: memory lifecycle (memorize, recall, pin, forget, reinforce, decay) - stdAgentContextWindow: token monitoring and auto-compaction - stdAgentProvider: provider switching based on task complexity - stdTabs: Chat / Memory / Settings tab navigation - stdDrawer: memory sidebar for quick recall Cross-trait events: - MEMORIZE_RESPONSE (Conversation -> Memory): auto-memorize important responses - PROVIDER_CHANGED (Provider -> Conversation): notify conversation of provider switch Pages: /chat (initial), /memory, /settings (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."
-}
+  ]
+}