Skip to content

Fix migration activity persistence after reverting a customization - #336828

Open
Hawk Ticehurst (hawkticehurst) wants to merge 2 commits into
mainfrom
agents/customization-migration-revert-fix
Open

Hawk Ticehurst (hawkticehurst) wants to merge 2 commits into
mainfrom
agents/customization-migration-revert-fix

Conversation

@hawkticehurst

Copy link
Copy Markdown
Member

Fixes #336731

This pull request addresses the issue where customization migration activity remains after a migration is reverted, as outlined in issue #336731. The changes ensure that stale migration activity is properly reconciled when migration candidates are refreshed.

Changes

  • Reconciles stored migration activity whenever migration candidates refresh, removing stale activity if a reverted source becomes migratable again.
  • Introduces stable URI-based migration keys for new file and MCP activity, while maintaining a legacy label/path fallback for existing stored activity.
  • Preserves copied-file activity, ensuring the original source remains intact.

Validation

  • All tests for the customization management editor pass.
  • Regression tests for current and legacy migration activity are successful.
  • ESLint checks and git diff --check pass without issues.
  • Full client type-check was blocked due to unrelated missing declarations, but transpilation completed successfully.

Copilot AI balanced review requested due to automatic review settings September 18, 2026 20:06
@hawkticehurst
Hawk Ticehurst (hawkticehurst) marked this pull request as ready for review September 18, 2026 20:08

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

The copied-file preservation branch needs regression coverage.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1 Low severity

Open (1)
What changed in this PR

Reconciles persisted customization migration activity after reverted migrations.

Changes:

  • Adds stable migration keys for files and MCP servers.
  • Removes stale current and legacy activity while preserving copied-file records.
  • Adds regression coverage for activity reconciliation.
File Description
aiCustomizationManagementEditor.ts Reconciles and keys migration activity.
customizationMigrationDashboard.ts Adds optional migration keys.
aiCustomizationManagementEditor.test.ts Tests current and legacy activity removal.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Cover the reconciliation exception that keeps copy migration activity when its source remains a migration candidate.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

github-actions Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Base: 6b0c54ee Current: 8de98620

No screenshot changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Chat customization: Migration notice sticks around after reverting change

3 participants