Question about skip-review behavior when only rule IDs change in DNR rulesets

Hi all,  

I’d like to clarify a case regarding declarativeNetRequest (DNR) rulesets and the skip-review mechanism.  

In our testing, we observed that when only the IDs of static rules change between versions (but the rules themselves remain identical), the Chrome Web Store review process still flagged the extension for review.  

Example:  
In version v5.1.83, a rule had this ID:

{
  "id": 3987098,
  "action": { "type": "redirect", "redirect": { "extensionPath": "/web-accessible-resources/redirects/nooptext.js" } },
  "condition": { "urlFilter": "||go.oclasrv.com/apu.php?" },
  "priority": 1001001
}

In version v5.1.84, the same rule received a different ID:

{
  "id": 3988422,
  "action": { "type": "redirect", "redirect": { "extensionPath": "/web-accessible-resources/redirects/nooptext.js" } },
  "condition": { "urlFilter": "||go.oclasrv.com/apu.php?" },
  "priority": 1001001
}

The only change was the id value.

Could you please confirm:

• Does a change in id values of static DNR rules alone trigger a full review?
• Or should skip-review still apply if rule contents are identical apart from IDs?

Thanks a lot for your help and clarification!

--