- 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.
XFlowViewMaker is the adapter layer between XFlowSDK and consuming app/framework integration. It is under evaluation for reduction or removal.
Durable Context
Historical release work often required bumping XFlowViewMaker alongside XFlowSDK before consumer validation was possible.
XFlowViewMaker was a recurring source of coupling between XFlow changes and Fid4 or flagship rollout.
Historical Slack evidence shows that version bumps through XFlowViewMaker were often blocked by external pipeline or dependency issues rather than pure feature regressions.
Integration Implications
When a fix exists in XFlowSDK but is not visible in consumer validation, check whether XFlowViewMaker or downstream pinned versions are blocking adoption.
If the issue involves version propagation into Fid4, treat XFlowViewMaker as part of the release path unless direct-consumption work has replaced it.
Questions about removing or collapsing the layer should be evaluated against current consumer integration patterns, not just local SDK behavior.
Historical Signals From Slack
XFlowViewMaker version bumps into flagship frequently surfaced PreviewMacros.SwiftUI, Apex, or pipeline compatibility issues.
Historical context shows growing pressure to reduce XFlowViewMaker-specific indirection and move toward simpler consumer paths.
Slack history also shows that tutorials and release steps around XFlowViewMaker were easy to misunderstand, which made version propagation a repeated risk.
david.delagneau
374991a568