@almadar/std 5.2.2 → 5.3.0

package/dist/exports/molecules/std-negotiator-game.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-negotiator-game",
+  "name": "NegotiatorGameOrbital",
   "version": "1.0.0",
-  "description": "Educational game molecule: menu -> playing -> complete. Uses the `negotiator-board` pattern for the playing state.",
   "orbitals": [
     {
       "name": "NegotiatorGameOrbital",
@@ -226,5 +225,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Educational game molecule: menu -> playing -> complete. Uses the `negotiator-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/molecules/std-platformer-game.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-platformer-game",
+  "name": "PlatLevelOrbital",
   "version": "1.0.0",
-  "description": "Side-scrolling platformer game molecule. Composes game atoms into a two-trait orbital:",
   "orbitals": [
     {
       "name": "PlatLevelOrbital",
@@ -549,5 +548,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Side-scrolling platformer game molecule. Composes game atoms into a two-trait orbital: 1. PlatformerFlow trait (primary): menu -> playing -> paused -> gameover    Renders game-menu, platformer-canvas, game-over-screen per state. 2. PlatformerCanvas trait (secondary): extracted from stdPlatformerCanvas,    INIT render-ui removed (standalone: false pattern) so the flow trait    owns the main render slot. (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/molecules/std-puzzle-game.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-puzzle-game",
+  "name": "PuzzleBoardOrbital",
   "version": "1.0.0",
-  "description": "Puzzle game molecule. Composes game atoms into a two-trait orbital:",
   "orbitals": [
     {
       "name": "PuzzleBoardOrbital",
@@ -576,5 +575,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Puzzle game molecule. Composes game atoms into a two-trait orbital: 1. PuzzleFlow trait (primary): menu -> playing -> paused -> gameover    Renders game-menu, game-canvas-2d with score-board, game-over-screen. 2. PuzzleScore trait (secondary): extracted from stdScoreBoard,    INIT render-ui removed (standalone: false pattern) so the flow trait    owns the main render slot. (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/molecules/std-quiz.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-quiz",
+  "name": "QuizItemOrbital",
   "version": "1.0.0",
-  "description": "Quiz molecule composing flip-card atom with question/answer flow. Absorbs: quiz-block.",
   "orbitals": [
     {
       "name": "QuizItemOrbital",
@@ -1066,5 +1065,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Quiz molecule composing flip-card atom with question/answer flow. Absorbs: quiz-block. (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/molecules/std-sequencer-game.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-sequencer-game",
+  "name": "SequencerGameOrbital",
   "version": "1.0.0",
-  "description": "Educational game molecule: menu -> playing -> complete. Uses the `sequencer-board` pattern for the playing state.",
   "orbitals": [
     {
       "name": "SequencerGameOrbital",
@@ -226,5 +225,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Educational game molecule: menu -> playing -> complete. Uses the `sequencer-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/molecules/std-service-content-pipeline.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-service-content-pipeline",
+  "name": "ServiceContentPipelineOrbital",
   "version": "1.0.0",
-  "description": "Content research pipeline molecule. Composes youtube search + llm summarization into a sequential pipeline: search -> select -> summarize.",
   "orbitals": [
     {
       "name": "ServiceContentPipelineOrbital",
@@ -912,5 +911,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Content research pipeline molecule. Composes youtube search + llm summarization into a sequential pipeline: search -> select -> summarize. Single trait with six states (idle, searching, results, summarizing, complete, error) that orchestrates call-service effects for youtube and llm services. (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/molecules/std-service-custom-api-tester.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-service-custom-api-tester",
+  "name": "custom-header-api",
   "version": "1.0.0",
-  "description": "Unified API tester molecule that exercises all 4 custom REST auth patterns (header API key, bearer token, query param API key, no auth) with a tab selector. Single entity, single trait, 4 call events. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceCustomApiTesterOrbital",
@@ -817,7 +816,46 @@
             }
           ]
         }
+      ],
+      "services": [
+        {
+          "name": "custom-header-api",
+          "type": "rest",
+          "baseUrl": "https://api.example.com/v1",
+          "auth": {
+            "type": "api-key",
+            "keyName": "X-API-Key",
+            "location": "header",
+            "secretEnv": "CUSTOM_API_SECRET"
+          }
+        },
+        {
+          "name": "custom-bearer-api",
+          "type": "rest",
+          "baseUrl": "https://api.example.com/v2",
+          "auth": {
+            "type": "bearer",
+            "secretEnv": "CUSTOM_BEARER_TOKEN"
+          }
+        },
+        {
+          "name": "custom-query-api",
+          "type": "rest",
+          "baseUrl": "https://api.example.com/v3",
+          "auth": {
+            "type": "api-key",
+            "keyName": "api_key",
+            "location": "query",
+            "secretEnv": "CUSTOM_QUERY_KEY"
+          }
+        },
+        {
+          "name": "custom-noauth-api",
+          "type": "rest",
+          "baseUrl": "https://api.example.com/v4"
+        }
       ]
     }
-  ]
-}
+  ],
+  "description": "Unified API tester molecule that exercises all 4 custom REST auth patterns (header API key, bearer token, query param API key, no auth) with a tab selector. Single entity, single trait, 4 call events. 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/exports/molecules/std-service-devops-toolkit.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-service-devops-toolkit",
+  "name": "ServiceDevopsToolkitOrbital",
   "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",
@@ -1523,5 +1522,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "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/dist/exports/molecules/std-service-notification-hub.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-service-notification-hub",
+  "name": "ServiceNotificationHubOrbital",
   "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",
@@ -693,5 +692,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "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/dist/exports/molecules/std-service-payment-flow.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-service-payment-flow",
+  "name": "ServicePaymentFlowOrbital",
   "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",
@@ -870,5 +869,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "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/molecules/std-simulator-game.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-simulator-game",
+  "name": "SimulatorGameOrbital",
   "version": "1.0.0",
-  "description": "Educational game molecule: menu -> playing -> complete. Uses the `simulator-board` pattern for the playing state.",
   "orbitals": [
     {
       "name": "SimulatorGameOrbital",
@@ -226,5 +225,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "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/molecules/std-turn-based-battle.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-turn-based-battle",
+  "name": "BattleUnitOrbital",
   "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",
@@ -506,5 +505,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "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/dist/exports/organisms/std-agent-assistant.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-agent-assistant",
+  "name": "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",
@@ -610,6 +609,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "Assistant created successfully"
                   ]
                 ]
               },
@@ -743,6 +746,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "Assistant deleted successfully"
                   ]
                 ]
               },
@@ -876,6 +883,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "Assistant deleted successfully"
                   ]
                 ]
               }
@@ -1591,6 +1602,10 @@
                   [
                     "emit",
                     "MEMORIZED"
+                  ],
+                  [
+                    "notify",
+                    "Memory created successfully"
                   ]
                 ]
               }
@@ -1789,6 +1804,10 @@
                     "create",
                     "Memory",
                     "@payload.data"
+                  ],
+                  [
+                    "notify",
+                    "Memory created successfully"
                   ]
                 ]
               },
@@ -5092,6 +5111,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "ProviderConfig updated successfully"
                   ]
                 ]
               }
@@ -6308,5 +6331,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "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."
+}