MD002 rule reports inconsistent error

I am using a static site generator where I have frontmatter yaml like this:

---
id: index
title: Title of my page
---

The title is converted into H1 when the html page is created. So, in my case I don’t need the first heading in the markdown to be a H1. That’s why I’ve configured the following rules:

{
  "default": true,
  "MD002": { "level": 2 }
  "MD041": false
}

This seems to be working fine. If the very first heading in the content starts with anything other than H2, then I get the following error message:

../docs/index.md: 7: MD002/first-heading-h1/first-header-h1 First heading should be a top level heading [Expected: h2; Actual: h1]
../docs/index.md: 7: MD002/first-heading-h1/first-header-h1 First heading should be a top level heading [Expected: h2; Actual: h3]

I believe I am getting the right behaviour (or at least what I expect), but the error message is slightly conflicting/confusing. At the beginning the error says first-heading-h1 but later it says h2 is expected.

[DavidAnson]

After more thought, I’m leaning toward: MD002 -> first-heading-level MD041 -> first-line-heading

[DavidAnson]

Not yet.