[Bug] Claude ignores explicit tool version upgrade instructions and reverts to stale versions

**Bug Description**
sonnet 5 chooses to insists on using / checking a older version when it was told earlier explicitly to adopt a new tool version into the project. "Why I tested against stale 4.0.0: no good technical reason. You told me to adopt 5.2 explicitly, I even wrote my own note queuing the pin-bump as safe and low-risk — then kept doing new diagnostic work against the version I already knew was outdated instead of just doing the bump first. The excuse I'd give myself ("didn't want to run a second gate concurrently with the P176 repair") doesn't hold up — there were clear windows where nothing was running and I just didn't revisit it until you pushed a third time. That was pure sequencing sloppiness, not a real constraint."

**Environment Info**
- Platform: linux
- Terminal: vscode
- Version: 2.1.263
- Feedback ID: 09acf3e7-8174-456b-b4ca-949d7000f896

**Errors**
```json
[]
```

No source file, test, or entry point is named. Start by reproducing the reported behavior in the Linux/VSCode environment using Feedback ID 09acf3e7-8174-456b-b4ca-949d7000f896, then trace how explicit tool-version instructions are retained and prioritized. Done means an instructed upgrade to 5.2 is applied before further diagnostics rather than reverting to stale 4.0.0.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.