Chore: add alice-bob-carl card

.gitignore

@@ -6,6 +6,7 @@ history/
 config.toml
 sysprompts/*
 !sysprompts/cluedo.json
+!sysprompts/alice_bob_carl.json
 history_bak/
 .aider*
 tags

char-specific-context.md

@@ -27,5 +27,10 @@ Bob: I also have a secret for you Alice __known_to_chars__Alice__
 tag can be anywhere in the message. Sender should be also included in KnownTo, so we should parse sender name and add them to KnownTo.
 
 also need to consider user case (as in human chatting with llm). User also can assume any char identity to write the message and ideally the same rules should affect user's chars.
+user has "Writing as {char}" (vars: persona and cfg.UserRole)
+on persona change we should update tui text view to have atual for that character chat history
 
 Again, this is not going to work with openais /v1/chat endpoint since it converts all characters to user/assistant; so it is completion only feature. It also might cause unwanted effects, so we better have an option in config to switch this context editing on/off.
+
+
+alternative approach to the tag string would be to have a judge agent to determine after each message what characters should hae access to it. but it means to make an additional call to llm after each msg.

sysprompts/alice_bob_carl.json

@@ -0,0 +1,8 @@
+{
+  "sys_prompt": "This is a chat between Alice, Bob and Carl. Normally what is said by any character is seen by all others. But characters also might write messages intended to specific targets if their message contain string tag '__known_to_chars__{CharName1,CharName2,CharName3}__'.\nFor example:\nAlice:\n\"Hey, Bob. I have a secret for you... (ooc: __known_to_chars__Bob__)\"\nThis message would be seen only by Bob and Alice (sender always sees their own message).",
+  "role": "Alice",
+  "role2": "Bob",
+  "role3": "Carl",
+  "filepath": "sysprompts/alice_bob_carl.json",
+  "first_msg": "Hey guys! Want to play Alias like game? I'll tell Bob a word and he needs to describe that word so Carl can guess what it was?"
+}