feat: Update standup and work item documentation for clarity and story prioritization

ai/state/current.md

@@ -7,6 +7,7 @@
 - Debug Discourse and AO issues
 - Prepare better updates for the current manager or stakeholder through Mattermost
 - Follow up on `PDIAP-15765`, `PDIAP-15836`, and `PDIAP-15838`
+- Finalize `PDIAP-14859` with a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically while preserving both flows appropriately
 
 ---
 
@@ -25,8 +26,17 @@
 ## Communication Priorities
 
 - Standups should reflect the latest technical state, not generic progress
+- Standups should prefer updates directly tied to active work items over one-off memory refreshes or side questions
+- Standups should include story titles whenever a reported update maps to a Jira item
+- Standups should use bullet points for each item, but avoid dash-separated title formatting inside the sentence body
+- When pairing a Jira ID with a title in standups, prefer a simple hyphen after the ID or omit punctuation instead of using commas
+- Standups should omit side questions or manager-only context refreshes unless they materially changed story work
+- If a root cause document or other documentation update directly supports a story, it should be reported under that story instead of as a separate standalone item
+- Standups should omit items not tied to a story unless they are real blockers
 - Manager updates should be short, precise, and natural in English
 - Mattermost messages should make scope and next action explicit
+- Standups should be written as David's external progress report and should not mention Jeff by name
+- Standups should never mention Mattermost because it is internal-only communication
 
 ---