New Stack Exchange search engine ignores automatic "possible duplicate" blocks in exact-duplicate questions

Question

I usually use the query "possible duplicate" closed:1 to search for questions closed as exact duplicates. It worked well in the past. Now, however, the query now returns considerably fewer results than in the past. It seems that the search engine finds only questions that contain the words "possible duplicate" outside of the "possible duplicate" block that is generated when the question is closed. Is this intended or not?

Answer 1

You can now use the duplicate:1 operator to perform this search, enjoy!

Answer 2

Using the following, where words are all now AND matched:

possible duplicate is:question closed:1

found a question whose entire content is this:

Should there be?

But note that you're using exact quoted match.

"possible duplicate"

This returns all those where the phrase is exactly that. Punctuation and all.

But, look closely at the duplicate close block and you'll see it starts like this:

Possible Duplicate:

Now, when you go back and search with this (with the colon):

"possible duplicate:"

you'll get the same numbers as you would if you just used the words in their AND state. It looks like punctuation really matters when you're quoting a phrase to search against.