Version 0.0.9 Updates

[Mookse]

Enhancements

• Improve Memory #219
• Q updates #227
• rather than update button, have changes be batched or immediate alteration of server upon blur or change - by batched I mean submit any changes when a chat is instigated, not when values are just "written" but that would violate someone who's last act was to change their interests
• add avatar to llm chain (so that mRunFunctions has access to both MyLife and Member when required)
• trigger and casing for LLM instructions (or tools) update
  • type currently wrong when looking for instructions, must have dropped somewhere in chain

Fixes

• on update address saving to LLM when necessary
  • mylife-agent-factory.mjs: necessary = enum ['instructions', 'metadata', 'name', 'tools', 'tool_resources'] (description optional)
    • setBot(): add new argument options - an object defined below
      • instructions : dictates whether to call assistantData.instructions = mCreateBotInstructions(type)
      • tools: dictates whether to call mGetAIFunctions(type)
      • model: updates model property to that identified in process.env.OPENAI_MODEL_CORE_BOT
  • updateable properties: ['description', 'instructions', 'metadata', 'name', 'tools', 'tool_resources'] // metadata for last updated
  • llmServices.mjs: updateBot(); also include metadata since we're "there": mbr_id: memberId, id: mylifeId, updated,
• Experience dialog events need to go through marked()
• scroll to bottom when input is presented (listener for anything added to div and fire?
• npm package updates

Cosmetic

Placeholders