feat: Update behavior rules and documentation for workspace maintenance and flow references

ai/context/index.md

@@ -38,6 +38,7 @@ Durable context about recurring streams of work and investigation:
 - [workstreams/xflow-debugging.md](./workstreams/xflow-debugging.md)
 - [workstreams/xflow-swiftui-migration.md](./workstreams/xflow-swiftui-migration.md)
 - [workstreams/consumer-integration.md](./workstreams/consumer-integration.md)
+- [workstreams/flow-page-references.md](./workstreams/flow-page-references.md)
 
 ### `process/`
 

ai/context/process/communication.md

@@ -24,6 +24,8 @@ When the format fits, prefer:
 - For standups, report the previous workday context, not blindly the prior calendar day.
 - On Mondays, use Friday's work context unless a later prior day has Mattermost activity.
 - If the previous calendar day has no project activity because of weekend, holiday, or OOO, use the latest prior day with Mattermost activity.
+- For standups, when a Jira item has multiple concrete updates, use one top-level `JIRA-ID - Title` bullet and indented markdown sub-bullets instead of repeating the same Jira line.
+- When a flow/page shorthand could be ambiguous, prefer the real flow identifier and page name from `ai/context/workstreams/flow-page-references.md`.
 - Avoid vague phrasing such as:
   - "same behavior"
   - "looks fixed"

ai/context/process/context-maintenance.md

@@ -17,6 +17,7 @@ Keep this workspace useful as living memory instead of a pile of disconnected no
   - `ai/state/work-items.md` for the compact active-work summary
   - `ai/context/` for durable project knowledge
   - `ai/context/people/` for named person context
+  - `.opencode/commands/`, `prompts/`, `.opencode/agents/`, `.opencode/skills/`, or `knowledge/` for reusable behavior rules that control how the workspace responds
 
 ---
 
@@ -26,9 +27,11 @@ Keep this workspace useful as living memory instead of a pile of disconnected no
 - Do not promote failed syncs or tooling errors as project facts.
 - Promote repeated durable patterns from historical archives into stable context when confidence is high.
 - Keep old status-only details archive-only unless they still change current understanding.
+- Treat user corrections about command output, prompt structure, memory handling, or agent behavior as inputs to the operational surface, not just as daily notes.
 
 ---
 
 ## Curation Rule
 
 - If a new stable context file is added, keep `project.md` and `index.md` aligned so future sessions can discover it quickly.
+- If a new rule affects a slash command or reusable prompt, update that command or prompt directly so the behavior changes on the next run.

ai/context/workstreams/flow-page-references.md

@@ -0,0 +1,25 @@
+# Flow And Page References
+
+## Goal
+
+Keep recurring flow names, page names, and shorthand references aligned so debugging notes and external updates do not drift into ambiguous wording.
+
+---
+
+## Current Mappings
+
+- `HybridYouthAccountOpening`
+  - This is the real flow identifier when David refers to the Youth flow in recent AO validation discussions.
+  - The relevant page in this flow is `TeenIdentityCheck`.
+
+- `HybridBrokerageAccountOpening`
+  - This is the separate authenticated flow discussed alongside the Youth issue.
+  - The relevant page in this flow is `JointIdentityCheck`.
+
+---
+
+## Usage
+
+- When drafting updates, prefer the real flow identifier if there is any risk that shorthand like `Youth flow` or `HybridBrokerage` could be misunderstood.
+- When a shorthand is still useful for readability, keep the real flow ID available somewhere in the same session context.
+- Capture additional stable flow/page mappings here when they come up repeatedly in debugging, standups, Jira comments, or consumer communication.

ai/context/workstreams/index.md

@@ -17,6 +17,9 @@
 - [consumer-integration.md](./consumer-integration.md)
   Release and validation coupling across XFlow, XFlowViewMaker, FT modules, and Fid4.
 
+- [flow-page-references.md](./flow-page-references.md)
+  Stable mapping between shorthand flow references and their real flow/page identifiers.
+
 ---
 
 ## Guidance