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

.opencode/commands/standup.md

@@ -37,6 +37,9 @@ Before drafting:
 - update workspace memory if the refreshed context introduced clear high-confidence project facts
 - prefer existing memory when the latest context is ambiguous
 - mention Jira IDs and approved titles when they map cleanly to yesterday's work
+- prioritize story-based updates over side questions, memory refreshes, or manager-only context
+- if documentation or root cause updates directly support a story, roll them into that story's update instead of listing them separately
+- exclude items that are not directly tied to a story unless they are true blockers
 
 Return a standup that is:
 
@@ -44,4 +47,9 @@ Return a standup that is:
 - concise
 - grounded in the latest context
 - safe to send without overstating certainty
-- written in natural US English that Jeff could forward without rewriting
+- written in natural US English that can be sent externally without rewriting
+- written as David's progress report
+- free of any mention of Jeff by name
+- free of any mention of Mattermost, since it is internal-only communication
+- uses bullet points for each item
+- uses `JIRA-ID - Title` or `JIRA-ID Title` formatting instead of comma-separated ID/title formatting

ai/logs/2026-04-09.md

@@ -9,6 +9,7 @@
 - Created `PDIAP-15836` for dismissal delegate lifecycle sequencing in pure SwiftUI (`8` points)
 - Aligned `PDIAP-15838` scope with REST migration cleanup and feature-flag removal
 - Confirmed XFlowViewMaker `0.5.0` is already in Fid4
+- Updated the root cause document for the AccountLink dismissal sequencing issue tied to `PDIAP-15836` and got approval on the proposed wording
 
 ---
 
@@ -26,6 +27,7 @@
 
 - Prepared clearer wording for Jeff
 - Focused on context, observation, and action instead of vague comparison language
+- Proposed a root cause document update and got confirmation on the revised wording
 
 ---
 

ai/logs/2026-04-10.md

@@ -0,0 +1,12 @@
+# 2026-04-10
+
+## Clarification
+
+- `PDIAP-15838` should not be framed as directly tied to the UIKit-removal spike.
+- Avoid wording that implies `PDIAP-15838` is dependent on or part of the dismissal-sequencing / UIKit-removal spike.
+- Standups should prioritize updates directly tied to active work items and omit side questions such as version reminders that were only for internal context.
+- Current focus for today is to finalize `PDIAP-14859` with a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically while preserving both flows appropriately.
+- Omit standup items that are not directly related to a story.
+- Use the approved title `Remove Apollo for iOS` for `PDIAP-15838`.
+- When a documentation or root cause update directly supports a story, report it under that story instead of as a separate standup item.
+- In standups, format Jira references as `ID - Title` or `ID Title`, not `ID, Title`.

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
 
 ---
 

ai/state/work-items.md

@@ -7,10 +7,10 @@ Update it only with explicit, project-relevant information that is useful for fu
 ## Current
 
 - `PDIAP-15765` - AO DOB field error not showing investigation
-  Current note: issue was moved back to In Progress temporarily and should move to Done after the new sprint starts.
+  Current note: root cause was documented; the DOB validation issue was confirmed on TeenIdentityCheck for authenticated users, and Jeff approved moving the story to Done once the new sprint starts.
 
 - `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
-  Current note: story created, sized at 8 points, aligned with epic `26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2)`, and meant to cover SwiftUI dismissal sequencing validation.
+  Current note: story came out of the AccountLink root cause investigation and related root cause document update; it was sized at 8 points, aligned with epic `26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2)`, and is meant to cover SwiftUI dismissal sequencing validation.
 
-- `PDIAP-15838` - REST deprecation / remove GraphQL networking layer
+- `PDIAP-15838` - Remove Apollo for iOS
-  Current note: approved at 8 points to remove Apollo, GraphQL-specific networking code, related tests and mocks, and transport feature flags so REST remains.
+  Current note: approved at 8 points; description and ACs were filled in and Jeff approved the scope to remove Apollo, GraphQL-specific networking code, related tests and mocks, and transport feature flags so REST remains.

prompts/standup.md

@@ -11,11 +11,20 @@ Requirements:
 - Mention debugging findings only if they materially changed understanding
 - Clarify auth-dependent behavior when relevant
 - Mention Jira IDs and approved titles when they are available and clearly tied to the reported work
+- Prefer including story titles whenever a reported update maps clearly to a Jira item
 - Prefer story-based reporting when the work maps clearly to a Jira item
+- Prefer updates directly tied to active work items over side questions, context refreshes, or manager-only reminders
+- If documentation or root cause updates directly support a story, group that work under the related story instead of reporting it as a separate unrelated item
 - Avoid vague phrases and generic progress language
 - Separate the main issue from unrelated follow-up work unless both are explicitly relevant today
+- Omit standup items that are not directly related to a story unless they are a real blocker
 - Prefer evidence-backed statements over assumptions
-- Write in natural US English that Jeff can forward without rewriting
+- Write in natural US English that can be forwarded externally without rewriting
+- Write the standup as David's external progress report
+- Do not mention Jeff by name
+- Do not mention Mattermost because it is internal-only communication
+- Use bullet points for each item
+- When pairing a Jira ID with a title, prefer `ID - Title` or `ID Title`; do not use commas between them
 - Keep it concise and ready to send
 
 Format: