- 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.
Debug backend-driven flows without losing track of dynamic dependencies or misclassifying integration behavior.
Stable Patterns
XFlow screens are backend-driven, so UI can change without local code changes.
Reproduction depends on:
entry point
authentication state
backend configuration
consumer integration path
Not all entry points are reachable from visible UI; some require exploratory validation.
Investigation Rules
Confirm the entry point before comparing behavior.
Separate service-driven behavior from client regressions.
Confirm whether the issue reproduces in:
sample app
XFlow-only environment
Fid4 / flagship
authenticated vs non-authenticated state
If a fix appears correct in the SDK but not in consumer validation, inspect the release chain before reopening root cause assumptions.
When validating service/configuration changes, check the active flow-definition version in Cogstore before assuming a change is live in QA or Production.
Do not assume a flow ID will exist in both Cogstore and Slate; verify which config system actually owns the flow you are inspecting.
david.delagneau
374991a568