feat: Refactor communication context to generalize from Jeff to current manager and enhance people management structure

AGENTS.md

@@ -7,7 +7,7 @@ OpenCode should treat this project as a persistent context layer used to:
 - keep current project state accurate
 - capture durable information from daily work
 - draft standups and Mattermost messages
-- improve communication for Jeff in natural US English
+- improve communication for the current manager or stakeholder in natural professional English
 
 ## Always-Loaded Context
 
@@ -15,7 +15,8 @@ The detailed operating rules live in:
 
 - `ai/AGENTS.md`
 - `ai/context/project.md`
-- `ai/context/people/jeff.md`
+- `ai/context/people/manager.md`
+- `ai/context/people/index.md`
 - `ai/state/current.md`
 - `ai/state/work-items.md`
 - `knowledge/workspace-model.md`
@@ -36,6 +37,8 @@ These are also loaded through `opencode.json`.
 - Promote to `ai/state/current.md` only when the fact materially changes active work over the next few days.
 - Keep explicit Jira IDs and approved titles in `ai/state/work-items.md` when they are useful for future standups or manager updates.
 - Promote to `ai/context/project.md` only when the fact changes durable project understanding.
+- When a repeatedly mentioned person becomes relevant to project flow, create or update a file under `ai/context/people/`.
+- Keep role-to-person mapping explicit in `ai/context/people/manager.md` and the roster in `ai/context/people/index.md`.
 - Never promote tooling chatter, sync status, or generic conversation noise.
 - Direct user prompts are also memory sources. Do not limit memory updates to explicit sync commands.
 - If a new prompt corrects prior understanding, update the canonical file directly instead of keeping both versions alive.