Allow standard-track sub-features without implementation / intent to implement

What type of issue is this?

Other

What information was incorrect, unhelpful, or incomplete?

As per BCD's data guidelines, we don't add browser features without any implementation, unless there is clear intent to implement.

However, there is some evidence that this practice can be confusing for end-users:

• https://github.com/mdn/browser-compat-data/pull/25081#issuecomment-2480492583
• https://github.com/mdn/browser-compat-data/issues/25916#issue-2852012266

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

I would suggest to accept standard-track sub-features, even if there is no implementation and no intent to implement.

Did you test this? If so, how?

n/a

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

No response

MDN metadata

No response

Start with docs/data-guidelines/index.md, especially the section on features with no browser support, then review the linked pull request and issue discussions for the reported confusion. No implementation file or test is named; done would require an agreed policy for standard-track sub-features and clearly identified updates to the relevant guidance or data checks.