feat: Enhance Slack import and memory promotion rules to better capture multi-channel, multi-year contributions and improve user role identification

knowledge/agent-memory-rules.md

@@ -42,6 +42,7 @@ Examples:
 - confirmed version, dependency, or rollout facts tied to current work
 - corrections to previously stored project context
 - repeated named people with stable roles or communication relevance
+- repeated named people with multi-channel, multi-year, or high-signal technical/process involvement even when the exact formal role is still unknown
 
 ---
 
@@ -106,6 +107,12 @@ Use these files for:
 - keeping named stakeholders recognizable across sessions
 - storing stable communication or responsibility context per person
 
+When the role is not explicit, store:
+
+- where the person tends to appear
+- what kinds of topics they influence
+- how they affect approvals, scope, debugging, or communication
+
 ### `ai/context/decisions/*.md`
 
 Use for explicit confirmed decisions with ongoing impact.

knowledge/memory-promotion-rules.md

@@ -75,6 +75,8 @@ Use these files when:
 - a person's identity matters repeatedly
 - a role becomes associated with a specific person
 - a stakeholder's communication or approval patterns affect future work
+- a human appears across multiple channels or years with repeated technical, process, or approval signal
+- the archive makes the collaboration pattern clear even if the formal title is still unknown
 
 Prefer:
 
@@ -82,6 +84,8 @@ Prefer:
 - `index.md` for active roster
 - one file per person for person-specific context
 
+If exact role confidence is low, store the person's repeated project relationship instead of inventing a title.
+
 ---
 
 ## Do Not Promote