feat: Refactor work item management and documentation for clarity and structure

knowledge/agent-memory-rules.md

@@ -80,16 +80,18 @@ Use when the fact changes the active work window, including:
 - current blockers or debugging constraints
 - manager direction that changes the next few days of work
 
-### `ai/state/work-items.md`
+### `ai/work-items/*.md` and `ai/state/work-items.md`
 
-Use for current Jira-linked work that should remain easy to reference across sessions, especially:
+Use `ai/work-items/*.md` as the canonical memory for current Jira-linked work that should remain easy to reference across sessions, especially:
 
 - Jira IDs
 - approved or explicit titles
 - currently relevant status notes
 - current points or scope notes
 
-This file should help standups and manager updates mention work items precisely.
+Use `ai/state/work-items.md` as the summary view of what is active now.
+
+These files should help standups and manager updates mention work items precisely.
 
 ### `ai/context/project.md`
 

knowledge/memory-promotion-rules.md

@@ -41,9 +41,9 @@ Use current state only for facts that materially affect active work over the nex
 
 Do not copy every daily update into current state.
 
-### Promote to `ai/state/work-items.md`
+### Promote to `ai/work-items/*.md` and `ai/state/work-items.md`
 
-Use this file for:
+Use `ai/work-items/*.md` for:
 
 - explicit Jira IDs
 - approved or explicit story titles
@@ -53,6 +53,8 @@ Use this file for:
 
 If a Jira item is likely to appear again in standups or manager updates, it belongs here.
 
+Use `ai/state/work-items.md` as the compact summary of which ticket files are active.
+
 ### Promote to `ai/context/project.md`
 
 Use project context only for durable project knowledge that should survive beyond the current work window, such as: