Jarvis Knowledge Base Learning from Tickets

We need to make sure that Jarvis is also learning something from the knowledge base. For example, here is the case: - Problem: User complains that he can see the project in his GitHub org, but when he is lookup it up when adding a repo, it does not show up - Solution: Org's admin only allowed certain repositories to be accessible to Jaah's GitHub App the the one user wants to add is not among them Based on that Jarvis would be able to suggest it as a likely cause. Let's setup a way to process that and accumulate this knowledge. It is kind of like Project Memory as well, even though it is a very different channel

Jarvis learns from solved tickets: an operator's solve gets an LLM-drafted lesson, approved/edited/dismissed on the ticket, served to tenants' Jarvis via search_docs as a likely cause (never public). PR #6470 merged; Jaah Deploy success; quick gate green; follow-up draft #8505. Memory: none applied.