A team is reviewing signals that can cause an agent to continue work from outdated assumptions. The agent uses GitHub Issues, pull requests, workflow artifacts, dependency caches, and repository custom instructions. Match each item to the correct mitigation. Which mapping is correct?

The correct mapping addresses how an agent can become outdated. 1. The issue scope changed after the agent branch was created is mitigated by re-reading the current issue and PR timeline (B). This ensures the agent has the most up-to-date understanding of the task and any changes made since its initial branch creation. 2. The workflow stores agent-context-latest across multiple runs is mitigated by using run- or SHA-specific artifact names (D). This prevents an agent from loading stale context from a previous, potentially irrelevant, run, ensuring it always starts with fresh or run-specific information. 3. The cache key omits the dependency lockfile hash is mitigated by including dependency hashes in cache keys (A). This ensures the cache is invalidated and rebuilt when dependencies change, preventing the agent from using outdated or incompatible libraries. 4. Repository instructions reference a deprecated ADR file is mitigated by updating persistent instructions to current sources (F). This ensures the agent's foundational guidance is always based on the most current and relevant architectural decisions. Incorrect options like increasing workflow timeouts (C), granting contents write to validation jobs (E), or other mismatched pairings do not directly address the specific causes of outdated assumptions.