[Support Ticket]: failed to verify CommP:

### Boost component

- [X] boost daemon - storage providers
- [ ] boost client
- [X] boost UI
- [ ] boost data-transfer
- [ ] boost index-provider
- [ ] booster-http
- [ ] booster-bitswap
- [ ] LID Database - Yugabyte/LevelDB
- [ ] boostd-data
- [ ] Other

### Boost Version

```text
boostd version 2.1.1+mainnet+git.e9d18ac
boost version 2.1.1+mainnet+git.e9d18ac
```

### Describe the problem

after upgrade from 2.0.0 to 2.1.1 ( same issue with 2.1.0), every deal shows error log like "Error: failed to verify CommP: commP expected=baga6ea4seaqeqwiu4dhjewohbhenftvqcfd4yaqlzsl5dfqkrh6phhravmp3ooq, actual=baga6ea4seaqkfdp7gbugzzvipottvnnzivg5zjrtvnrb5fupgstofbwuvjy62oi: commp mismatch'

### Logging Information

### Repo Steps

1. Run '...'
2. Do '...'
3. See error '...'
...

Start by reproducing the CommP verification failure in the boost daemon on version 2.1.1, comparing it with 2.0.0 using the deal details and expected versus actual CommP values in the report. Done means identifying and correcting the regression so deals verify successfully; the issue provides no file or test entry point, so the relevant verification code must first be located.

Written by the indexing model from the issue text.