-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Labels
effort-smallSmall effort: <2 hoursSmall effort: <2 hoursenhancementNew feature or requestNew feature or requestimpact-lowLow impact on users or systemLow impact on users or systemuser-experienceUser experience improvementsUser experience improvementsworkflowWorkflow state and validation featuresWorkflow state and validation features
Description
Description
When workflow-state.json is loaded in any command and auto-migration occurs (e.g., from legacy format to v1.0), notify the user once with a friendly message.
Current Behavior
Migration happens silently in the background via applyMigrations() call in WorkflowStateManager.loadWorkflowState(). Users have no visibility that their workflow state file was upgraded.
Proposed Behavior
Add a notification when auto-migration occurs:
Notice: Migrated workflow-state.json from legacy format to v1.0
(This migration happens automatically. No action required.)
Analyzing ./src...
Implementation Approach
- Add a flag to WorkflowStateManager to track if migration occurred
- Return migration status from
loadWorkflowState()(e.g.,{ state, migrated: boolean, from?: string, to?: string }) - Display one-time notification in commands when migration detected
- Migration info includes: source version, target version, timestamp
Benefits
- Users see transparency about schema upgrades
- No need to understand manual migration commands
- Builds trust in automated processes
Files to Modify
cli/src/utils/workflow-state-manager.ts- Return migration metadataanalyzer/src/utils/workflow_state_manager.py- Python equivalent- All command files that call
loadWorkflowState()- Check and display notification
Related Issues
- Implement workflow state schema migration utilities #375 - Schema migration utilities (parent feature)
- Add
docimp statuscommand to visualize workflow state #374 -docimp statuscommand implementation
Estimated Effort
2-3 hours
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
effort-smallSmall effort: <2 hoursSmall effort: <2 hoursenhancementNew feature or requestNew feature or requestimpact-lowLow impact on users or systemLow impact on users or systemuser-experienceUser experience improvementsUser experience improvementsworkflowWorkflow state and validation featuresWorkflow state and validation features