@almadar/std 6.1.0 → 6.1.7

package/{dist/exports → behaviors/registry}/atoms/std-rate-limiter.orb

@@ -1,6 +1,7 @@
 {
-  "name": "RateBucketOrbital",
+  "name": "std-rate-limiter",
   "version": "1.0.0",
+  "description": "std-rate-limiter as a Function",
   "orbitals": [
     {
       "name": "RateBucketOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "count",
             "type": "number",
@@ -892,6 +889,5 @@
         }
       ]
     }
-  ],
-  "description": "Rate limiting parameterized for any domain. Provides open and throttled states for controlling request frequency. Tracks request count and throttle status 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/exports → behaviors/registry}/atoms/std-rating.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ReviewOrbital",
+  "name": "std-rating",
   "version": "1.0.0",
+  "description": "Rating atom with star-rating input and display. Absorbs: star-rating.",
   "orbitals": [
     {
       "name": "ReviewOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "rating",
             "type": "number",
@@ -328,6 +325,5 @@
         }
       ]
     }
-  ],
-  "description": "Rating atom with star-rating input and display. Absorbs: star-rating. (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/registry/atoms/std-rl-agent.orb.unconvertible.txt

@@ -0,0 +1,7 @@
+# std-rl-agent (B.2 — runtime invocation failed)
+
+The converter could not invoke this behavior with default params.
+It is a Phase B.3 candidate (hand-author or fix invocation defaults).
+
+- runtime invocation failed: Cannot read properties of undefined (reading 'map')
+- behavior requires non-default params (likely an ML behavior — Phase B.3 candidate)

package/{dist/exports → behaviors/registry}/atoms/std-score-board.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ScoreBoardEntryOrbital",
+  "name": "std-score-board",
   "version": "1.0.0",
+  "description": "Score display atom using the `score-board` pattern. Shows score, high score, combo, multiplier, level.",
   "orbitals": [
     {
       "name": "ScoreBoardEntryOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "score",
             "type": "number",
@@ -244,6 +241,5 @@
         }
       ]
     }
-  ],
-  "description": "Score display atom using the `score-board` pattern. Shows score, high score, combo, multiplier, level. (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}/atoms/std-score.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ScoreEntryOrbital",
+  "name": "std-score",
   "version": "1.0.0",
+  "description": "std-score as a Function",
   "orbitals": [
     {
       "name": "ScoreEntryOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "total",
             "type": "number",
@@ -708,6 +705,5 @@
         }
       ]
     }
-  ],
-  "description": "Score tracking parameterized for any domain. Provides a single-state machine with self-loops for adding, subtracting, resetting, and applying combo multipliers to a score. 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/exports → behaviors/registry}/atoms/std-search.orb

@@ -1,6 +1,7 @@
 {
-  "name": "SearchResultOrbital",
+  "name": "std-search",
   "version": "1.0.0",
+  "description": "std-search as a Function",
   "orbitals": [
     {
       "name": "SearchResultOrbital",
@@ -33,10 +34,6 @@
           {
             "name": "createdAt",
             "type": "string"
-          },
-          {
-            "name": "pendingId",
-            "type": "string"
           }
         ]
       },
@@ -389,6 +386,5 @@
         }
       ]
     }
-  ],
-  "description": "Search behavior parameterized for any domain. Provides a search input that filters entity data by query string. 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/exports → behaviors/registry}/atoms/std-selection.orb

@@ -1,6 +1,7 @@
 {
-  "name": "SelectableItemOrbital",
+  "name": "std-selection",
   "version": "1.0.0",
+  "description": "std-selection as a Function",
   "orbitals": [
     {
       "name": "SelectableItemOrbital",
@@ -33,10 +34,6 @@
           {
             "name": "createdAt",
             "type": "string"
-          },
-          {
-            "name": "pendingId",
-            "type": "string"
           }
         ]
       },
@@ -805,6 +802,5 @@
         }
       ]
     }
-  ],
-  "description": "Selection behavior parameterized for any domain. Provides item selection from a list with confirm/deselect controls. Three states: idle, selecting, selected with transitions for the full lifecycle. (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}/atoms/std-service-custom-bearer.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceCustomBearerOrbital",
+  "name": "std-service-custom-bearer",
   "version": "1.0.0",
+  "description": "Custom REST API behavior with Bearer token authentication. Tests the schema-level service declaration pattern with bearer auth. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceCustomBearerOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "endpoint",
             "type": "string"
@@ -544,19 +541,7 @@
             }
           ]
         }
-      ],
-      "services": [
-        {
-          "name": "custom-bearer-api",
-          "type": "rest",
-          "baseUrl": "https://api.example.com/v2",
-          "auth": {
-            "type": "bearer",
-            "secretEnv": "CUSTOM_BEARER_TOKEN"
-          }
-        }
       ]
     }
-  ],
-  "description": "Custom REST API behavior with Bearer token authentication. Tests the schema-level service declaration pattern with bearer auth. 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 → behaviors/registry}/atoms/std-service-custom-header.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceCustomHeaderOrbital",
+  "name": "std-service-custom-header",
   "version": "1.0.0",
+  "description": "Custom REST API behavior with header-based API key authentication. Tests the schema-level service declaration pattern (no pre-built integration). Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceCustomHeaderOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "endpoint",
             "type": "string"
@@ -544,21 +541,7 @@
             }
           ]
         }
-      ],
-      "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"
-          }
-        }
       ]
     }
-  ],
-  "description": "Custom REST API behavior with header-based API key authentication. Tests the schema-level service declaration pattern (no pre-built integration). 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/behaviors/{exports → registry}/atoms/std-service-custom-noauth.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceCustomNoauthOrbital",
+  "name": "std-service-custom-noauth",
   "version": "1.0.0",
+  "description": "Custom REST API behavior with no authentication. Tests the schema-level service declaration pattern for public APIs. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceCustomNoauthOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "endpoint",
             "type": "string"
@@ -544,15 +541,7 @@
             }
           ]
         }
-      ],
-      "services": [
-        {
-          "name": "custom-noauth-api",
-          "type": "rest",
-          "baseUrl": "https://api.example.com/v4"
-        }
       ]
     }
-  ],
-  "description": "Custom REST API behavior with no authentication. Tests the schema-level service declaration pattern for public APIs. 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 → behaviors/registry}/atoms/std-service-custom-query.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceCustomQueryOrbital",
+  "name": "std-service-custom-query",
   "version": "1.0.0",
+  "description": "Custom REST API behavior with query-string API key authentication. Tests the schema-level service declaration pattern with query-based auth. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceCustomQueryOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "endpoint",
             "type": "string"
@@ -544,21 +541,7 @@
             }
           ]
         }
-      ],
-      "services": [
-        {
-          "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"
-          }
-        }
       ]
     }
-  ],
-  "description": "Custom REST API behavior with query-string API key authentication. Tests the schema-level service declaration pattern with query-based auth. 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 → behaviors/registry}/atoms/std-service-email.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceEmailOrbital",
+  "name": "std-service-email",
   "version": "1.0.0",
+  "description": "Email service integration behavior: compose, send, track delivery status. Wraps the `email` service with call-service for send operations. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceEmailOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "to",
             "type": "string"
@@ -540,6 +537,5 @@
         }
       ]
     }
-  ],
-  "description": "Email service integration behavior: compose, send, track delivery status. Wraps the `email` service with call-service for send 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/exports → behaviors/registry}/atoms/std-service-github.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceGithubOrbital",
+  "name": "std-service-github",
   "version": "1.0.0",
+  "description": "GitHub service integration behavior: idle, creatingPR, prCreated, error. Wraps the `github` integration (listIssues, createPR) with a PR creation flow. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceGithubOrbital",
@@ -74,10 +75,6 @@
           {
             "name": "createdAt",
             "type": "string"
-          },
-          {
-            "name": "pendingId",
-            "type": "string"
           }
         ]
       },
@@ -586,6 +583,5 @@
         }
       ]
     }
-  ],
-  "description": "GitHub service integration behavior: idle, creatingPR, prCreated, error. Wraps the `github` integration (listIssues, createPR) with a PR creation flow. 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/behaviors/{exports → registry}/atoms/std-service-llm.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceLlmOrbital",
+  "name": "std-service-llm",
   "version": "1.0.0",
