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

.opencode/commands/slack-import.md

@@ -50,6 +50,16 @@ Instructions:
   - durable role/person associations
   - recurring architecture or debugging patterns
   - past approvals or decisions that still matter
+- create or update person files when the archive shows a human repeatedly contributing across channels, years, or high-signal technical/process discussions
+- store people conservatively:
+  - exact role only when explicitly supported by the archive
+  - otherwise store collaboration pattern, communication style, and project relationship
+- actively look for:
+  - Jira IDs plus explicit titles, sizing, and scope changes
+  - repeated architecture themes around XFlow, SwiftUI, REST, GraphQL, auth, and entry-point behavior
+  - ownership or responsibility boundaries between framework and consuming app teams
+  - recurring pipeline or dependency failures that shaped project work
+  - named people who repeatedly drive approvals, technical framing, or debugging direction
 - prioritize high-signal messages such as Jira references, approvals, scope changes, root-cause notes, points, and persistent technical constraints
 - favor messages that help reconstruct project history across multiple years, not just the newest ones
 - avoid promoting outdated daily status unless it changes current understanding