@almadar/std 16.245.0 → 16.246.0

package/behaviors/lolo/agent/atoms/std-agent-context.lolo

@@ -5,11 +5,16 @@ type AgentChatMessage = {
   role : "user" | "assistant"
   content : string!
 }
-type AgentTool = {
-  event : event
-  read : string
-  scope : "declared"
+type AgentToolScope = {
+  scope : "declared"!
 }
+type AgentToolInput = {
+  event : EventAddress!
+}
+type AgentToolRead = {
+  read : string!
+}
+type AgentTool = AgentToolScope | AgentToolInput | AgentToolRead
 
 orbital AgentContextOrbital {
   type ContextSummarized = Event { summary : string, keyPoints : [string] } "Fired when the older turns have been summarized"

package/behaviors/lolo/agent/atoms/std-agent-memory.lolo

@@ -5,11 +5,16 @@ type AgentChatMessage = {
   role : "user" | "assistant"
   content : string!
 }
-type AgentTool = {
-  event : event
-  read : string
-  scope : "declared"
+type AgentToolScope = {
+  scope : "declared"!
 }
+type AgentToolInput = {
+  event : EventAddress!
+}
+type AgentToolRead = {
+  read : string!
+}
+type AgentTool = AgentToolScope | AgentToolInput | AgentToolRead
 type AgentMemoryRow = {
   id : string!
   content : string!

package/behaviors/lolo/agent/atoms/std-agent-proposal.lolo

@@ -2,11 +2,16 @@ app std-agent-proposal "1.0.0"
 "std-agent-proposal — an agent that reads what the person hands over, works out a structured proposal, and commits nothing until they approve it. The app starts it with PROPOSAL_REQUESTED { input, context } (any trait emitting it, or the person typing into the start form when `showInputForm` is on). A second std-agent-tool-loop answers with `instructions`, `prompt` and `tools` as the signed-in person — `quiet`, its reply and failure renamed PROPOSAL_LOOP_REPLIED / PROPOSAL_LOOP_FAILED so they never reach the assistant's chat — and submits its proposal through one declared input, PROPOSE (its @description is the tool text): a summary and a list of items, each a flat map of scalar values the app names. The person reviews it (the summary, the items drawn with `itemPattern` and `itemFields`) and chooses: Approve emits PROPOSAL_APPROVED { proposal } for the app to commit (the app owns the commit; this atom writes nothing); Revise sends their written feedback back to the agent, which proposes again; Discard emits PROPOSAL_DISCARDED. Cancel while the agent works aborts its model call and emits PROPOSAL_CANCELLED. A run that fails, or ends without proposing, shows its error with Retry and Discard. The panel renders into `panelSlot`. Import the orbital once per app: `orbital Proposal = Proposal.orbitals.AgentProposalOrbital { config { instructions: \"…\", prompt: \"…\", itemFields: […] } }`, restating `tools` with PROPOSE addressed by its local orbital name (`{ event: Proposal.AgentProposalWorkflow.PROPOSE }`). Instructions, prompts, item fields and labels are the app's vocabulary, declared in config."
 ;; @capabilities "agent proposal, review before commit, human approval of agent output, approve or revise agent suggestions, structured proposal review, ai drafts for approval, extract then confirm"
 
-type AgentTool = {
-  event : event
-  read : string
-  scope : "declared"
+type AgentToolScope = {
+  scope : "declared"!
 }
+type AgentToolInput = {
+  event : EventAddress!
+}
+type AgentToolRead = {
+  read : string!
+}
+type AgentTool = AgentToolScope | AgentToolInput | AgentToolRead
 type AgentChatMessage = {
   role : "user" | "assistant"
   content : string!

package/behaviors/lolo/agent/atoms/std-agent-session.lolo

@@ -24,11 +24,16 @@ type AgentThreadRow = {
   content : string!
   createdAt : number
 }
-type AgentTool = {
-  event : event
-  read : string
-  scope : "declared"
+type AgentToolScope = {
+  scope : "declared"!
 }
+type AgentToolInput = {
+  event : EventAddress!
+}
+type AgentToolRead = {
+  read : string!
+}
+type AgentTool = AgentToolScope | AgentToolInput | AgentToolRead
 type AgentToolKind = "input" | "read" | "invalid"
 type AgentMessageEntry = {
   type : "message"!

package/behaviors/lolo/agent/atoms/std-agent-suggestions.lolo

@@ -2,11 +2,16 @@ app std-agent-suggestions "1.0.0"
 "std-agent-suggestions — an agent that proactively proposes things to the signed-in person, who accepts or dismisses each one. The agent proposes through one declared input, PROPOSE_SUGGESTION (its @description is the tool text): a kind, a title, a body that gives its reasoning, an optional action (a name the app routes) with a payload, an optional href, and a subject (what it is about). A suggestion's signature is kind:action:subject; a signature that was ever proposed to this person, accepted or dismissed included, is never stored again (SUGGESTION_DUPLICATE), and no more than `maxPending` wait at once (SUGGESTION_LIMIT_REACHED). `kinds` and `actions`, when listed, are the only values accepted (SUGGESTION_REJECTED). The agent runs on its own: any trait emitting SUGGESTIONS_TRIGGERED (or an app event routed into AgentSuggestionTrigger's TRIGGERED by re-binding that trait in the import body with `omit { AgentSuggestionTrigger }` and its own `listens`) asks for a run, and once `cooldownMinutes` have passed since this person's last run a second std-agent-tool-loop answers `prompt` with `tools` as the signed-in person — `quiet`, so it streams no live steps and toasts no failure, and its reply and failure are renamed PROACTIVE_REPLIED / PROACTIVE_FAILED so they never reach the assistant's chat. AgentSuggestionInbox lists the pending suggestions with Accept and Dismiss and an empty state that offers to look again (SUGGESTIONS_ANALYZE_REQUESTED). Accept stores accepted, emits SUGGESTION_ACCEPTED { action, payload, href, … } for the app to route (and navigates to `href` when the suggestion has one); Dismiss stores dismissed and emits SUGGESTION_DISMISSED. The inbox renders into `panelSlot`: `main` inline (the content of a std-panel-launcher), or `modal`/`drawer` opened with OPEN and closed with CLOSE (set std-app-layout's notificationClickEvent, or a topBarActions event, to SUGGESTIONS_OPEN_REQUESTED). Import the orbital once per app: `orbital Suggestions = Suggest.orbitals.AgentSuggestionsOrbital { entity MySuggestion  entities { AgentSuggestionRun: MySuggestionRun } config { … } }`, retargeting the records onto owner-scoped entities (`ownerId` a relation to your [identity] roster, with @read/@create/@update); a suggestion's proposer, inbox and trigger read only the rows whose ownerId is the signed-in person. PROPOSE_SUGGESTION's refusals (SUGGESTION_DUPLICATE, SUGGESTION_LIMIT_REACHED, SUGGESTION_REJECTED) are the agent's tool response; no trait listens to them. Suggestion kinds, actions and prompts are the app's vocabulary, declared in config."
 ;; @capabilities "proactive suggestions, agent recommendations, suggestion inbox, next best action, accept or dismiss suggestions, notification bell suggestions, agent proposals"
 
-type AgentTool = {
-  event : event
-  read : string
-  scope : "declared"
+type AgentToolScope = {
+  scope : "declared"!
 }
+type AgentToolInput = {
+  event : EventAddress!
+}
+type AgentToolRead = {
+  read : string!
+}
+type AgentTool = AgentToolScope | AgentToolInput | AgentToolRead
 type AgentChatMessage = {
   role : "user" | "assistant"
   content : string!

package/behaviors/lolo/agent/atoms/std-agent-tool-loop.lolo

@@ -1,11 +1,16 @@
 app std-agent-tool-loop "2.0.0"
 "std-agent-tool-loop — answers a conversation by operating the running app as the caller, through `call-service llm call-tools`. Its `tools` are `{ scope: declared }` (every declared external input plus a read over every persisted entity), or named declared inputs (addressed like a listens source: `Trait.EVENT`, `Orbital.Trait.EVENT`) and entities to read; each input fires as the signed-in user through the ordinary dispatch (guards and entity policies apply) and each read returns only the rows the caller may read. Headless: the conversation UI (std-agent-session) shows the reply; a failure shows as a toast, unless `quiet` is on (a background run nobody is watching: no live steps and no toast). CONVERSE carries the conversation (and optionally what std-agent-memory recalled); ASSISTANT_STEP carries each step live while it works (a model call, a tool it used, what the app answered) to the asking tab; ASSISTANT_REPLIED carries the reply, every step and the token usage; ASSISTANT_REPLY_FAILED carries the error. These names are the assistant contract std-agent-session's conversation hears from any orbital. Compose with std-agent-session (the conversation) and std-agent-trace (the step record)."
 
-type AgentTool = {
-  event : event
-  read : string
-  scope : "declared"
+type AgentToolScope = {
+  scope : "declared"!
 }
+type AgentToolInput = {
+  event : EventAddress!
+}
+type AgentToolRead = {
+  read : string!
+}
+type AgentTool = AgentToolScope | AgentToolInput | AgentToolRead
 type AgentChatMessage = {
   role : "user" | "assistant"
   content : string!

package/behaviors/lolo/agent/organisms/std-agent-assistant.lolo

@@ -1,11 +1,16 @@
 app std-agent-assistant "2.0.0"
 "std-agent-assistant — an in-app assistant that operates the running app for the signed-in user. Each section's floating button opens it in a side panel docked beside the page (std-panel-launcher; a side sheet on small screens), where the conversation shows every step the assistant takes live as it works; /assistant is the same conversation as a full page, in the app's own shell (pass `appName` and `navItems`); past conversations and what the assistant remembers open in place from its toolbar (Back returns to the chat), on either surface. One request flows down a chain of std agent atoms on the bus: the conversation (std-agent-session) SENDs → CONVERSE → std-agent-context bounds it → std-agent-memory adds what it recalls → std-agent-tool-loop answers it through `call-service llm call-tools`, firing only the inputs and reading only the entities its `tools` allow, as the signed-in user → ASSISTANT_REPLIED goes back to the conversation, to memory (remembered) and to std-agent-trace (the run record). By default the tools are the program's own declarations: every `-> external` input (its @description is the tool text) and a read over every persisted entity, so composing building blocks composes the assistant's abilities. Any section's page gets the assistant with two traits, `XAssistant = AgentSession.traits.AgentConversation` and a std-panel-launcher dock: the conversation speaks the ASSISTANT_* contract from any orbital, so the assistant needs no per-section wiring. Import the orbital once per app: `orbital Assistant = Agent.orbitals.AgentAssistantOrbital { config { instructions: \"…\" } }`. The conversation, memory and run records live in AgentRecordsOrbital; retarget them onto your own owner-scoped entities (`ownerId` a relation to your [identity] roster, with @read/@create) with `entities { AgentMessage: …, AgentMemory: …, AgentRun: …, AgentChat: … }`. The conversation is kept across pages and reloads (each person's most recently used conversation is the current one);"
 
-type AgentTool = {
-  event : event
-  read : string
-  scope : "declared"
+type AgentToolScope = {
+  scope : "declared"!
 }
+type AgentToolInput = {
+  event : EventAddress!
+}
+type AgentToolRead = {
+  read : string!
+}
+type AgentTool = AgentToolScope | AgentToolInput | AgentToolRead
 type AgentLink = {
   label : string!
   href : string!

package/behaviors/lolo/ui/core/atoms/ui-svg-flow.lolo

@@ -43,7 +43,7 @@ orbital SvgFlowOrbital {
     }
 
     config {
-      points : [[number]] = []
+      points : [[number, number]] = []
         @label "Points"
         @description "points prop"
         @tier "presentation"

package/behaviors/lolo/ui/core/molecules/ui-import-progress.lolo

@@ -52,7 +52,7 @@ orbital ImportProgressOrbital {
         @label "Counts"
         @description "Unit counts"
         @tier "presentation"
-      labels : Map string string = { item: "Item" }
+      labels : Map string string = { fetching: "Item" }
         @label "Labels"
         @description "Step label overrides"
         @tier "presentation"

package/behaviors/lolo/ui/game/atoms/ui-canvas.lolo

@@ -32,12 +32,12 @@ orbital CanvasOrbital {
   type CanvasLightingAmbient = {
     intensity : number
     color : string
-    position : [number]
+    position : [number, number, number]
   }
   type CanvasLightingDirectional = {
     intensity : number
     color : string
-    position : [number]
+    position : [number, number, number]
   }
   type CanvasLightingHemisphere = {
     intensity : number
@@ -47,7 +47,7 @@ orbital CanvasOrbital {
   type CanvasLightingPointsItem = {
     intensity : number
     color : string
-    position : [number]!
+    position : [number, number, number]!
     distance : number
     decay : number
   }

package/behaviors/lolo/ui/game/atoms/ui-control-grid.lolo

@@ -132,15 +132,15 @@ orbital ControlGridOrbital {
         @label "Direction Event"
         @description "Event-bus event emitted with `{ direction, pressed }` (kind='dpad')"
         @tier "presentation"
-      directionEvents : Map string string = { item: "INIT" }
+      directionEvents : Map string string = { up: "INIT" }
         @label "Direction Events"
         @description "Per-direction PRESS → the board's SEMANTIC event (kind='dpad'), e.g. `{ left: 'LEFT', right: 'RIGHT', up: 'JUMP' }`. Lets the d-pad emit the SAME intent events as the keyboard so the FSM stays device-agnostic."
         @tier "presentation"
-      directionReleaseEvents : Map string string = { item: "INIT" }
+      directionReleaseEvents : Map string string = { up: "INIT" }
         @label "Direction Release Events"
         @description "Per-direction RELEASE → semantic event, e.g. `{ left: 'STOP', right: 'STOP' }`. Omit a direction to ignore its release."
         @tier "presentation"
-      directionAssets : Map string ControlGridDirectionAssetsValue = { item: { url: "https://almadar-kflow-assets.web.app/shared/ui-roguelike-board/default/features/sword.png", role: "item", category: "item", animations: ["static"], style: "pixel", dimension: "2d", aspect: "1:1", name: "item", thumbnailUrl: "" } }
+      directionAssets : Map string ControlGridDirectionAssetsValue = { up: { url: "https://almadar-kflow-assets.web.app/shared/ui-roguelike-board/default/features/sword.png", role: "item", category: "item", animations: ["static"], style: "pixel", dimension: "2d", aspect: "1:1", name: "item", thumbnailUrl: "" } }
         @label "Direction Assets"
         @description "Per-direction sprite assets for kind='dpad' buttons (e.g. Kenny arrow PNGs). Falls back to arrow emoji."
         @tier "presentation"

package/behaviors/lolo/ui/game/atoms/ui-draw-group.lolo

@@ -64,7 +64,7 @@ orbital DrawGroupOrbital {
         @label "Rotate"
         @description "Rotation in radians (painter units)."
         @tier "presentation"
-      rotation : [number] = []
+      rotation : [number, number, number]
         @label "Rotation"
         @description "Euler rotation `[x, y, z]` in radians (world axes) — per-axis joint rotation for the 3D backend; a group placed at a joint with children authored joint-local IS a bone. The 2D painter applies only the in-plane `z` component, after `rotate`."
         @tier "presentation"

package/behaviors/lolo/ui/game/atoms/ui-draw-mesh.lolo

@@ -144,7 +144,7 @@ orbital DrawMeshOrbital {
         @label "Skin"
         @description "`polyhedron` only: smooth-skinning weights binding the vertices to named bone groups. Vertices must then be authored in BIND POSE model space; the bones' animated transforms deform them."
         @tier "presentation"
-      rotation : [number] = []
+      rotation : [number, number, number]
         @label "Rotation"
         @description "Euler rotation `[x, y, z]` in radians."
         @tier "presentation"

package/behaviors/lolo/ui/game/atoms/ui-draw-skinned-mesh.lolo

@@ -23,7 +23,7 @@ orbital DrawSkinnedMeshOrbital {
   }
   type DrawSkinnedMeshMesh = {
     vertices : [DrawSkinnedMeshMeshVerticesItem]!
-    triangles : [[number]]!
+    triangles : [[number, number, number]]!
   }
   type DrawSkinnedMeshMeshVerticesItem = {
     x : number!
@@ -39,8 +39,8 @@ orbital DrawSkinnedMeshOrbital {
   type DrawSkinnedMeshBonesItem = {
     name : string!
     parent : string
-    pivot : [number]!
-    tip : [number]!
+    pivot : [number, number]!
+    tip : [number, number]!
   }
   type DrawSkinnedMeshClip = {
     frames : [Map string number]!

package/behaviors/lolo/ui/learning/atoms/ui-biology-canvas.lolo

@@ -32,12 +32,12 @@ orbital BiologyCanvasOrbital {
   type BiologyCanvasLightingAmbient = {
     intensity : number
     color : string
-    position : [number]
+    position : [number, number, number]
   }
   type BiologyCanvasLightingDirectional = {
     intensity : number
     color : string
-    position : [number]
+    position : [number, number, number]
   }
   type BiologyCanvasLightingHemisphere = {
     intensity : number
@@ -47,7 +47,7 @@ orbital BiologyCanvasOrbital {
   type BiologyCanvasLightingPointsItem = {
     intensity : number
     color : string
-    position : [number]!
+    position : [number, number, number]!
     distance : number
     decay : number
   }

package/behaviors/lolo/ui/learning/atoms/ui-chemistry-canvas.lolo

@@ -32,12 +32,12 @@ orbital ChemistryCanvasOrbital {
   type ChemistryCanvasLightingAmbient = {
     intensity : number
     color : string
-    position : [number]
+    position : [number, number, number]
   }
   type ChemistryCanvasLightingDirectional = {
     intensity : number
     color : string
-    position : [number]
+    position : [number, number, number]
   }
   type ChemistryCanvasLightingHemisphere = {
     intensity : number
@@ -47,7 +47,7 @@ orbital ChemistryCanvasOrbital {
   type ChemistryCanvasLightingPointsItem = {
     intensity : number
     color : string
-    position : [number]!
+    position : [number, number, number]!
     distance : number
     decay : number
   }

package/behaviors/lolo/ui/learning/atoms/ui-physics-canvas.lolo

@@ -32,12 +32,12 @@ orbital PhysicsCanvasOrbital {
   type PhysicsCanvasLightingAmbient = {
     intensity : number
     color : string
-    position : [number]
+    position : [number, number, number]
   }
   type PhysicsCanvasLightingDirectional = {
     intensity : number
     color : string
-    position : [number]
+    position : [number, number, number]
   }
   type PhysicsCanvasLightingHemisphere = {
     intensity : number
@@ -47,7 +47,7 @@ orbital PhysicsCanvasOrbital {
   type PhysicsCanvasLightingPointsItem = {
     intensity : number
     color : string
-    position : [number]!
+    position : [number, number, number]!
     distance : number
     decay : number
   }