david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Update work item statuses and refine sprint planning for PDIAP-15838; adjust standup prompt guidelines

Browse Source
This commit is contained in:
David Delagneau
2026-04-21 07:33:53 -06:00
parent 4d8948672b
commit 688b4d462a
5 changed files with 20 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
project-knowledge/01-current/current-work.md
View File

@@ -17,8 +17,8 @@ tags:
- Prepare better updates for the current manager or stakeholder through Mattermost
- Follow up on active tickets through `project-knowledge/02-work-items/`, especially `PDIAP-15838` and `PDIAP-15836`
- `PDIAP-15765` is done and `PDIAP-14859` is also done
- `PDIAP-15838` is now in progress
- The current top priority is back to `PDIAP-15838` implementation work for removing GraphQL and related LaunchDarkly toggles
- `PDIAP-15838` is assigned to the next sprint
- Do not describe `PDIAP-15838` as current-sprint in-progress implementation work
- `PDIAP-15836` comes after the current REST-investigation / Apollo-removal work
- Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of `PDIAP-15765` scope unless later evidence proves it belongs there
- Include feature-flag planning for the broader UIKit-removal spike, including dismissal sequencing changes that affect consumers
@@ -64,7 +64,7 @@ tags:
- Adam reported the earlier REST activation problem, and he or his team validate behavior on real devices rather than simulator-only paths
- Avoid treating GitHub Copilot or LaunchDarkly as story-specific tools; both are broader Fidelity workflow tools that happened to matter in this investigation
- Defining a consumer rollout plan for UIKit-removal sequencing changes, including validation, communication, and feature-flag retirement
- Continue broader Apollo-removal / REST-migration cleanup now that the latest build is reportedly activating REST again
- Keep the Apollo-removal / REST-migration context ready for the next sprint, when `PDIAP-15838` becomes active
- Avoiding assumptions when comparing iOS and Android validation behavior; scenario-specific parity needs to be confirmed before reporting scope
- Avoiding assumptions about legacy Apex/ApexKit paths; breakpoint evidence and helper usage both need to be reconciled before reporting ownership or replacement guidance
- When ownership is still uncertain under production pressure, prefer rollback-plus-investigation framing over confident blame assignment to consumers