@almadar/std 5.2.2 → 5.3.0

package/dist/behaviors/exports/organisms/std-service-marketplace.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-service-marketplace",
+  "name": "ServiceMarketplace",
   "version": "1.0.0",
-  "description": "Service marketplace organism. Composes molecules and atoms via compose: - stdList(Product): product catalog with CRUD - stdServiceOauth(AuthSession): OAuth login with standalone provider picker - stdServicePaymentFlow(OrderPayment): Stripe payment + email receipt - stdList(Order): order history with CRUD",
   "orbitals": [
     {
       "name": "ProductOrbital",
@@ -443,6 +442,10 @@
                   [
                     "emit",
                     "PRODUCT_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Product created successfully"
                   ]
                 ]
               }
@@ -611,6 +614,10 @@
                   [
                     "emit",
                     "PRODUCT_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Product updated successfully"
                   ]
                 ]
               }
@@ -1030,6 +1037,10 @@
                   [
                     "emit",
                     "PRODUCT_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Product deleted successfully"
                   ]
                 ]
               },
@@ -1092,7 +1103,8 @@
             }
           ]
         }
-      ]
+      ],
+      "services": []
     },
     {
       "name": "AuthSessionOrbital",
@@ -2136,7 +2148,8 @@
             }
           ]
         }
-      ]
+      ],
+      "services": []
     },
     {
       "name": "OrderPaymentOrbital",
@@ -3381,7 +3394,8 @@
             }
           ]
         }
-      ]
+      ],
+      "services": []
     },
     {
       "name": "OrderOrbital",
@@ -3805,6 +3819,10 @@
                   [
                     "emit",
                     "ORDER_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Order created successfully"
                   ]
                 ]
               }
@@ -3972,6 +3990,10 @@
                   [
                     "emit",
                     "ORDER_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Order updated successfully"
                   ]
                 ]
               }
@@ -4374,6 +4396,10 @@
                   [
                     "emit",
                     "ORDER_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Order deleted successfully"
                   ]
                 ]
               },
@@ -4435,7 +4461,9 @@
             }
           ]
         }
-      ]
+      ],
+      "services": []
     }
-  ]
-}
+  ],
+  "description": "Service marketplace organism. Composes molecules and atoms via compose: - stdList(Product): product catalog with CRUD - stdServiceOauth(AuthSession): OAuth login with standalone provider picker - stdServicePaymentFlow(OrderPayment): Stripe payment + email receipt - stdList(Order): order history with CRUD Cross-orbital connections: - CHECKOUT: ProductBrowse -> OrderPaymentPayment (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/organisms/std-service-research-assistant.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-service-research-assistant",
+  "name": "ResearchAssistant",
   "version": "1.0.0",
-  "description": "Content research assistant organism. Composes service atoms/molecules via compose: - stdServiceContentPipeline(Research): YouTube search + LLM summarization - stdServiceRedis(CacheEntry): Redis cache management (standalone) - stdServiceStorage(Report): saving research reports to storage (standalone) - stdServiceCustomBearer(KnowledgeQuery): custom knowledge API queries (standalone)",
   "orbitals": [
     {
       "name": "ResearchOrbital",
@@ -3553,5 +3552,17 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "services": [
+    {
+      "name": "custom-bearer-api",
+      "type": "rest",
+      "baseUrl": "https://api.knowledge-base.example.com",
+      "auth": {
+        "type": "bearer",
+        "secretEnv": "CUSTOM_BEARER_TOKEN"
+      }
+    }
+  ],
+  "description": "Content research assistant organism. Composes service atoms/molecules via compose: - stdServiceContentPipeline(Research): YouTube search + LLM summarization - stdServiceRedis(CacheEntry): Redis cache management (standalone) - stdServiceStorage(Report): saving research reports to storage (standalone) - stdServiceCustomBearer(KnowledgeQuery): custom knowledge API queries (standalone) Cross-orbital connections: (none - each page operates independently, user navigates via dashboard nav) (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/organisms/std-social-feed.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-social-feed",
+  "name": "SocialFeed",
   "version": "1.0.0",
-  "description": "Social feed organism. Composes molecules via compose: - stdDetail(Post): browse + create + view posts - stdMessaging(Comment): messaging thread for comments",
   "orbitals": [
     {
       "name": "PostOrbital",
@@ -373,6 +372,10 @@
                     "render-ui",
                     "modal",
                     null
+                  ],
+                  [
+                    "notify",
+                    "Post created successfully"
                   ]
                 ]
               }
@@ -983,6 +986,10 @@
                     "render-ui",
                     "modal",
                     null
+                  ],
+                  [
+                    "notify",
+                    "Comment created successfully"
                   ]
                 ]
               }
@@ -1234,5 +1241,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Social feed organism. Composes molecules via compose: - stdDetail(Post): browse + create + view posts - stdMessaging(Comment): messaging thread for comments Pages: /feed (initial), /messages Connections: COMMENT event wires posts to comments. (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/organisms/std-stem-lab.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-stem-lab",
+  "name": "STEM Lab",
   "version": "1.0.0",
-  "description": "STEM lab organism. Composes: stdSimulatorGame(Experiment) + stdClassifierGame(Classification) + stdDisplay(LabResult)",
   "orbitals": [
     {
       "name": "ExperimentOrbital",
@@ -1918,5 +1917,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "STEM lab organism. Composes: stdSimulatorGame(Experiment) + stdClassifierGame(Classification)         + stdDisplay(LabResult) Pages: /simulator (initial), /classifier, /results (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/organisms/std-strategy-game.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-strategy-game",
+  "name": "Strategy Game",
   "version": "1.0.0",
-  "description": "Strategy game organism. Composes: stdTurnBasedBattle(ArmyBattle) + stdOverworld(Territory) + stdDisplay(Resource)",
   "orbitals": [
     {
       "name": "ArmyBattleOrbital",
@@ -2439,5 +2438,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Strategy game organism. Composes: stdTurnBasedBattle(ArmyBattle) + stdOverworld(Territory) + stdDisplay(Resource) Pages: /battle, /map (initial), /resources (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/organisms/std-trading-dashboard.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-trading-dashboard",
+  "name": "Trading Dashboard",
   "version": "1.0.0",
-  "description": "Trading dashboard organism. Composes: stdDisplay(Portfolio) + stdList(TradeOrder) + stdAsync(MarketFeed)",
   "orbitals": [
     {
       "name": "PortfolioOrbital",
@@ -1837,6 +1836,10 @@
                   [
                     "emit",
                     "TRADE_ORDER_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "TradeOrder created successfully"
                   ]
                 ]
               }
@@ -2004,6 +2007,10 @@
                   [
                     "emit",
                     "TRADE_ORDER_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "TradeOrder updated successfully"
                   ]
                 ]
               }
@@ -2406,6 +2413,10 @@
                   [
                     "emit",
                     "TRADE_ORDER_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "TradeOrder deleted successfully"
                   ]
                 ]
               },
@@ -2763,6 +2774,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "MarketFeed created successfully"
                   ]
                 ]
               },
@@ -3055,5 +3070,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Trading dashboard organism. Composes: stdDisplay(Portfolio) + stdList(TradeOrder) + stdAsync(MarketFeed) Pages: /portfolio (initial), /orders, /market (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."
+}