A team notices that Copilot repeatedly applies legacy billing migration guidance to unrelated mobile analytics tasks. They want to remove stale persistent context, keep valid billing conventions available only for billing files, and create a focused context area for the current analytics migration. Which four actions should you perform in order? 1. Create an analytics migration Copilot Space 2. Delete misleading repository memory facts 3. Move all billing notes into repository-wide instructions 4. Review stored Copilot Memory facts 5. Add billing conventions to path-specific instructions 6. Exclude the entire billing package from Copilot

The correct sequence addresses the problem systematically. First, Review stored Copilot Memory facts (4) is crucial to understand what persistent context is causing the issue. Then, Delete misleading repository memory facts (2) directly removes the stale, incorrect information that Copilot is repeatedly applying. Next, Add billing conventions to path-specific instructions (5) ensures that valid billing guidance is available only when relevant, preventing its application to unrelated tasks. Finally, Create an analytics migration Copilot Space (1) provides a focused, clean environment for the new analytics work, free from interference from other contexts. Option 1 is incorrect because deleting facts before reviewing them could remove useful information. Option 3 is incorrect because moving all billing notes to repository-wide instructions would reintroduce the problem of broad application. Option 4 is incorrect because excluding the entire billing package might remove necessary context for actual billing tasks.