david.delagneau
374991a568
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md - Updated opencode.json to remove references to deleted files. - Revised profile.md to clarify the status of legacy paths and communication evidence. - Adjusted prompts to reflect new file paths and improve clarity. - Enhanced daily logs with focus, work-items, and blockers properties. - Updated work-item notes to include systems, workstreams, people, and related properties. - Improved context maintenance guidelines to ensure accurate and durable project knowledge. - Refined base filters to exclude template files and ensure only relevant notes are displayed. - Updated daily templates to ensure proper formatting and consistency. - Modified workflows to align with the new vault structure and improve context synchronization.
49 lines
1.4 KiB
Markdown
49 lines
1.4 KiB
Markdown
---
|
|
type: workstream
|
|
project: fidelity
|
|
status: active
|
|
systems: [xflowsdk, xflowviewmaker, ftframeworks, fid4]
|
|
work-items: [pdiap-14859, pdiap-15836]
|
|
related: [xflow-swiftui-migration, xflow-debugging]
|
|
updated: 2026-04-16
|
|
tags:
|
|
- workstream
|
|
- fidelity
|
|
---
|
|
# Consumer Integration And Release
|
|
|
|
## Goal
|
|
|
|
Capture the durable release and validation path between XFlow changes and real consumer behavior.
|
|
|
|
---
|
|
|
|
## Stable Patterns
|
|
|
|
- End-to-end validation often requires more than an SDK change.
|
|
- Historical Slack evidence shows repeated coupling across:
|
|
- XFlowSDK
|
|
- XFlowViewMaker
|
|
- FTFrameworks modules
|
|
- Fid4 / flagship
|
|
- Version pins, publishing delays, and consumer build issues can block validation even when the original code change is ready.
|
|
|
|
---
|
|
|
|
## Investigation Rules
|
|
|
|
- Before concluding a fix is absent in Fid4, check whether the right version actually propagated downstream.
|
|
- Separate these failure modes:
|
|
- SDK bug
|
|
- adapter/version propagation issue
|
|
- FT module publish/test issue
|
|
- consumer app setup or pipeline issue
|
|
- Consumer validation constraints should shape story scope and estimates because they can dominate the real effort.
|
|
|
|
---
|
|
|
|
## Historical Signals From Slack
|
|
|
|
- Version bump work repeatedly involved XFlowViewMaker, FTAccountOpen, and FTTransfer.
|
|
- Some rollout problems involved Jenkins, Apex/ApexKit, preview macro compatibility, or secret/token access rather than the product behavior under investigation.
|