+  "description": "LLM service integration behavior: generate, classify, summarize text. Wraps the `llm` integration with 4 actions via separate action events. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceLlmOrbital",
@@ -59,10 +60,6 @@
           {
             "name": "createdAt",
             "type": "string"
-          },
-          {
-            "name": "pendingId",
-            "type": "string"
           }
         ]
       },
@@ -671,6 +668,5 @@
         }
       ]
     }
-  ],
-  "description": "LLM service integration behavior: generate, classify, summarize text. Wraps the `llm` integration with 4 actions via separate action 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/behaviors/exports → behaviors/registry}/atoms/std-service-oauth.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceOauthOrbital",
+  "name": "std-service-oauth",
   "version": "1.0.0",
+  "description": "OAuth service integration behavior: authorize, token exchange, refresh. Wraps the `oauth` integration with a multi-step authorization flow. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceOauthOrbital",
@@ -64,10 +65,6 @@
           {
             "name": "createdAt",
             "type": "string"
-          },
-          {
-            "name": "pendingId",
-            "type": "string"
           }
         ]
       },
@@ -764,6 +761,5 @@
         }
       ]
     }
-  ],
-  "description": "OAuth service integration behavior: authorize, token exchange, refresh. Wraps the `oauth` integration with a multi-step authorization flow. 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/behaviors/{exports → registry}/atoms/std-service-redis.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceRedisOrbital",
+  "name": "std-service-redis",
   "version": "1.0.0",
+  "description": "Redis cache integration behavior: get, set, delete with TTL support. Wraps the `redis` service with separate events for each operation. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceRedisOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "key",
             "type": "string"
@@ -580,6 +577,5 @@
         }
       ]
     }
-  ],
-  "description": "Redis cache integration behavior: get, set, delete with TTL support. Wraps the `redis` service with separate events for each operation. 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 → behaviors/registry}/atoms/std-service-storage.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceStorageOrbital",
+  "name": "std-service-storage",
   "version": "1.0.0",
+  "description": "Storage service integration behavior: upload, download, list, delete files. Wraps the `storage` service with separate events for each operation. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceStorageOrbital",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "bucket",
             "type": "string",
@@ -664,6 +661,5 @@
         }
       ]
     }
-  ],
-  "description": "Storage service integration behavior: upload, download, list, delete files. Wraps the `storage` service with separate events for each operation. 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 → behaviors/registry}/atoms/std-service-stripe.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceStripeOrbital",
+  "name": "std-service-stripe",
   "version": "1.0.0",
+  "description": "Stripe payment integration behavior: idle, creating, confirming, succeeded, error. Wraps the `stripe` service integration with a multi-step payment flow. Pure function: params in, OrbitalDefinition out.",
   "orbitals": [
     {
       "name": "ServiceStripeOrbital",
@@ -64,10 +65,6 @@
           {
             "name": "createdAt",
             "type": "string"
-          },
-          {
-            "name": "pendingId",
-            "type": "string"
           }
         ]
       },
@@ -639,6 +636,5 @@
         }
       ]
     }
-  ],
-  "description": "Stripe payment integration behavior: idle, creating, confirming, succeeded, error. Wraps the `stripe` service integration with a multi-step payment flow. 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 → behaviors/registry}/atoms/std-service-twilio.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceTwilioOrbital",
+  "name": "std-service-twilio",
   "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",
@@ -34,10 +35,6 @@
             "name": "createdAt",
             "type": "string"
           },
-          {
-            "name": "pendingId",
-            "type": "string"
-          },
           {
             "name": "to",
             "type": "string"
@@ -611,6 +608,5 @@
         }
       ]
     }
-  ],
-  "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/exports → behaviors/registry}/atoms/std-service-youtube.orb

@@ -1,6 +1,7 @@
 {
-  "name": "ServiceYoutubeOrbital",
+  "name": "std-service-youtube",
   "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",
@@ -64,10 +65,6 @@
           {
             "name": "createdAt",
             "type": "string"
-          },
-          {
-            "name": "pendingId",
-            "type": "string"
           }
         ]
       },
@@ -696,6 +693,5 @@
         }
       ]
     }
-  ],
-  "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."
-}
+  ]
+}